From: Miles Bader <miles.bader@necel.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Juri Linkov' <juri@jurta.org>, emacs-pretest-bug@gnu.org
Subject: Re: Info-build-node-completions has an extra `*' node
Date: Mon, 18 Feb 2008 12:37:35 +0900 [thread overview]
Message-ID: <buobq6fvssg.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <000001c871cd$64e4a6c0$e140908d@us.oracle.com> (Drew Adams's message of "Sun, 17 Feb 2008 17:27:14 -0800")
"Drew Adams" <drew.adams@oracle.com> writes:
> But first things first. What is the rationale for this? Does it really
> fulfill a need? If not, let's just get rid of it, to avoid unnecessary
> confusion.
I agree.
Seeing the raw info file as a result of goto-node is pretty odd,
unlikely to be very useful for most people (especially now that info
does inter-node search very naturally with normal isearch), and fairly
likely to confuse those who stumble upon this "feature" by accident.
Are there people that use this feature regularly?
-Miles
--
/\ /\
(^.^)
(")")
*This is the cute kitty virus, please copy this into your sig so it can spread.
next prev parent reply other threads:[~2008-02-18 3:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 22:25 Info-build-node-completions has an extra `*' node Drew Adams
2008-02-17 22:34 ` Drew Adams
2008-02-17 23:05 ` Bastien
2008-02-17 23:22 ` Juri Linkov
2008-02-17 23:53 ` Bastien Guerry
2008-02-18 0:27 ` Juri Linkov
2008-02-18 0:56 ` Bastien Guerry
2008-02-18 23:54 ` Juri Linkov
2008-02-19 0:48 ` Bastien
2008-02-21 19:24 ` Drew Adams
2008-02-18 0:02 ` Drew Adams
2008-02-18 0:29 ` Juri Linkov
2008-02-18 0:54 ` Bastien Guerry
2008-02-18 1:27 ` Drew Adams
2008-02-18 3:37 ` Miles Bader [this message]
2008-02-18 4:12 ` David De La Harpe Golden
2008-02-18 11:56 ` Bastien Guerry
2008-02-18 23:55 ` Juri Linkov
2008-02-18 17:31 ` Richard Stallman
2008-02-18 17:40 ` Drew Adams
2008-02-19 15:45 ` Richard Stallman
2008-02-19 21:35 ` Stefan Monnier
2008-02-20 3:23 ` 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=buobq6fvssg.fsf@dhapc248.dev.necel.com \
--to=miles.bader@necel.com \
--cc=drew.adams@oracle.com \
--cc=emacs-pretest-bug@gnu.org \
--cc=juri@jurta.org \
--cc=miles@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 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).