[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: use of minibuffer in interactive spec code
From: |
Drew Adams |
Subject: |
RE: use of minibuffer in interactive spec code |
Date: |
Wed, 19 May 2010 05:44:01 -0700 |
> > 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.
- use of minibuffer in interactive spec code, Drew Adams, 2010/05/18
- RE: use of minibuffer in interactive spec code, Drew Adams, 2010/05/18
- Re: use of minibuffer in interactive spec code, Stefan Monnier, 2010/05/18
- Re: use of minibuffer in interactive spec code, Stefan Monnier, 2010/05/18
- RE: use of minibuffer in interactive spec code,
Drew Adams <=
- Re: use of minibuffer in interactive spec code, Sean Sieger, 2010/05/19
- Re: use of minibuffer in interactive spec code, Eli Zaretskii, 2010/05/19
- posting Windows binaries of latest trunk dev code [was: use of minibuffer in interactive spec code], Drew Adams, 2010/05/19
- Re: posting Windows binaries of latest trunk dev code [was: use of minibuffer in interactive spec code], Eli Zaretskii, 2010/05/19
- RE: posting Windows binaries of latest trunk dev code [was: use of minibuffer in interactive spec code], Drew Adams, 2010/05/19
- Re: posting Windows binaries of latest trunk dev code, Sean Sieger, 2010/05/20