Re: keys and command name info

[Gregor Zattler <telegraph@gmx.net>]

Hi Carsten, org-mode developers,
* Carsten Dominik <carsten.dominik@gmail.com> [02. Aug. 2010]:
> I am not sure I would like such a change because I think it
> makes the manual harder and less fluid to read and considerably longer.

It makes the manual longer as in bytes/bandwidth but not as in
lines which IMHO corresponds with the amount of time one needs to
read the manual.

If it's consistent within the manual it's IMHO not confusing or
harder to read because it's easy to skip.

To me actually this hints look like headings.  They would support
me in skimming a section of commands in order to find the right
one.  Those paragraphs with key sequences at the beginning are
hard to skim because all the info which stands out is not
relevant if one searches for a specific action.

Seeing how the command is named in the context of usage
information might help lisp novices in getting an idea why some
solutions work the way they do.

Just my 2¢, Gregor


> On Jul 28, 2010, at 9:36 PM, Andreas Röhler wrote:
>>what about delivering mnemonic command names alongside
>>with its keys in org-info?
>>
>>For example
>>
>>8.1. Agenda files
>>
>>[ ... ]
>>`C-c ['
>>    Add current file to the list of agenda files.  The file is added to
>>    the front of the list.  If it was already in the list, it is moved
>>    to the front.  With prefix arg, file is added/moved to the end.
>>
>>might be provided as
>>
>>8.1. Agenda files
>>
>>[ ... ]
>>`C-c [', org-agenda-file-to-front
>>    Add current file to the list of agenda files.  The file is added to
>>    the front of the list.  If it was already in the list, it is moved
>>    to the front.  With prefix arg, file is added/moved to the end.
>>
>>
>>IMHO it's useful for emacs-beginners, but for hackers
>>too, as remembering function names may precede
>>remembering keys - which are to change individually
>>anyway.