From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: Re: emacs Info's Next node name much more obvious than Current Date: Sat, 24 Jan 2004 05:17:04 +0200 Organization: JURTA Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: <873ca6diy7.fsf@mail.jurta.org> References: <87r7xtt5cm.fsf@jidanni.org> <87smi9t21t.fsf@penguin.cs.ucla.edu> <87llnzel2p.fsf_-_@jidanni.org> <87k73jkuyd.fsf@mail.jurta.org> <877jziqt6g.fsf@jidanni.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1074921923 1245 80.91.224.253 (24 Jan 2004 05:25:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 24 Jan 2004 05:25:23 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Jan 24 06:25:17 2004 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AkGIG-00089l-00 for ; Sat, 24 Jan 2004 06:25:17 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AkGIA-0000xz-QU for geb-bug-gnu-emacs@m.gmane.org; Sat, 24 Jan 2004 00:25:10 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1AkGI7-0000v5-RF for bug-gnu-emacs@gnu.org; Sat, 24 Jan 2004 00:25:07 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1AkGHb-0000hh-Kg for bug-gnu-emacs@gnu.org; Sat, 24 Jan 2004 00:25:06 -0500 Original-Received: from [66.33.219.4] (helo=spork.dreamhost.com) by monty-python.gnu.org with esmtp (Exim 4.24) id 1AkGGI-0000D5-FV for bug-gnu-emacs@gnu.org; Sat, 24 Jan 2004 00:23:14 -0500 Original-Received: from mail.jurta.org (80-235-32-150-dsl.mus.estpak.ee [80.235.32.150]) by spork.dreamhost.com (Postfix) with ESMTP id 2057C11DC3E; Fri, 23 Jan 2004 21:23:11 -0800 (PST) Original-To: Dan Jacobson In-Reply-To: <877jziqt6g.fsf@jidanni.org> (Dan Jacobson's message of "Sat, 24 Jan 2004 04:57:43 +0800") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:6723 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:6723 Dan Jacobson 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 " > > 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/