From: Eli Zaretskii <eliz@gnu.org>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: 15337@debbugs.gnu.org
Subject: bug#15337: 24.3.50; [PATCH] cd to directory name with french accent fail from term/ansi-term
Date: Wed, 11 Sep 2013 16:51:31 +0300 [thread overview]
Message-ID: <83y573ihzw.fsf@gnu.org> (raw)
In-Reply-To: <87a9jj7eqj.fsf@gmail.com>
> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
> Date: Wed, 11 Sep 2013 13:57:24 +0200
>
> diff --git a/lisp/files.el b/lisp/files.el
> index f9ff3c9..a27bb06 100644
> --- a/lisp/files.el
> +++ b/lisp/files.el
> @@ -729,7 +729,7 @@ The path separator is colon in GNU and GNU-like systems."
> (setq cd-path (or (parse-colon-path (getenv "CDPATH"))
> (list "./"))))
> (cd-absolute
> - (or (locate-file dir cd-path nil
> + (or (locate-file (decode-coding-string dir locale-coding-system) cd-path nil
> (lambda (f) (and (file-directory-p f) 'dir-ok)))
> (error "No such directory found via CDPATH environment variable"))))
> --8<---------------cut here---------------end--------------->8---
How come cd-path got a value that is a unibyte string? If it came
from getenv, then that function explicitly decodes the values.
IOW, please dig deeper and tell where did the unibyte string in
cd-path come from, because I don't see why would it be TRT to decode
it where you suggest; perhaps I'm missing something.
next prev parent reply other threads:[~2013-09-11 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 11:57 bug#15337: 24.3.50; [PATCH] cd to directory name with french accent fail from term/ansi-term Thierry Volpiatto
2013-09-11 13:51 ` Eli Zaretskii [this message]
2013-09-11 14:12 ` Thierry Volpiatto
2013-09-11 16:21 ` Eli Zaretskii
2013-09-12 5:11 ` Thierry Volpiatto
2013-09-12 15:33 ` Eli Zaretskii
2013-09-13 5:21 ` Thierry Volpiatto
2013-09-13 7:49 ` Eli Zaretskii
2013-09-13 11:29 ` Thierry Volpiatto
2013-09-13 11:59 ` Thierry Volpiatto
2013-09-13 13:25 ` Eli Zaretskii
2013-09-13 13:23 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y573ihzw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15337@debbugs.gnu.org \
--cc=thierry.volpiatto@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.