From: Juri Linkov <juri@jurta.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: emacs Info's Next node name much more obvious than Current
Date: Fri, 23 Jan 2004 09:03:38 +0200 [thread overview]
Message-ID: <87k73jkuyd.fsf@mail.jurta.org> (raw)
In-Reply-To: <87llnzel2p.fsf_-_@jidanni.org> (Dan Jacobson's message of "Fri, 23 Jan 2004 05:21:18 +0800")
Dan Jacobson <jidanni@jidanni.org> writes:
> I see. In emacs, unless one looks down to the dreary modeline,
> one's eyes think one is already on the uniq page, as it is glowing on
> top, even though prefixed by "Next:"
> C-h i m s o r t <return> s + <return> s <return> s <return>
Right. This is quite confusing. So, instead of the current
header line and node header:
Next: uniq invocation, Up: Operating on sorted files
File: coreutils.info, Node: sort invocation
it's better to hide the node header completely and show the
following header line:
(coreutils)sort invocation Next: uniq invocation, Up: Operating on sorted files
This, of course, duplicates information displayed in the mode line,
but this is not as bad as current information separation between
node header, header line and mode line.
> P.S. I wonder if there is any one stroke equivalent of "s <return>"
In the latest patch for info.el I already proposed to add `M-s' keybinding:
(define-key Info-mode-map "\M-s" 'Info-search-next)
There were another suggestions like `/', `\' for the same function,
but seems these are not acceptable.
--
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-01-23 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r7xtt5cm.fsf@jidanni.org>
[not found] ` <87smi9t21t.fsf@penguin.cs.ucla.edu>
2004-01-22 21:21 ` emacs Info's Next node name much more obvious than Current Dan Jacobson
2004-01-23 7:03 ` Juri Linkov [this message]
2004-01-23 20:57 ` Dan Jacobson
2004-01-24 3:17 ` Juri Linkov
[not found] ` <mailman.1254.1074921911.928.bug-gnu-emacs@gnu.org>
2004-01-24 16:36 ` Johan Bockgård
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=87k73jkuyd.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=bug-gnu-emacs@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.