From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: fixing url-unhex-string for unicode/multi-byte charsets
Date: Sun, 08 Nov 2020 08:39:33 -0500 [thread overview]
Message-ID: <jwv1rh46ka4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20201108091216.xug4neeem7iuayhq@E15-2016.optimum.net> (Boruch Baum's message of "Sun, 8 Nov 2020 04:12:16 -0500")
>> > My guess is that his `file-name-coding-system` is set to something
>> > different from utf-8.
>
> That's correct, kind of. The setting isn't 'mine', its the emacs
> default. In both emacs 26.1 (debian) and emacs-snapshot (v28),
> file-name-coding-system defaults to nil, and
> default-file-name-coding-system defaults to utf-8-unix, so we have:
>
> file-name-coding-system => nil
> (default-value file-name-coding-system) => nil
> default-file-name-coding-system => utf-8-unix
This means your file name coding system *is* set to utf-8, so that
doesn't explain the problem.
> "The value type for this key is “string”; it SHOULD store the file
> name as the sequence of bytes produced by the file system, with
> characters escaped as in URLs (as defined by RFC 2396, section 2)."
Thanks. So we should indeed obey `file-name-coding-system`.
Stefan
next prev parent reply other threads:[~2020-11-08 13:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 7:47 fixing url-unhex-string for unicode/multi-byte charsets Boruch Baum
2020-11-06 8:02 ` Eli Zaretskii
2020-11-06 10:27 ` Boruch Baum
2020-11-06 12:04 ` Eli Zaretskii
2020-11-06 12:28 ` Boruch Baum
2020-11-06 13:34 ` Eli Zaretskii
2020-11-06 14:59 ` Stefan Monnier
2020-11-06 15:04 ` Eli Zaretskii
2020-11-08 9:12 ` Boruch Baum
2020-11-08 13:39 ` Stefan Monnier [this message]
2020-11-08 15:07 ` Eli Zaretskii
2020-11-06 14:38 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2020-11-06 7:54 Boruch Baum
2020-11-06 8:05 ` Eli Zaretskii
2020-11-06 10:34 ` Boruch Baum
2020-11-06 12:06 ` 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=jwv1rh46ka4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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.