On 24/06/12 20:52, Ben Fritz wrote:
On Sunday, June 24, 2012 7:06:39 AM UTC-5, Tony Mechelynck wrote:
On 24/06/12 13:41, Christian Brabandt wrote:
Hi Tony!
On So, 24 Jun 2012, Tony Mechelynck wrote:
:setlocal option=value
:setlocal boolopt
:setlocal noboolopt
sets only the local value
Except, that for iminsert this also sets the global option.
regards,
Christian
Ben Fritz said the behaviour is correct for already existing buffers. I
think what happened here is what I mentioned lower down in the part you
snipped.
Nope, the option is not getting copied from the buffer on creating a new buffer.
It is getting set from the global option as documented.
However, the global option is being incorrectly set when using :setlocal.
Ah, sorry. I did the tests below myself and I get the same results as you do
gvim -N -i NONE -u NONE
:set iminsert?
2
iminsert=2
:setg imi?
iminsert=2
:new
:setlocal iminsert=1
:set iminsert?
1
iminsert=1
:setg imi?
iminsert=1 <== this shows the bug
:wincmd w
:set iminsert?
2
iminsert=2
:setg imi?
iminsert=1 <== and yet, this is not a global option: in this
particular case, we see a local setting
different from the global setting
:new
:set iminsert?
1
iminsert=1
:setg imi?
iminsert=1
:setl imi=2
:setg imi?
iminsert=2 <== the bug, again
:setl imi=0
:setg imi?
iminsert=0
The above shows that it is possible to display different values with
:setl imi? and :setg imi? in the same buffer, but that :setl imi=value
(with "value" being 0, 1 or 2) also sets the global setting to the same
value.
I'm using gvim (Huge) version 7.3.566 with GTK2/Gnome2 GUI.
Best regards,
Tony.
--
Drugs may be the road to nowhere, but at least they're the scenic
route!
--
You received this message from the "vim_dev" 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
