From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: bob@rattlesnake.com
Subject: Re: Patch to disable links line in *info* buffer
Date: Tue, 11 Jun 2002 13:20:44 +0000 (UTC) [thread overview]
Message-ID: <m17HlZk-000IeXC@localhost> (raw)
In-Reply-To: <buoofeii9bd.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 11 Jun 2002 16:05:58 +0900)
Miles Bader <miles@lsi.nec.co.jp> suggests:
... we could keep the `Next:' &c tags in the header-line, and
put _only_ the `File:' and `Node:' tags in the (displayed)
buffer -- that way, there wouldn't be any redundancy, and the
string that people most commonly might want to copy is
available in the buffer for copying.
This would also have the advantage that the first line usually
wouldn't wrap, as it often does currently.
Yes, this should work!
The output would look like this, where the first line is the new style
*info* header line, the second line is similar to the first line of an
old-style Info file, but contains only the `File:' and `Node:' tags,
and the following visible line is the title in whatever face or voice
you have set for Info:
Next: Printed Books, Prev: Using Texinfo, Up: Overview
File: texinfo, Node: Info Files
Info files
An Info file is a Texinfo file formatted so that the Info
documentation reading program can operate on it. (`makeinfo' and
`texinfo-format-buffer' are two commands that convert a Texinfo file
into an Info file.) ....
When I want to send a a long-winded, but I hope informative and
inspiring reference to someone, I copy
File: texinfo, Node: Info Files
as usual. When I want to send a more efficient reference to a
knowledgeable person, I use the `Info-specify-current-node-name'
command to construct the expression:
(texinfo)Info Files
(The `Info-specify-current-node-name' is simply the
`Info-copy-current-node-name' command renamed to make more sense than
the latter, which does *not* copy the node name, which is not
mentioned in the new style *info* header line.
[digression]
By the way, how do you fix an instance of a `plain vanilla' Emacs from
the current CVS sources so that you can move around an Info file using
the next, prev, and up key and mouse bindings?
This bug was reported some time ago but no permanent fix has been
installed in CVS; I simply cannot remember the temporary fix someone
suggested so I can use the new style *info* header lines.
I normally `(setq Info-use-header-line nil)' in my .emacs file, which
solves the problem for me, but for testing, I run
/usr/local/bin/emacs -q --no-site-file --eval '(blink-cursor-mode 0)'
and Info fails when I type `n' in a node, with the error message:
Info-extract-pointer: Node has no Next
(This morning's CVS snapshot, Tue, 2002 Jun 11 11:39 UTC,
GNU Emacs 21.3.50.29 (i686-pc-linux-gnu, X toolkit).)
--
Robert J. Chassell bob@rattlesnake.com
Rattlesnake Enterprises http://www.rattlesnake.com
next prev parent reply other threads:[~2002-06-11 13:20 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 18:32 Patch to disable links line in *info* buffer Romain FRANCOISE
2002-06-06 23:24 ` Kim F. Storm
2002-06-07 23:22 ` Richard Stallman
2002-06-08 0:52 ` Kim F. Storm
2002-06-08 21:39 ` Romain FRANCOISE
2002-06-08 22:08 ` Alex Schroeder
2002-06-08 22:30 ` Robert J. Chassell
2002-06-09 4:11 ` Miles Bader
2002-06-09 10:56 ` Robert J. Chassell
2002-06-09 5:16 ` Eli Zaretskii
2002-06-10 13:59 ` Stefan Monnier
2002-06-10 16:46 ` Robert J. Chassell
2002-06-10 17:28 ` Stefan Monnier
2002-06-10 20:50 ` Robert J. Chassell
2002-06-10 22:18 ` Thien-Thi Nguyen
2002-06-10 22:24 ` Stefan Monnier
2002-06-11 11:15 ` Robert J. Chassell
2002-06-11 21:00 ` Thien-Thi Nguyen
2002-06-11 5:26 ` Eli Zaretskii
2002-06-10 20:58 ` Robert J. Chassell
2002-06-10 21:52 ` Stefan Monnier
2002-06-11 9:36 ` Andreas Schwab
2002-06-10 19:57 ` Kim F. Storm
2002-06-11 19:25 ` Richard Stallman
2002-06-11 20:01 ` Jason Rumney
2002-06-11 23:45 ` Kim F. Storm
2002-06-12 12:14 ` Richard Stallman
2002-06-12 22:15 ` Kim F. Storm
2002-06-13 21:46 ` Richard Stallman
2002-06-13 23:22 ` Kim F. Storm
2002-06-19 13:10 ` Kim F. Storm
2002-06-19 15:02 ` Stefan Monnier
2002-06-21 21:40 ` Kim F. Storm
2002-06-21 23:56 ` Kim F. Storm
2002-06-21 9:40 ` Richard Stallman
2002-06-13 15:34 ` Robert J. Chassell
2002-06-13 17:17 ` Andreas Schwab
[not found] ` <200206130905.g5D95ie06537@aztec.santafe.edu>
2002-06-13 11:36 ` Robert J. Chassell
2002-06-13 23:18 ` Kim F. Storm
2002-06-14 15:47 ` Richard Stallman
2002-06-17 19:28 ` Patch for emacs-lisp-intro.texi Christian Egli
2002-06-11 19:25 ` Patch to disable links line in *info* buffer Richard Stallman
2002-06-09 23:04 ` Kim F. Storm
2002-06-10 10:15 ` Richard Stallman
2002-06-10 10:25 ` Eli Zaretskii
2002-06-09 15:18 ` Richard Stallman
2002-06-09 15:58 ` Kai Großjohann
2002-06-09 23:38 ` Kim F. Storm
2002-06-10 23:43 ` Richard Stallman
2002-06-10 5:14 ` Karl Eichwalder
2002-06-10 5:24 ` Miles Bader
2002-06-10 23:43 ` Richard Stallman
2002-06-11 0:12 ` Miles Bader
2002-06-11 5:27 ` Eli Zaretskii
2002-06-11 7:05 ` Miles Bader
2002-06-11 13:20 ` Robert J. Chassell [this message]
2002-06-12 2:34 ` Richard Stallman
2002-06-12 10:33 ` Robert J. Chassell
2002-06-12 23:47 ` Richard Stallman
2002-06-13 13:20 ` Robert J. Chassell
2002-06-14 15:47 ` Richard Stallman
2002-06-14 19:00 ` Karl Eichwalder
2002-06-12 2:32 ` Richard Stallman
2002-06-12 2:53 ` Miles Bader
2002-06-12 18:21 ` Karl Eichwalder
2002-06-12 21:36 ` Alex Schroeder
2002-06-11 4:17 ` Karl Eichwalder
2002-06-11 5:29 ` Eli Zaretskii
2002-06-11 15:26 ` Karl Eichwalder
2002-06-09 5:13 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2002-06-07 13:35 David Ponce
2002-06-07 13:56 David Ponce
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=m17HlZk-000IeXC@localhost \
--to=bob@rattlesnake.com \
/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.