From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: use of minibuffer in interactive spec code
Date: Wed, 19 May 2010 11:39:42 -0400 [thread overview]
Message-ID: <jwvtyq3oqdg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <EC1F2B6DBEAC47F1A23A768A011349E0@us.oracle.com> (Drew Adams's message of "Wed, 19 May 2010 05:44:01 -0700")
> But as I said, the breakage occurred apparently between the last
> pretest and 23.2.
I'm confused. Your message seemed to refer to a "last pretest" in
january 2009:
I don't know if this is a bug or a bug fix. I would like to get some
info about it, if possible, to understand better. The behavior in
this respect is new in Emacs 23.2. It changed apparently sometime
after this build:
GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
of 2009-01-15 on LENNART-69DE564
> Since the last pretest was not long before 23.2, and
> since you think you were the one who might have broken this, perhaps
> you can look at changes you made during that short period.
If it's really between the last pretest and 23.2, then I'm not so sure
I'd be to blame since I haven't made (m)any changes around that time.
Have you tried my recipe? What does it return?
Stefan
next prev parent reply other threads:[~2010-05-19 15:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 17:11 use of minibuffer in interactive spec code Drew Adams
2010-05-18 17:27 ` Drew Adams
2010-05-18 20:39 ` Stefan Monnier
2010-05-19 3:27 ` Stefan Monnier
2010-05-19 12:44 ` Drew Adams
2010-05-19 15:39 ` Stefan Monnier [this message]
2010-05-19 16:40 ` Drew Adams
2010-05-19 17:41 ` Stefan Monnier
2010-05-19 16:04 ` Sean Sieger
2010-05-19 16:16 ` Eli Zaretskii
2010-05-19 16:21 ` posting Windows binaries of latest trunk dev code [was: use of minibuffer in interactive spec code] Drew Adams
2010-05-19 17:25 ` Eli Zaretskii
2010-05-19 17:48 ` Drew Adams
2010-05-20 21:19 ` posting Windows binaries of latest trunk dev code Sean Sieger
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=jwvtyq3oqdg.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@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).