On Sun, Sep 09, 2012 at 04:17:41PM +0200, Bram Moolenaar wrote: >> Should examples like ":au group ..." also be put in backticks, >> e.g. `:au group ...` (which is not colored at the moment) or only >> commands, e.g ":autogroup" -> `:autogroup` - and stuff like ":au >> group ..." stays in quotes. > > Every command a user would type should be in single quotes. But not > option values, command output, etc.
Thanks for the clarification.
>> Related to this is e.g. ":{range}!cmd" which is not a tag and
>> can't be followed with Ctrl-], should it be put in `..`? Same for
>> "caw" for which no help is available.
>>
>> In short, should all `..` point to tags, and what to do with the
>> commands which don't have a tag?
>
> No, the backticks are not for tags but for commands. We may need to
> change the way tags are extracted in help files so that using CTRL-] on
> the command inside backticks works.
Okay, thanks. I was just confused because `..` can be used as tag
in most cases just fine (due to the recent patch) and it might
confuse the user if CTRL-] doesn't work for all `..` items.
Is `:{range}!cmd` correct, or should it be ".."? The user can't
really type it ("{range}" and "cmd" are not verbatim) - but it
still describes a command.
Regards,
Simon
--
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9
pgpkUDtK67spo.pgp
Description: PGP signature
