all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: mattiase@acm.org, grindeg@yandex.ru
Cc: 36085@debbugs.gnu.org
Subject: bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text
Date: Sun, 09 Jun 2019 08:22:09 +0300	[thread overview]
Message-ID: <83h88zcozi.fsf@gnu.org> (raw)
In-Reply-To: <83o938nl9j.fsf@gnu.org> (message from Eli Zaretskii on Sat, 08 Jun 2019 18:34:48 +0300)

> Date: Sat, 08 Jun 2019 18:34:48 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: grindeg@yandex.ru, 36085@debbugs.gnu.org
> 
> Indeed, the hard part is to distinguish between \nnn an octal escape
> and the literal string "\nnn".  That difficulty is one reason why
> gdb-mi.el performs a similar decoding only as an opt-in optional
> behavior.

Here's an idea for making this command work with non-ASCII file names:
do NOT add "-ls" to the 'find' command line, then in the process
filter function call file-attributes on each file name we receive from
'find', and format the result according to Dired convention before
inserting it into the buffer.

Any takers?





  reply	other threads:[~2019-06-09  5:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04  3:43 bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text Nikita
2019-06-04 11:44 ` bug#36085: Screenshots for th bug Никита Никита
2019-06-08 12:20 ` bug#36085: 26.2; find-dired octal escapes instead of Cyrillic text Eli Zaretskii
2019-06-09 12:34   ` Tomas Nordin
2019-06-09 12:51     ` Eli Zaretskii
2019-06-08 15:14 ` Mattias Engdegård
2019-06-08 15:34   ` Eli Zaretskii
2019-06-09  5:22     ` Eli Zaretskii [this message]
2019-06-09  9:08       ` Mattias Engdegård
2019-06-09 10:57         ` Eli Zaretskii
2019-06-09 12:39           ` Mattias Engdegård
2019-06-09 12:49             ` Eli Zaretskii
2022-03-13  6:05     ` Visuwesh

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=83h88zcozi.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=36085@debbugs.gnu.org \
    --cc=grindeg@yandex.ru \
    --cc=mattiase@acm.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.