Re: [Mutt] #1263: establish variable categories prefix naming scheme
#1263: establish variable categories prefix naming scheme
Changes (by brendan):
* reporter: Rado Smiljanic <rado@xxxxxxxxxxxxxxxxxxx> => rado
Old description:
> {{{
> Package: mutt, Version: 1.5.6i
> Severity: normal
>
> -- Please type your report below this line
>
> Often it happens that people ask where they have to look for (a)
> variable(s) controlling a certain feature. It would save a lot of
> time finding related variables controlling a distinct area of mutt
> if we changed the organization of the reference for the variables
> in the TOC (table of contents) of the manual by putting them into
> categories.
> It will ease the time of newbies when searching for help, and that
> of veterans pointing people to an overviewable (?) portion of the
> _big_ manual, so they don't lose hope and interest in checking it
> out themselves.
>
> The idea is to prefix all vars with a common category name.
> For this I offer a suggestion at
>
> http://WIKI.mutt.org/?ManualVarNames
>
> where it can easily be changed by everyone and discussed why
> or why not the change should be done in some way or the other or
> at all. Corrections and additions (especially for post 1.5.6
> version) are welcome.
>
> Rado S
> >How-To-Repeat:
> >Fix:
> }}}
New description:
Often it happens that people ask where they have to look for (a)
variable(s) controlling a certain feature. It would save a lot of
time finding related variables controlling a distinct area of mutt
if we changed the organization of the reference for the variables
in the TOC (table of contents) of the manual by putting them into
categories.
It will ease the time of newbies when searching for help, and that
of veterans pointing people to an overviewable (?) portion of the
_big_ manual, so they don't lose hope and interest in checking it
out themselves.
The idea is to prefix all vars with a common category name.
For this I offer a suggestion at
http://WIKI.mutt.org/?ManualVarNames
where it can easily be changed by everyone and discussed why
or why not the change should be done in some way or the other or
at all. Corrections and additions (especially for post 1.5.6
version) are welcome.
Rado S
--
Ticket URL: <http://dev.mutt.org/trac/ticket/1263#comment:14>