From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 11348@debbugs.gnu.org
Subject: bug#11348: 24.0.95; TAB-completion in shell-command produces d:\/foo on MS-Windows
Date: Fri, 04 May 2012 20:01:55 +0300 [thread overview]
Message-ID: <83pqaj6fss.fsf@gnu.org> (raw)
In-Reply-To: <87bom40x0o.fsf@gnu.org>
> From: Chong Yidong <cyd@gnu.org>
> Cc: 11348@debbugs.gnu.org
> Date: Fri, 04 May 2012 23:46:31 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> The black magic occurs in `comint--complete-file-name-data' in
> >> comint.el.
> >
> > That function doesn't get called when I use the recipe to reproduce
> > the problem. At least instrumenting it with Edebug doesn't activate
> > Edebug inside that function.
>
> Whoops. Then maybe the problem is in pcomplete-completions-at-point,
I see in pcomplete-completions-at-point that typing "M-! cd d:\gnu TAB"
causes pcomplete-stub on entry to pcomplete-completions-at-point to get
the value "d:gnu", whereas if I type "M-! cd d:/gnu TAB", the value of
pcomplete-stub is "d:/gnu".
Sounds like whoever computes pcomplete-stub is the culprit: they treat
the backslash as an escape character (or so it seems).
> As an experiment, could you try removing
> pcomplete-completions-at-point from shell-dynamic-complete-functions
> and see if there is anything different?
This works better, it produces "cd d:\gnu/ ", which is ugly, but
correct.
next prev parent reply other threads:[~2012-05-04 17:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 11:09 bug#11348: 24.0.95; TAB-completion in shell-command produces d:\/foo on MS-Windows Eli Zaretskii
2012-05-04 7:10 ` Eli Zaretskii
2012-05-04 14:29 ` Chong Yidong
2012-05-04 14:54 ` Eli Zaretskii
2012-05-04 15:07 ` Drew Adams
2012-05-04 15:36 ` Chong Yidong
2012-05-04 15:02 ` Eli Zaretskii
2012-05-04 15:46 ` Chong Yidong
2012-05-04 17:01 ` Eli Zaretskii [this message]
2012-05-04 17:59 ` Stefan Monnier
2012-05-04 18:15 ` Eli Zaretskii
2012-05-04 23:32 ` Stefan Monnier
2012-05-05 0:22 ` Drew Adams
2012-05-05 12:47 ` Eli Zaretskii
2012-05-05 4:20 ` Stefan Monnier
2012-05-05 6:33 ` Eli Zaretskii
2012-05-07 8:01 ` Chong Yidong
2012-05-07 17:40 ` Eli Zaretskii
2012-05-07 15:27 ` Stefan Monnier
2012-05-07 15:44 ` Drew Adams
2012-05-07 16:11 ` Chong Yidong
2012-05-08 0:27 ` Stefan Monnier
2012-05-08 18:56 ` Eli Zaretskii
2012-05-09 17:22 ` Stefan Monnier
2012-05-09 18:07 ` 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=83pqaj6fss.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11348@debbugs.gnu.org \
--cc=cyd@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).