From: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: info.texi
Date: Thu, 11 Aug 2005 03:29:33 +0300 [thread overview]
Message-ID: <87y879789s.fsf@jurta.org> (raw)
In-Reply-To: <200508101355.j7ADtjp25568@tug.org> (Karl Berry's message of "Wed, 10 Aug 2005 15:55:45 +0200")
> The new node tree has three top nodes: `Getting Started' for novices,
> `Advanced' for advances users, and `Expert Info' with the description
> of Info internals.
>
> In general this sounds quite good to me. The current conglomeration has
> always struck me as less than ideal.
>
> Two thoughts:
>
> - "edit document" seems "expert" to me.
The item `Info-enable-edit' in the node `Emacs Info Variables' has a
cross-reference @xref{Add, Edit}. It seems it tries to refer to the
text describing the command `e' which is currently located in the node
`Advanced'. So either this text should be moved to the node `Add',
or to a new node `Edit' under `Expert Info'.
> - the search commands seem by far the most important to me. In fact,
> they are the primary feature that (still) distinguishes Info from HTML
> etc. So I would put them first in the Advanced chapter. I also
> suggest putting Search Text before Search Index.
Ok, a new node tree is below. I will create a patch in a few days
if no one has more suggestions.
Getting Started
Help-Small-Screen
Help
Help-P
Help-^L
Help-Inv
Help-]
Help-]
Help-]
Help-M
Help-FOO
Help-FOO
Help-FOO
Help-Xref
Help-Int
Help-Q
Advanced
Search Text
Search Index
Go to node
Choose menu subtopic
Create Info buffer
Emacs Info Variables
Expert Info
Edit
Add
Menus
Cross-refs
Help-Cross
Tags
Checking
Creating an Info File
Index
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-08-11 0:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 0:08 info.texi Juri Linkov
2005-08-04 1:06 ` info.texi Lennart Borgman
2005-08-04 1:27 ` info.texi Luc Teirlinck
2005-08-04 1:55 ` info.texi Juri Linkov
2005-08-04 2:04 ` info.texi Lennart Borgman
2005-08-04 2:09 ` info.texi Luc Teirlinck
2005-08-04 3:39 ` info.texi Eli Zaretskii
2005-08-04 3:46 ` info.texi Luc Teirlinck
2005-08-04 11:21 ` info.texi Robert J. Chassell
2005-08-04 14:54 ` info.texi Andreas Schwab
2005-08-05 23:20 ` void symbol: font-lock-keyword-face Robert J. Chassell
2005-08-06 1:12 ` Juri Linkov
2005-08-06 11:19 ` Robert J. Chassell
2005-08-04 20:45 ` info.texi Richard M. Stallman
2005-08-04 20:45 ` info.texi Richard M. Stallman
2005-08-04 16:04 ` info.texi Karl Berry
2005-08-04 16:57 ` info.texi Juri Linkov
2005-08-04 22:11 ` info.texi Karl Berry
2005-08-04 17:41 ` info.texi David Kastrup
2005-08-10 4:02 ` info.texi Juri Linkov
2005-08-10 13:55 ` info.texi Karl Berry
2005-08-11 0:29 ` Juri Linkov [this message]
2005-08-11 12:56 ` info.texi Karl Berry
2005-08-11 14:28 ` info.texi Richard M. Stallman
2005-10-09 6:07 ` info.texi Juri Linkov
2005-10-09 17:14 ` info.texi Karl Berry
2005-10-10 4:14 ` info.texi Richard M. Stallman
2005-10-11 6:14 ` info.texi Juri Linkov
2005-10-11 6:15 ` info.texi Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2005-06-17 18:47 info.texi Richard Stallman
2005-06-18 9:33 ` info.texi Eli Zaretskii
2005-06-18 13:57 ` info.texi Juri Linkov
2005-06-19 3:51 ` info.texi Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y879789s.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.