> On Jan 16, 2012, at 1:53 PM, Tim Chase wrote:
>
> > On 01/16/12 12:04, Eric Weir wrote:
>
> >> Thanks, Tim--and to everyone else who responded. My guess is
> >> it was hitting u while in visual mode. I have not advanced to
> >> the stage of using commands beginning with a g or a v. I'll
> >> check out the ones you suggest.
>
> > well, the "v" ones are ones done in visual mode, which it sounds like you're already using. Pressing u/U/~/? in visual mode transform the selection accordingly (lowercasing, uppercasing, swap-casing, and ROT13ing). The other "g" variants perform the same transformations over the text covered by <motion>
>
> I misspoke. Yes, I do use v and V--frequently! What puzzles me in this case is that the changes took place over an extended block of text. As I write I can see how that would have happened. Most of what was changed was in folds. If I selected the folds I would've selected everything in the fold.
>
It's easy to make such mistake if selected text in Visual mode does
not stand out and looks similar to Folded lines. Then you may not
notice that you are in Visual mode. This is unfortunately a problem
with many Vim color schemes, including the default one for GUI. They
use the same or similar background color for selected text (Visual),
folded lines (Folded), and current line/column (CursorLine,
CursorColumn) highlight groups. I recommend setting background color
for Visual selection to some bright, garish color that is different
from all other highlightings. Something like CadetBlue2 or cyan. Then
you will always know when you are in Visual mode. If you use default
GUI colorscheme, try putting this in your .vimrc:
hi Visual gui=NONE guifg=NONE guibg=CadetBlue2
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment