From: "David De La Harpe Golden" <david.delaharpe.golden@gmail.com>
To: "Miles Bader" <miles@gnu.org>
Cc: Juri Linkov <juri@jurta.org>,
emacs-pretest-bug@gnu.org, Drew Adams <drew.adams@oracle.com>
Subject: Re: Info-build-node-completions has an extra `*' node
Date: Mon, 18 Feb 2008 04:12:57 +0000 [thread overview]
Message-ID: <8e24944a0802172012w7fa68beft213e2795041de9e6@mail.gmail.com> (raw)
In-Reply-To: <buobq6fvssg.fsf@dhapc248.dev.necel.com>
On 18/02/2008, Miles Bader <miles.bader@necel.com> wrote:
> "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.
>
Also, how does it differ from C-x n w widening the info buffer?
Ideally, I suppose an "all nodes" thing would show all nodes, but
still prettied for viewing, something like a "view docs as one big
HTML" translated web page, maybe with info commands working relative
to the node the point is in, and that would be the difference, but it
seems that g * is very similar to just turning off narrow at the
moment.
next prev parent reply other threads:[~2008-02-18 4:12 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
2008-02-18 4:12 ` David De La Harpe Golden [this message]
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=8e24944a0802172012w7fa68beft213e2795041de9e6@mail.gmail.com \
--to=david.delaharpe.golden@gmail.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).