unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "Juri Linkov" <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: RE: generate 1) virtual index
Date: Mon, 24 Sep 2007 00:09:47 -0700	[thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACOEANCDAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87d4w9w1uh.fsf@jurta.org>

> Below is a simple patch that implements this:

Good. [I typed "forward" as the input regexp.]

I realize this was a first try, and here is some feedback. Compared to a
normal Index page such as Concept Index, I see these formatting differences
(drawbacks):

1. It says `File: apropos' instead of `File: emacs' (for the Emacs manual).
`File:' should point to the manual being indexed.

2. `Node: Index' is not quite correct. It would be better to use `Node:
Index for `forward'', where `forward' is the regexp input by the user, which
defines this particular virtual index. [BTW, `Node' for `L' says `Top',
which is not correct either (it should be something like `History').]
Together, `File:' and `Node:' would then uniquely identify a virtual index
(node).

3. The `Up:' link is `(dir)'. It should be `Top', to send you to the top of
the manual that is being indexed.

4. The description "Nodes whose indices contain `forward':" should come
before, not after, `* Menu:'.

5. That description should say "Index entries that match `forward':". (a) It
is the index entries that match, not the whole indexes. (b) It is the index
entries that are listed (the nodes are also listed, but the index entries
are primary). (c) It is regexp matching that is used, not necessarily
substring containment, IIUC.

Actually, I think you could dispense with the description line altogether,
if the `Node:' name is descriptive, as suggested in #2: `Node: Index for
`forward''.

6. Each menu item should be formatted as in a normal index: (a) no file name
written next to either the index entry or the node name, (b) alignment using
tabs, not a space. IOW, use this:

 * search-forward:		Nonincremental Search.

not this, which is what I see:

 * search-forward [c:/Emacs-22.1/info/emacs]:
(c:/Emacs-22.1/info/emacs)Nonincremental Search.


#3 and #6 make me think that you are perhaps intending this for use across
multiple books. Is that right?

Such a feature might be useful, but if it exists it should have a different
command name and a different binding. When used within a manual, `I' should
produce a virtual index for only that manual. In this case, I hit `I' in the
Emacs manual, so only the Emacs manual should be used for this virtual
index.

But if `I' is hit in `(dir)', then you could fall back to the multi-book
command, which would ask which books to use. If multiple manuals are used,
then you could include the Info file indication in the menu items, but it
should be listed only once, next to the node name, not the index entry, and
it should use the standard Info file format, e.g. `(emacs)', not an absolute
file name.

Question: Once such a virtual node has been created, couldn't it be
referenced in the history? `l' and `r' do access it properly, but it does
not seem to get registered with `L'. It's important that `L' be able to
access all visited nodes, including such virtual nodes.

HTH, and thanks; this is useful.

  reply	other threads:[~2007-09-24  7:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-23  9:47 generate 1) virtual index and 2) other pages for Info; 3) S-mouse-2: follow link in new window Drew Adams
2007-09-23 11:09 ` Bastien
2007-09-23 12:03   ` generate 2) other pages for Info Juri Linkov
2007-09-23 12:38     ` Lennart Borgman (gmail)
2007-09-23 14:17     ` Bastien
2007-09-23 19:18       ` Eli Zaretskii
2007-09-24  0:27         ` Bastien
2007-09-23 21:54     ` Richard Stallman
2007-09-23 11:41 ` generate 1) virtual index Juri Linkov
2007-09-23 16:43   ` Drew Adams
2007-09-23 20:42     ` Juri Linkov
2007-09-24  7:09       ` Drew Adams [this message]
2007-09-23 11:45 ` generate 2) other pages for Info Juri Linkov
2007-09-23 12:00 ` generate 3) S-mouse-2: follow link in new window Juri Linkov
2007-09-23 16:44   ` Drew Adams
2007-09-23 19:14     ` Lennart Borgman (gmail)
2007-09-23 20:42       ` Drew Adams
2007-09-24  0:20         ` Johan Bockgård
2007-09-24  1:22         ` Stefan Monnier
2007-09-24  2:01           ` Drew Adams
2007-09-24 18:20             ` Richard Stallman
2007-09-27 21:21               ` Drew Adams
2007-09-27 21:34                 ` David Kastrup
2007-09-27 21:34                 ` Stefan Monnier
2007-09-27 21:41                   ` Drew Adams
2007-09-27 21:53                 ` Drew Adams
2007-09-28 19:04                 ` Richard Stallman
2007-09-28 19:33                   ` Drew Adams
2007-09-28 22:22                     ` David Kastrup
2007-09-30  2:19                       ` Drew Adams
2007-09-30  8:54                         ` David Kastrup
2007-09-30 23:37                           ` Drew Adams
2007-09-30 23:49                             ` David Kastrup
2007-10-01  1:36                           ` Richard Stallman
2007-09-25 23:39     ` info.el patch to open node in new window [was: generate 3) S-mouse-2: follow link in new window] Drew Adams
2007-09-26  8:56       ` Juri Linkov
2007-09-26 15:02         ` Drew Adams
2007-09-29 22:44           ` info.el patch to open node in new window Juri Linkov
2007-09-30  2:19             ` Drew Adams
2007-09-29 22:41     ` generate 3) S-mouse-2: follow link " Juri Linkov
2007-09-30  2:19       ` Drew Adams
2007-09-29 22:43 ` Juri Linkov
2007-09-30  2:18   ` Drew Adams

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BNELLINCGFJLDJIKDGACOEANCDAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).