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: Sat, 24 Jan 2004 05:17:04 +0200 [thread overview]
Message-ID: <873ca6diy7.fsf@mail.jurta.org> (raw)
In-Reply-To: <877jziqt6g.fsf@jidanni.org> (Dan Jacobson's message of "Sat, 24 Jan 2004 04:57:43 +0800")
Dan Jacobson <jidanni@jidanni.org> writes:
> J> Right. This is quite confusing. So, instead of the current
> J> header line and node header:
>
> J> Next: uniq invocation, Up: Operating on sorted files
> J> File: coreutils.info, Node: sort invocation
>
> which one sees only in the standalone info reader, and only at the top
> of a page.
>
> Anyway, I'm talking about what one sees at the top of the screen, when
> not at the top of a page, and in emacs:
> Next: uniq invocation, Up: Operating on sorted files
In Emacs terminology, the line at the top of a window is "header line",
and the line at the top of an Info node buffer is "node header".
> J> it's better to hide the node header completely and show the
> J> following header line:
>
> J> (coreutils)sort invocation Next: uniq invocation, Up: Operating on sorted files
>
> I see, adding "(coreutils)sort invocation" to the front of the
> line. Sounds good, and there should be enough room too.
However, in some Info nodes the long node header might not fit on
the header line. One solution is to truncate the long node name
and display it in the header line partially with an ellipsis, e.g.:
sort invoc... Next: uniq invocation, Up: Operating on sorted files
>>> P.S. I wonder if there is any one stroke equivalent of "s <return>"
>
> J> In the latest patch for info.el I already proposed to add `M-s' keybinding:
> J> (define-key Info-mode-map "\M-s" 'Info-search-next)
>
> Well for we who have ESC s welded into our heads due to being born
> before the ALT button, there is no gain.
In most GNU programs the next search command is bound to `n' key,
but in Info this key is already occupied by `Info-next' command.
One alternative is to bind it to `N' key, but usually this key is used
to repeat a search backwards. Then another possibility is to bind it
to `S' key, which was suggested for `Info-search-case-sensitively'.
Since `Info-search-case-sensitively' is quite rarely used command,
its suggested keybinding `S' could be rebound to `Info-search-next'.
--
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2004-01-24 3:17 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
2004-01-23 20:57 ` Dan Jacobson
2004-01-24 3:17 ` Juri Linkov [this message]
[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
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=873ca6diy7.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 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).