On Mon, 8 Dec 2008 14:12:08 +0100, "Richard Hartmann"
<[EMAIL PROTECTED]> wrote:
> On Mon, Dec 8, 2008 at 11:54, Tony Mechelynck
> <[EMAIL PROTECTED]> wrote:
>
> > I don't personally use variable tabs so maybe I'm off-target; but for
> > some options (such as 'syntax' and 'filetype', not to mention
> > 'compatible') special actions are taken at the exact moment when their
> > their setting is modified by a ":set" command. Why not say that a ":set
> > ts=" or ":setlocal ts=", with a value (not ":set ts?" or equivalent)
> > will, at that instant, set vts to empty in the same range (":set",
> > ":setlocal" or even ":setglobal")? (IIUC, 'ts' is remembered but not
> > acted upon if 'vts' is nonempty, the way, let's say, 'cindent' is
> > remembered but not acted upon when 'indentexpr' is nonempty)
>
> Even better, just unset vts if ts is set and vice versa. Or copy all ts
> settings into vts, basically removing the ts functionality.
I did try that but it's trickier than it sounds. 'vts' allocates
memory for a parsed copy of the tabstops, and keeping track of that
memory when setting ts was excessively complicated so I opted for a
simpler "ignore ts if vts is set" strategy instead. I'll take another
look at it because I'm not happy with the counterintuitive way in
which 'ts' suddenly ceases to have any effect when 'vts' is set and
I'd rather the two options cooperated.
--
Matthew Winn
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
