From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10134@debbugs.gnu.org
Subject: bug#10134: 24.0.91; Typo, (elisp) `Text from Minibuffer'
Date: Sat, 24 Dec 2011 19:34:07 +0200 [thread overview]
Message-ID: <83vcp5x4a8.fsf@gnu.org> (raw)
In-Reply-To: <58DC9697D3AE4E1593894000B83A9546@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <10134@debbugs.gnu.org>
> Date: Sat, 24 Dec 2011 09:17:58 -0800
>
> Did you actually try it using the cited Emacs version/build? It is the latest
> Windows binary made available on emacs-devel. It is simple to download it and
> test with `emacs -Q'.
I used my own compiled binary of the same version.
Please look at the file info/elisp-3 you have, and tell me:
. Do you see the extra newline in that file?
. If you do, what do the first 2 lines of that file say?
The file I have doesn't have the extra newline, and its beginning says
this:
This is /home/cyd/trunk/doc/lispref/../../info/elisp, produced by
makeinfo version 4.13 from /home/cyd/trunk/doc/lispref/elisp.texi.
IOW, this file was produced by Chong when he created the pretest
tarball. Maybe yours was produced by a different version of makeinfo
which has some bug. That would explain why we see such a different
picture.
> If you test only with the pretest or the latest trunk then you are probably not
> testing with the same Emacs sources, let alone the same binary build.
I don't see it, neither in the current trunk nor in the 24.0.91
pretest. The binary was built by me, but I don't think a different
binary can produce such an effect on display. The Info files in the
pretest are produced by whoever made the pretest, in this case Chong,
and are not supposed to be regenerated during the build. However,
perhaps Christoph somehow ended regenerating them when he built the
binary you used, and maybe he used some different version of makeinfo.
next prev parent reply other threads:[~2011-12-24 17:34 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 [this message]
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
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=83vcp5x4a8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10134@debbugs.gnu.org \
--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).