From: Christoph Scholtes <cschol2112@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10134@debbugs.gnu.org
Subject: bug#10134: 24.0.91; Typo, (elisp) `Text from Minibuffer'
Date: Sat, 24 Dec 2011 10:48:27 -0700 [thread overview]
Message-ID: <4EF6106B.4080203@gmail.com> (raw)
In-Reply-To: <83vcp5x4a8.fsf@gnu.org>
On 12/24/2011 10:34 AM, Eli Zaretskii wrote:
> 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.
Sorry, I actually ran `make bootstrap' and `make info' when building the
pretest from Chong's tarball. I use the same build/package script
(Python) for the pretest that I wrote for the weekly builds. I can take
these steps out for the pretest though.
C:\Program Files (x86)\GnuWin32\bin>makeinfo --version
makeinfo (GNU texinfo) 4.8
Copyright (C) 2004 Free Software Foundation, Inc.
There is NO warranty. You may redistribute this software
under the terms of the GNU General Public License.
For more information about these matters, see the files named COPYING.
next prev parent reply other threads:[~2011-12-24 17:48 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 [this message]
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=4EF6106B.4080203@gmail.com \
--to=cschol2112@googlemail.com \
--cc=10134@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).