unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aura Kelloniemi <kaura.dev@sange.fi>
To: Lars Ingebrigtsen <larsi@gnus.org>, Glenn Morris <rgm@gnu.org>
Cc: 22477@debbugs.gnu.org
Subject: bug#22477: 24.5; Dired does not work if file names contain newlines
Date: Tue, 16 Feb 2016 18:47:49 +0200	[thread overview]
Message-ID: <87oabghaa2.fsf@sange.fi> (raw)
In-Reply-To: <87a8n15f0f.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

 > Glenn Morris <rgm@gnu.org> writes:

 > > Aura Kelloniemi wrote:
 > >
 > >> 1. Create a file which contains a newline character in its name.
 > >
 > > If you like to do weird things like that, adding "-b" to
 > > dired-listing-switches helps.

 > The reason characters like that are problematic is because we're using
 > "ls" and then parsing the output, I guess?  Is there any particular
 > reason dired is still doing that?  Is the ls-lisp.el implementation
 > noticeably slower still?

According to the Emacs manual, ls-lisp is lacking some features that the ls
binary generally has.

What comes to special characters, ls supports many quoting styles, which Emacs
could implement (at least GNU ls supports them).

But the most portable, secure and configurable solution would be to enhance
(or rewrite) ls-lisp. It could support additional features which cannot be
very well implemented when using read ls, like allowing the user to control
the format of printed directory entries (I personally would like the file
permissions and other attributes to be shown on the right edge of the window
and the file name on the left, not the other way around as with 'ls -l').

-- 
Aura





      parent reply	other threads:[~2016-02-16 16:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-27 12:21 bug#22477: 24.5; Dired does not work if file names contain newlines Aura Kelloniemi
2016-01-27 16:40 ` Glenn Morris
2016-01-27 19:30   ` Aura Kelloniemi
2016-01-29  2:18     ` John Wiegley
2016-02-16  6:46   ` Lars Ingebrigtsen
2016-02-16  9:01     ` Andreas Schwab
2016-02-16 16:47     ` Aura Kelloniemi [this message]

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=87oabghaa2.fsf@sange.fi \
    --to=kaura.dev@sange.fi \
    --cc=22477@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rgm@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 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).