On Mon, 3 Jun 2013 18:34:37 +0200, "Christian Brabandt" <[email protected]> wrote:
> Oh, well. I'll just carry it around for myself and keep working on it. > I already saw one problem, that when variable tabstops are enabled, > the 'tabstop' setting is ignored, but it still looks active. > This is confusing for the user and he might wonder, why the 'ts' > setting isn't honored. There's no way around that. Variable tabstops add more functionality than can possibly be expressed in the 'tabstop' option. When I originally wrote the patch I did it as a change to the 'tabstop' setting so that if you set it to a value which was a comma-separated list then it set multiple tab positions, while setting it to a single numeric value gave the existing behaviour. But people pointed out that if someone was expecting to be able to do numeric calculations with the value of 'tabstop' then suddenly finding that it contained non-numeric characters might cause problems. So it was implemented as a new option that takes priority over the older option. There are other options in Vim that behave in the same way, so there's a precedent. For example, if you set 'textwidth' then the value of 'wrapmargin' is ignored, and if you set 'binary' then a whole host of options are ignored. -- Matthew Winn -- -- 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.
