On Tuesday, February 5, 2013 5:32:35 AM UTC-6, Christian Brabandt wrote: > > Hm, this is tricky, since 'tw' is local to the buffer, while 'colorcolumn' > > is local to the window and by the time colorcolumn is evaluated, it looks > > for the textwidth column of the current active buffer. It isn't > > re-evaluated the next time another buffer is loaded (and even then, > > it wouldn't be window-local anymore).So perhaps, we need to make > > 'colorcolumn' buffer-local. >
Why couldn't it still be window-local? Don't we just need to add a redraw/refresh/whatever after loading a new buffer in an existing window? The value of colorcolumn doesn't change currently, only the visual effect. You could have one window on a buffer with colorcolumn set to 5, and another window with colorcolumn set to follow textwidth. Just because each buffer may have a different textwidth doesn't mean colorcolumn needs to follow the buffer as well. I think colorcolumn should follow textwidth when it changes, no matter the reason it changes. -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" 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.
