5 ms·

What's wrong with the way it handles long lines? It can either wrap or not wrap depending on your configuration. Personally, I disable wrapping in every editor

by doix 4y ago

What's wrong with the way it handles long lines? It can either wrap or not wrap depending on your configuration. Personally, I disable wrapping in every editor I use because I find it extremely off putting. I'm curious which behavior you desire and if you have any examples of editors that you think handle long lines well.

yakubin 4y ago
Performance. I mean really long lines, not merely lines which exceed window width. Vim is a bit better at that than Emacs, but it still slows to a crawl on some large lines. Sublime Text e.g. never has any problems with long lines on the other hand, no matter how long.
- doix 4y ago
  With wrapping or without? I occasionally use vim to open up minified JavaScript files to follow stack traces when sourcemaps are broken. I'll open the file and do something like 515328l (go 5153281 characters to the right) to get to the correct place and have never had issues. When we broke our sourcemaps for a bit, I was the dedicated human source map for a while and vim was an absolute life saver.
- Izkata 4y ago
  I've found that to mainly be a problem with syntax highlighting. Turning it off speeds it up significantly.
tombh 4y ago
Another issue is scrolling visual lines one by one that have been wrapped. (N)vim can only scroll by literal lines, so if a line is longer than the screen and wrapped, there is no way to step through line by visual line. https://github.com/neovim/neovim/issues/8715 https://github.com/neovim/neovim/issues/8715
- wruza 4y ago
  That’s strange. I just tested it and both GVim on windows and vim on a vps linux terminal have no problem with going anywhere on a 170k long line. It lags a little but visually is fine. And just in case you missed it, you may gj gk to navigate visual lines or remap j, k (and <Up>, <Down>) to gj gk to make that default. I have a genuine question why use nvim at all if it has such issues with presenting text in a window.
  - tombh 4y ago
    This is about _scrolling_ visual lines. Navigating them as you say, is just fine.
    - wruza 4y ago
      Ah, got it, right. Sorry for the noise!
- Macha 4y ago
  As that issue points out, "gj" and "gk" will step through by visual lines. The complaint in that ticket is that you can't make it the default for all the other ways of scrolling

by doix 4y ago

yakubin 4y ago

Performance. I mean really long lines, not merely lines which exceed window width. Vim is a bit better at that than Emacs, but it still slows to a crawl on some large lines. Sublime Text e.g. never has any problems with long lines on the other hand, no matter how long.

doix 4y ago
With wrapping or without? I occasionally use vim to open up minified JavaScript files to follow stack traces when sourcemaps are broken. I'll open the file and do something like 515328l (go 5153281 characters to the right) to get to the correct place and have never had issues. When we broke our sourcemaps for a bit, I was the dedicated human source map for a while and vim was an absolute life saver.
Izkata 4y ago
I've found that to mainly be a problem with syntax highlighting. Turning it off speeds it up significantly.

tombh 4y ago

Another issue is scrolling visual lines one by one that have been wrapped. (N)vim can only scroll by literal lines, so if a line is longer than the screen and wrapped, there is no way to step through line by visual line. https://github.com/neovim/neovim/issues/8715 https://github.com/neovim/neovim/issues/8715

wruza 4y ago
That’s strange. I just tested it and both GVim on windows and vim on a vps linux terminal have no problem with going anywhere on a 170k long line. It lags a little but visually is fine. And just in case you missed it, you may gj gk to navigate visual lines or remap j, k (and <Up>, <Down>) to gj gk to make that default. I have a genuine question why use nvim at all if it has such issues with presenting text in a window.
- tombh 4y ago
  This is about _scrolling_ visual lines. Navigating them as you say, is just fine.
  - wruza 4y ago
    Ah, got it, right. Sorry for the noise!
Macha 4y ago
As that issue points out, "gj" and "gk" will step through by visual lines. The complaint in that ticket is that you can't make it the default for all the other ways of scrolling