From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 20237@debbugs.gnu.org
Subject: bug#20237: Emacs built on Windows cannot figure out path correctly
Date: Sat, 04 Apr 2015 18:07:11 +0300 [thread overview]
Message-ID: <83y4m8nd9c.fsf@gnu.org> (raw)
In-Reply-To: <86a8yoq7wt.fsf@gmail.com>
> From: Andy Moreton <andrewjmoreton@gmail.com>
> Date: Sat, 04 Apr 2015 15:34:26 +0100
>
> >> Removing the use of shell-quote-argument seems to work around this
> >> problem.
> >
> > I don't see why quoting here could do any harm. Could you elaborate
> > on why you think it's wrong?
>
> Because removing the shell-quote-argument call fixed it for me:
But that might mean some other bug elsewhere, which is simply
concealed by removing the quoting. The quoting is probably necessary
if the Python install directory's name includes whitespace.
Can you tell where the quoting causes that strange prefix be
prepended? I got as far as split-string-and-unquote in
python-shell-make-comint, and still saw no apparent problems.
Thanks.
next prev parent reply other threads:[~2015-04-04 15:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 17:52 bug#20237: Emacs built on Windows cannot figure out path correctly Da Zhang
2015-03-31 18:24 ` Eli Zaretskii
2015-03-31 21:24 ` Da Zhang
2015-04-01 2:40 ` Eli Zaretskii
2015-04-01 13:50 ` Da Zhang
2015-04-04 10:34 ` Eli Zaretskii
[not found] ` <55201ACF.2080001@gmail.com>
2015-04-04 17:23 ` Eli Zaretskii
[not found] ` <552022E4.7000008@gmail.com>
2015-04-04 17:49 ` Eli Zaretskii
2015-04-04 18:06 ` Da Zhang
2015-04-04 18:12 ` Eli Zaretskii
2015-04-04 18:18 ` Da Zhang
2015-04-04 18:38 ` Eli Zaretskii
2015-04-04 18:44 ` Eli Zaretskii
2015-04-04 19:06 ` Eli Zaretskii
2015-04-04 20:15 ` Da Zhang
2015-04-04 21:12 ` Eli Zaretskii
2015-04-04 19:07 ` Da Zhang
2015-03-31 22:46 ` Andy Moreton
2015-04-04 10:35 ` Eli Zaretskii
2015-04-04 14:34 ` Andy Moreton
2015-04-04 15:07 ` Eli Zaretskii [this message]
2016-06-02 2:54 ` Noam Postavsky
2016-06-04 9:15 ` 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=83y4m8nd9c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20237@debbugs.gnu.org \
--cc=andrewjmoreton@gmail.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 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).