From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: use of minibuffer in interactive spec code
Date: Wed, 19 May 2010 05:44:01 -0700 [thread overview]
Message-ID: <EC1F2B6DBEAC47F1A23A768A011349E0@us.oracle.com> (raw)
In-Reply-To: <jwvy6fgshi8.fsf-monnier+emacs@gnu.org>
> > It turns out that I now need to bind
> > `minibuffer-completion-predicate' in the
> > interactive spec. Otherwise, it has the value that is used for
> > `read-directory-name', which is `file-directory-p'.
>
> I cannot reproduce this problem on the trunk. Can you?
I don't have a trunk. ;-) The latest Windows binary I have is 23.2. If a more
recent binary becomes available I can check that. Or if there is a particular
source file or two that I can download and try (assuming I can get through to
the HTTP page), I can do that.
But as I said, the breakage occurred apparently between the last pretest and
23.2. 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.
next prev parent reply other threads:[~2010-05-19 12:44 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 [this message]
2010-05-19 15:39 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=EC1F2B6DBEAC47F1A23A768A011349E0@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.