-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Full soft-wrap implementation #77
Comments
First of all, thanks for this nice editor! I have written a short introduction to mle here /1/ I have some questions regarding usage:
|
Hi, thank you for writing up that blog post. It's better than the official help!
For this key press, termbox2 currently understands xterm style (
Yes cut/copy buffers are local to current buffer. But there is also a global buffer that contains the last cut/copy performed in any buffer. That command ( By the way, to insert the content of a file into a buffer, it may be easier to
I'm very curious about this. What kind of machine are you running this on? On my machine (Linux 6.x x86_64), mle is still a bit faster than vim latest. It seems more recent versions of vim became more efficient since the last time I tested this! I do see most of the time spent in
mle has 1 built-in syntax called
Indeed, I have a branch with this that I need to revisit. It will most likely be in the next version. |
Thanks for the elaborate answer.
/1/ "Small" file, i.e.,
/2/ "Large" file, i.e.,
/3/ Uses /4/ Performance Comparison of mmap() versus read() versus fread() |
Interesting. I wonder why Can you run it through a debugger or |
Results for small file
Large file
|
OK I see a bug in |
Yes, this change in the command line makes a difference of a factor of more than two!
Profiling mle 1.7.3-dev and the "small" files gives:
Results for small file with
|
as discussed in #75
The text was updated successfully, but these errors were encountered: