all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Tim Van Holder" <tim.vanholder@gmail.com>
To: "Chong Yidong" <cyd@stupidchicken.com>
Cc: 279@emacsbugs.donarmstrong.com
Subject: bug#279: 23.0.60; (minor) minibuffer file-name completion issue for files containing $
Date: Wed, 27 Aug 2008 14:47:41 +0200	[thread overview]
Message-ID: <d69e7f6a0808270547h487d0f28w72ebbdccf0208464@mail.gmail.com> (raw)
In-Reply-To: <87ej4b8asv.fsf@cyd.mit.edu>

On Wed, Aug 27, 2008 at 4:13 AM, Chong Yidong <cyd@stupidchicken.com> wrote:
>> Files present on the system:
>>  /foo/$blah.xyzzy
>>  /foo/$blah.quux
>>
>> When pressing TAB twice to get completions for "/foo/$b", I noticed
>> that the fact that the $ gets escaped in the minibuffer seems to cause
>> the wrong letter to be highlighted in the *Completions* buffer
>> (i.e. the 'y' and 'u' are highlighted, respectively, instead of the
>> 'x' and 'q', respectively).
>
> I can't reproduce it in latest CVS.  Maybe it's been fixed in the
> meantime.  Do you still see this bug?

Now I get:
-> /foo
-> TAB
-> /foo/
-> TAB
-> /foo/$$blah.
-> TAB
-> /foo/$$blah. [no completions]

So I cannot reproduce the original problem with a CVS HEAD build, but
only in the sense that I don't get a *Completions* buffer at all.






  reply	other threads:[~2008-08-27 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  2:13 bug#279: 23.0.60; (minor) minibuffer file-name completion issue for files containing $ Chong Yidong
2008-08-27 12:47 ` Tim Van Holder [this message]
2008-08-27 17:19   ` Chong Yidong
2008-08-28  9:46     ` Tim Van Holder
2008-08-28 14:15       ` Chong Yidong
2008-08-29  9:51         ` Tim Van Holder
  -- strict thread matches above, loose matches on Subject: below --
2008-05-19 11:23 Tim Van Holder

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=d69e7f6a0808270547h487d0f28w72ebbdccf0208464@mail.gmail.com \
    --to=tim.vanholder@gmail.com \
    --cc=279@emacsbugs.donarmstrong.com \
    --cc=cyd@stupidchicken.com \
    /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.