From: David Ponce <david@dponce.com>
Subject: Re: Info navigation is broken
Date: Sun, 02 Jun 2002 10:31:55 +0200 [thread overview]
Message-ID: <3CF9D7FB.3060403@dponce.com> (raw)
In-Reply-To: 3CF9D6B4.4060200@dponce.com
> After commenting out the following line in `Info-setup-header-line'
> Info navigation worked fine again.
>
> ;;; It is useful to be able to copy the links line out of the buffer
> ;;; with M-w.
> (narrow-to-region (1+ header-end) (point-max))
Oops! You should have read : After uncommenting the abobe line.
Sorry!
next prev parent reply other threads:[~2002-06-02 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 8:26 Info navigation is broken David Ponce
2002-06-02 8:31 ` David Ponce [this message]
2002-06-03 11:41 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-06-03 12:05 David Ponce
2002-06-04 23:26 ` Richard Stallman
2002-06-05 15:16 ` Stefan Monnier
2002-06-05 16:39 ` Eli Zaretskii
2002-06-05 23:55 ` Miles Bader
2002-06-06 4:45 ` Eli Zaretskii
2002-06-07 0:44 ` Richard Stallman
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=3CF9D7FB.3060403@dponce.com \
--to=david@dponce.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 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).