From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15426@debbugs.gnu.org, politza@hochschule-trier.de
Subject: bug#15426: 24.3.50; Multibyte filenames and directory-files in unibyte buffer
Date: Sat, 21 Sep 2013 19:26:29 +0300 [thread overview]
Message-ID: <83mwn6jg3u.fsf@gnu.org> (raw)
In-Reply-To: <jwvy56q9n5b.fsf-monnier+emacsbugs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Andreas Politz <politza@hochschule-trier.de>, 15426@debbugs.gnu.org
> Date: Sat, 21 Sep 2013 12:06:10 -0400
>
> >> => ("/tmp/\301\203\300\204/." nil "/tmp/\303\204/." t)
> > "The minibuffer displays" is the key point here:
>
> No, the key point is that the two strings should be identical
But you don't see the strings, except after they are inserted into
some buffer.
> So the current-buffer's multibyte setting somehow affects the
> directory-files function. That's the bug.
Yes. But the way to show the bug is not to display the strings, but
to pass them to multibyte-string-p, or some other function whose
output's display cannot be possibly affected by multibyte-ness.
next prev parent reply other threads:[~2013-09-21 16:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 16:47 bug#15426: 24.3.50; Multibyte filenames and directory-files in unibyte buffer Andreas Politz
2013-09-20 17:46 ` Eli Zaretskii
2013-09-20 18:51 ` Andreas Politz
2013-09-20 19:08 ` Eli Zaretskii
2013-09-20 19:15 ` Stefan Monnier
2013-09-20 19:17 ` Eli Zaretskii
2013-09-20 20:56 ` Andreas Politz
2013-09-21 6:48 ` Eli Zaretskii
2013-09-21 9:35 ` Andreas Politz
2013-09-21 9:38 ` Andreas Politz
2013-09-21 11:59 ` Eli Zaretskii
2013-09-21 17:12 ` Andreas Politz
2013-09-21 18:53 ` Eli Zaretskii
2013-09-21 16:06 ` Stefan Monnier
2013-09-21 16:26 ` Eli Zaretskii [this message]
2013-09-22 1:29 ` Stefan Monnier
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=83mwn6jg3u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=15426@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=politza@hochschule-trier.de \
/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.