From: "Drew Adams" <drew.adams@oracle.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 09:17:58 -0800 [thread overview]
Message-ID: <58DC9697D3AE4E1593894000B83A9546@us.oracle.com> (raw)
In-Reply-To: <831urtykqf.fsf@gnu.org>
> tags 10134 unreproducible
> quit
>
> > Yes, `emacs -Q'. Recipe: go to the node; look at it.
> > See attached screenshot.
>
> Sorry, not reproducible. See the attached screenshot. It's probably
> something specific to that system's setup, although I'm puzzled what
> kind of setup can have such a profound effect on the Emacs display.
Dunno what you mean by "that system's setup". Are you referring to the system
used to build Emacs or the system where I invoke `emacs -Q'?
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'.
In GNU Emacs 24.0.92.1 (i386-mingw-nt5.1.2600) of 2011-12-06 on MARVIN
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.6) --no-opt --cflags
-ID:/devel/emacs/libs/libXpm-3.5.8/include
-ID:/devel/emacs/libs/libXpm-3.5.8/src
-ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
-ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
-ID:/devel/emacs/libs/giflib-4.1.4-1/include
-ID:/devel/emacs/libs/jpeg-6b-4/include
-ID:/devel/emacs/libs/tiff-3.8.2-1/include
-ID:/devel/emacs/libs/gnutls-2.10.1/include --ldflags
-LD:/devel/emacs/libs/gnutls-2.10.1/lib'
This is the build zip:
http://alpha.gnu.org/gnu/emacs/windows/emacs-20111206-r106632-bin-i386.zip
This is the announcement post to emacs-devel@gnu.org:
http://lists.gnu.org/archive/html/emacs-devel/2011-12/msg00142.html
It is 100% reproducible with that build. If the bug has been fixed since then,
fine. But please try to reproduce it using the build cited in the bug report.
Do that, and my guess is you will have no problem at all seeing it.
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.
next prev parent reply other threads:[~2011-12-24 17:17 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 [this message]
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
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=58DC9697D3AE4E1593894000B83A9546@us.oracle.com \
--to=drew.adams@oracle.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).