From: Doug Lewan <dougl@shubertticketing.com>
To: Whitfield Diffie <whitfield.diffie@gmail.com>,
"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: Newlines in file names
Date: Tue, 11 Dec 2012 14:02:05 +0000 [thread overview]
Message-ID: <155DEC68569B714B86C2C7075F5EDA9828DF1C50@DAKIYA1.pegasus.local> (raw)
In-Reply-To: <CAF+O-CXUO2RzKGMHh7dWsAHsucJtOxJkNAgbipdy=qgW3LMGkQ@mail.gmail.com>
What version of emacs are you using?
I don't have such problems in version 24, but I do remember dired using a regular expression that wouldn't match such uncommon names in earlier versions.
,Douglas
Douglas Lewan
Shubert Ticketing
(201) 489-8600 ext 224
When I do good, I feel good. When I do bad, I feel bad and that's my religion. - Abraham Lincoln
> -----Original Message-----
> From: help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org
> [mailto:help-gnu-emacs-bounces+dougl=shubertticketing.com@gnu.org] On
> Behalf Of Whitfield Diffie
> Sent: Monday, 2012 December 10 14:48
> To: help-gnu-emacs@gnu.org
> Subject: Newlines in file names
>
> Question: How do you translate a filename containing a newline to one
> containing
> a \n without getting a \\n.
>
> Problem: Create a directory ``test''.
>
> In the directory create a file with (call-process "touch" nil
> nil nil "Icon\n").
> This file's name has five characters of which the last is a
> newline. (Such files
> appear in some downloads.)
>
> This directory now appears as
>
> /Users/diffie/test:
> total used in directory 0 available 327738716
> drwxr-xr-x 3 diffie staff 102 Dec 10 11:04 .
> drwxr-xr-x 25 diffie staff 850 Dec 10 11:03 ..
> -rw-r--r-- 1 diffie staff 0 Dec 9 10:01 Icon
>
> Place the cursor on the line with the Icon file and type
>
> <esc>: (file-exists-p (dired get filename))
>
> The response is ``nil''.
>
> Make the buffer writable with <ctrl-x><ctrl-q> and edit the
> name by hand to ``Icon\n''. Type
>
> <esc>: (file-exists-p (dired-get-filename))
>
> The response is now ``t''.
>
> Type g to revert the buffer and the name returns to being
> ``Icon''.
>
> Place the cursor on the line with the Icon file again and type
>
> M+x
>
> The entire file line disappears leaving only . and .. in the
> directory.
>
> Type g to revert the buffer and the line reappears but the
> file
> has not become executable.
>
> Edit the filename as before and repeat the attempt to make it
> executable.
>
> Now the file line becomes
>
> -rwxr-xr-x 1 diffie staff 0 Dec 9 10:01 Icon
>
> The file has become executable but its name has returned to
> being
> ``Icon'', lacks the newline character.
>
> Objective: Repair dired so that filenames containing newlines are
> displayed
> with \n in place of newline characters (and \r in place of
> carriage
> returns).
>
> I have tried setting print-escape-newlines to t and recoding
> filename with buffer-file-coding-system, file-name-coding-
> system,
> and default-file-name-coding-system, without success.
>
>
> Whit
next prev parent reply other threads:[~2012-12-11 14:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 19:47 Newlines in file names Whitfield Diffie
2012-12-11 14:02 ` Doug Lewan [this message]
2012-12-11 15:19 ` Whitfield Diffie
2012-12-11 16:34 ` Doug Lewan
[not found] <mailman.14995.1355169707.855.help-gnu-emacs@gnu.org>
2012-12-10 22:53 ` Barry Margolin
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=155DEC68569B714B86C2C7075F5EDA9828DF1C50@DAKIYA1.pegasus.local \
--to=dougl@shubertticketing.com \
--cc=help-gnu-emacs@gnu.org \
--cc=whitfield.diffie@gmail.com \
/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.
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).