Re: command history ("q:") inherits foldcolumn from current window

On Aug 17, 10:41 am, "Christian Brabandt" <cbli...@256bit.org> wrote:
> On Wed, August 17, 2011 4:22 pm, Paul wrote:
> > On Aug 17, 10:17 am, Paul <paul.domas...@gmail.com> wrote:
> >> The foldcolumn option is listed as local to window. Whenever I recall
> >> the command history ("q:"), the foldcolumn is set to the same as the
> >> window in which the cursor resided when issuing "q:". Is there a way
> >> to prevent this? I am using Vim 7.3 in Windows 7 Enterprise 32-bit.
>
> > For that matter, any new buffer/window created with <Ctrl-W Ctrl-N> or
> > ":new" also inherits the foldcolumn option...it'd be nice to avoid
> > that as well.  Not sure if it can be done with autocmd (which I'm
> > newly read-up on).  Currently, my .vimrc has:
>
> > autocmd BufNewFile,BufRead *.vb setl ft=vb | syntax enable | color
> > mine
> > autocmd BufNewFile,BufRead *.vb setl fen foldmethod=indent
> > foldcolumn=7 number
>
> I can't reproduce this. Only if I used set fdc=7 the new window opened by
> q: will contain the global value of the foldcolumn, but when only
> setting the foldcolumn locally (using :setl) opening the commandline
> window using q: does not contain the foldcolumn.

According to the help, foldcolumn is local to window. I can try
":setg foldcolumn=0", but when I issue ":setg? foldcolumn", the result
depends is determined by whatever window I happen to be in. So does
the foldcolumns showing in the command history. After ":setg fdc=0",
try ":setg fdc?" from different windows, some with foldcolumns and
some without. Also try calling up the command history from different
windows. Do you get the same variable result?

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