From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: cschol2112@googlemail.com, 10134@debbugs.gnu.org
Subject: bug#10134: 24.0.91; Typo, (elisp) `Text from Minibuffer'
Date: Sat, 24 Dec 2011 22:38:55 +0200 [thread overview]
Message-ID: <83pqfdwvq8.fsf@gnu.org> (raw)
In-Reply-To: <7BAAA475867B497B9676E0F4F1D4E217@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <10134@debbugs.gnu.org>,
> "'Christoph Scholtes'" <cschol2112@googlemail.com>
> Date: Sat, 24 Dec 2011 12:00:35 -0800
>
> > Please look at the file info/elisp-3 you have, and tell me:
> >
> > . Do you see the extra newline in that file?
>
> Yes:
>
> -- Variable: minibuffer-local-map
> This
>
> is the default local keymap for reading from the minibuffer. By
> default, it makes the following bindings:
>
> `C-j'
> `exit-minibuffer'
> ...
>
> > . If you do, what do the first 2 lines of that file say?
>
> This is ./../../info/elisp, produced by makeinfo version 4.8 from
> ./elisp.texi.
So now everything is clear: this is a bug in Texinfo 4.8 that is fixed
in later versions. The bug is triggered by this trickery in the
manual's sources:
@defvar minibuffer-local-map
This
@anchor{Definition of minibuffer-local-map}
@c avoid page break at anchor; work around Texinfo deficiency
is the default local keymap for reading from the minibuffer. By
default, it makes the following bindings:
Evidently, makeinfo 4.8 leaves an empty line where there was the
@anchor. The @anchor was put in this strange place to make sure the
page break is not inserted in the printed manual, thus making the
cross-references to it point to the wrong page. I don't know if this
trickery is still needed nowadays.
prev parent reply other threads:[~2011-12-24 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 14:45 bug#10134: 24.0.91; Typo, (elisp) `Text from Minibuffer' Drew Adams
2011-12-24 11:05 ` Eli Zaretskii
2011-12-24 16:05 ` Drew Adams
2011-12-24 16:53 ` Eli Zaretskii
2011-12-24 17:17 ` Drew Adams
2011-12-24 17:34 ` Eli Zaretskii
2011-12-24 17:48 ` Christoph Scholtes
2011-12-24 17:57 ` Eli Zaretskii
2011-12-24 20:06 ` Christoph Scholtes
2011-12-25 10:23 ` Juanma Barranquero
2011-12-25 11:01 ` Eli Zaretskii
2011-12-24 20:00 ` Drew Adams
2011-12-24 20:38 ` Eli Zaretskii [this message]
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=83pqfdwvq8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10134@debbugs.gnu.org \
--cc=cschol2112@googlemail.com \
--cc=drew.adams@oracle.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).