From: Kenichi Handa <handa@gnu.org>
To: Haoyang Xu <snakehsu@gmail.com>
Cc: 15334@debbugs.gnu.org
Subject: bug#15334: 24.3; shell-quote-argument not considering non-ascii paths
Date: Fri, 13 Sep 2013 22:39:29 +0900 [thread overview]
Message-ID: <87vc24on72.fsf@gnu.org> (raw)
In-Reply-To: <CAGHDjn4=QmAgCyouB9=QUGBycrh_CAMJhqM0U8R5UikC8kDV5g@mail.gmail.com> (message from Haoyang Xu on Wed, 11 Sep 2013 11:27:25 +0800)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=iso-2022-jp-2, Size: 947 bytes --]
In article <CAGHDjn4=QmAgCyouB9=QUGBycrh_CAMJhqM0U8R5UikC8kDV5g@mail.gmail.com>, Haoyang Xu <snakehsu@gmail.com> writes:
> (shell-quote-argument "/Users/user/^[$BCfJ8L\^[$AB<^[(B/^[$BCfJ8^[(Bfile.txt")
> evals to
> "/Users/user/\\^[$BCf^[(B\\^[$BJ8^[(B\\^[$BL\^[(B\\^[$AB<^[(B/\\^[$BCf^[(B\\^[$BJ8^[(Bfile.txt"
> The shell-quote-argument function yields the same output under a new
> emacs instance started with `emacs -q`, so this should not be related to
> my configuration.
> A quick look of the function in question shows that it just escapes all
> non-ASCII characters, and the escaped Chinese characters cannot be
> correctly recognized by either bash or zsh.
I agree that such excapes are superfluous, but my bash
recognizes it correctly (my locale is ja_JP.UTF-8).
% mkdir -p \^[$BCf^[(B\^[$BJ8^[(B\^[$BL\^[(B\^[$AB<^[(B/\^[$BCf^[(B\^[$BJ8^[(Bfile.txt
% ls \^[$BCf^[(B\^[$BJ8^[(B\^[$BL\^[(B\^[$AB<^[(B
^[$BCfJ8^[(Bfile.txt/
---
Kenichi Handa
handa@gnu.org
prev parent reply other threads:[~2013-09-13 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 3:27 bug#15334: 24.3; shell-quote-argument not considering non-ascii paths Haoyang Xu
2013-09-11 8:11 ` Andreas Schwab
[not found] ` <CAGHDjn6egD84niYYK+ZaBqawTXc8Z=xBtZMtyNosDTxGw4EMUg@mail.gmail.com>
2013-09-12 5:09 ` bug#15334: Fwd: " Haoyang Xu
2013-09-12 8:41 ` Andreas Schwab
2013-09-12 9:56 ` Haoyang Xu
2013-09-13 13:39 ` Kenichi Handa [this message]
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=87vc24on72.fsf@gnu.org \
--to=handa@gnu.org \
--cc=15334@debbugs.gnu.org \
--cc=snakehsu@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 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.