From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: kzhr@d1.dion.ne.jp, michael.albinus@gmx.de, emacs-devel@gnu.org
Subject: Re: Multibyte and unibyte file names
Date: Thu, 24 Jan 2013 19:02:22 +0200 [thread overview]
Message-ID: <83wqv2ldk1.fsf@gnu.org> (raw)
In-Reply-To: <jwv1udby611.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: emacs-devel@gnu.org, Kazuhiro Ito <kzhr@d1.dion.ne.jp>,
> Michael Albinus <michael.albinus@gmx.de>
> Date: Wed, 23 Jan 2013 16:09:18 -0500
>
> I think that for w32 it makes sense to try and always decode file names
> before returning them to Elisp:
> Most file names passed to Elisp primitives are derived from file names
> returned by Elisp primitives, so if Emacs decodes all the file names it
> returns to Elisp, we can expect to see *very* few encoded file names
> passed to Elisp primitives.
So you are saying that each primitive should detect unibyte file names
it gets as arguments and DECODE_FILE them right away? We would also
need to modify all the C code that calls the primitives directly and
passes them encoded file names. Did I understand your suggestion
correctly?
next prev parent reply other threads:[~2013-01-24 17:02 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:45 Multibyte and unibyte file names Eli Zaretskii
2013-01-23 18:08 ` Paul Eggert
2013-01-23 19:04 ` Eli Zaretskii
2013-01-23 23:38 ` Paul Eggert
2013-01-23 19:42 ` Michael Albinus
2013-01-23 20:05 ` Eli Zaretskii
2013-01-23 20:58 ` Michael Albinus
2013-01-24 16:37 ` Eli Zaretskii
2013-01-23 21:09 ` Stefan Monnier
2013-01-24 17:02 ` Eli Zaretskii [this message]
2013-01-24 18:25 ` Stefan Monnier
2013-01-24 18:38 ` Eli Zaretskii
2013-01-25 0:06 ` Stefan Monnier
2013-01-25 7:37 ` Eli Zaretskii
2013-01-25 11:36 ` Stefan Monnier
2013-01-25 20:31 ` Eli Zaretskii
2013-01-25 22:28 ` Stefan Monnier
2013-01-26 10:54 ` Eli Zaretskii
2013-01-26 11:34 ` Stefan Monnier
2013-01-26 13:16 ` Eli Zaretskii
2013-01-26 22:11 ` Stefan Monnier
2013-01-27 7:03 ` Eli Zaretskii
2013-01-27 8:46 ` Andreas Schwab
2013-01-27 9:40 ` Eli Zaretskii
2013-01-28 1:55 ` Stefan Monnier
2013-01-28 14:44 ` Eli Zaretskii
2013-01-28 15:21 ` Stefan Monnier
2013-02-02 17:19 ` Eli Zaretskii
2013-01-26 13:20 ` Stephen J. Turnbull
2013-01-26 3:04 ` Stephen J. Turnbull
2013-01-26 11:27 ` Eli Zaretskii
2013-01-26 13:03 ` Stephen J. Turnbull
2013-01-26 13:36 ` Eli Zaretskii
2013-01-26 16:26 ` Paul Eggert
2013-01-26 18:30 ` Stephen J. Turnbull
2013-01-26 17:10 ` Stephen J. Turnbull
2013-01-26 17:33 ` Eli Zaretskii
2013-01-26 18:06 ` Paul Eggert
2013-01-26 18:20 ` Eli Zaretskii
2013-01-26 18:56 ` Stephen J. Turnbull
2013-01-26 21:40 ` Stefan Monnier
2013-01-26 21:44 ` Stefan Monnier
2013-01-27 6:14 ` Eli Zaretskii
2013-01-26 16:05 ` Richard Stallman
2013-01-26 17:57 ` Stephen J. Turnbull
2013-01-26 22:16 ` Stefan Monnier
2013-01-24 10:00 ` Michael Albinus
2013-01-24 16:40 ` 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=83wqv2ldk1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kzhr@d1.dion.ne.jp \
--cc=michael.albinus@gmx.de \
--cc=monnier@IRO.UMontreal.CA \
/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).