On 16/02/14 09:58, Lew_Rockwell_fan wrote:
TYVM, sir! That's a 110% response. :)

  I used:

map <F12> :set invwrap<CR>
imap <F12> <C-O>:set invwrap<CR>

in

/root/.vimrc
~/.vimrc
/root/.gvimrc
~/.gvimrc
&
/usr/share/vim/vim74/evim.vim

and it works perfectly in evim, gvim, and vim.  For the possible benefit of
people reading this because they got here through a search engine looking
for the same thing I'll add that the single line

map <F12> :set wrap!<cr>

that I've seen elsewhere asserted to do the same thing does not work for me
on a plain Openbox system (no LXDE, no Lubuntu) built from the 32 bit Ubuntu
13.10 Saucy mini.iso as of 2014.02-Feb.16.

That's unusual, because wherever I tried, :set wrap! (with the exclamation mark at the end) and :set invwrap do exactly the same thing (and similarly for any boolean option). Maybe <cr> (in lowercase) is not the same as <CR> (in uppercase, as used everywhere in the Vim help, and among others at ":help keycodes") but in that case you should have seen it remain hanging on the command-line, which somehow I doubt. Another possibility is that your Openbox system was running in 'compatible' mode, where <> notation is not recognised by default; however as soon as Vim finds a .vimrc during startup it sets 'nocompatible' immediately before sourcing it. (This does not happen if a -u argument prevents the search for a user .vimrc.)

Tips and tricks:
On my system, /root/.vimrc is a softlink to /home/tonymec/.vimrc so these two can never get out of sync. Similarly for .gvimrc which is actually a zero-length file. Maybe I ought to do the same for .vim/


Best regards,
Tony.
--
If you think last Tuesday was a drag, wait till you see what happens tomorrow!

--
--
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

--- You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to