> The at sign says "there's more lines, but the next line would wrap and > take up more than what you currently can see". If you have 'wrap' on, > Vim never shows you a line unless it's complete. So, if you have a huge > line, it might need many physical lines to show it to you. If it > doesn't have that many, it shows an '@', telling you that the file > doesn't end (~), doesn't have a newline ( ), but can't really be > displayed properly with the current setup. Usually, placing the cursor, > or rather trying to place it, on the first '@' line will make the line > visible. > > Vim veterans, I'm not sure about at least the secod part myself, so > please correct me if I'm wrong.
See my previous email...you're right or wrong, depending on how 'display' is set :) The really ugly case occurs when a single very-long-but-wrapped line occupies more than the entire screen. You're then stuck using gj/gk to navigate by screen-lines instead of using j/k to navigate by file-lines. I've seen folks remap j/k (or <up>/<down>) to gj/gk to make this less noisome. I map them on the fly if I need them. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
