Wednesday, April 27, 2011

Re: Where is defined?

On Wed, 27 Apr 2011, Steve Litt wrote:

> On Wednesday 27 April 2011 21:04:34 Ben Schmidt wrote:
>
>> <localleader> to <voleader> before executing it.
>>
>> My main question though, is, why do you want to do this? Maybe [...]
>> there is a more standard 'Vim way' [...]
>
> [...]
>
> Some time around VO 0.2.4, VO stopped hard-coding .. and began to set
> <localleader> to ,, and put <localleader> in all VO's map commands.
> Then our troubles began.
>
> The Debian maintainer changed <localleader> to two backslashes or
> something like that, with the explanation that Debian must default
> <localleader> to that or it's not a Debian package.
>
> I don't know anything about that, but I can tell you that if every
> command starts with \\, it's not VimOutliner, it's some poke slow
> piece of software.

Where do you get the idea that Debian defaults <LocalLeader> to "two
backslashes or something like that"?

I don't use Debian regularly, but in a Debian 6 (sid?) VM, it seems to
default VO's mappings to ,,{whatever}.

Test steps:
# apt-get install vim-addons-manager
# apt-get install vim-vimoutliner
$ vim-addons install vimoutliner
$ vim test.otl
:map
(shows a bunch of mappings that start with ,,)

vim-vimoutliner version is listed as 0.3.4+pristine-9


> So the best of both worlds is to stop using <localleader> for the VO
> command prefix.. [...]

What? Isn't the best of both worlds to set <LocalLeader> ( ==
maplocalleader ) to ',,'? the way Debian VO's /etc/vim/vimoutlinerrc
seems to do?

Then the default is the value you (and presumably others) find sensible.
And if someone else wants something different, it's easy to change.


> [...] Personally I'd just hardcode ,, but there seems to be some
> resistance to that -- maybe for a reason similar to an aversion to
> magic numbers. Or maybe because a person missing their right middle
> finger would want to change that command prefix.

Not everyone uses a QWERTY, is another reason. Regardless, hardcoding
it with no easy way to override is the wrong route for a plugin to take.


> So anyway, all we have to do is define a command or key or variable or
> whatever that isn't currently a part of Vim, and that way the Debian
> people can define <localleader> however they want, and we can default
> our command prefix to the tried and true ,,.
>
> So, within that context, what do you think?

Are you sure something else isn't interfering with maplocalleader?

--
Best,
Ben

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

No comments:

Post a Comment