From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Strange behaviour with dired and UTF8
Date: Fri, 25 Apr 2003 15:20:05 +0200 [thread overview]
Message-ID: <84he8mogsa.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 200304241235.h3OCZdbL023178@stubby.bodenonline.com
"Jan D." <jan.h.d@swipnet.se> writes:
> But when trying to operate on a file, say opening it, I get
> "File no longer exists; type `g' to update Dired buffer"
> It seems that dired does not keep the original file name around, but
> tries to open with the display name representation of the file name.
Yeah, it seems that's how dired operates: it inserts the output from
"ls -l" into the buffer and then does operations on that buffer to
find the file name and suchlike.
Hm. And the "ls -l" output contains not only the file names, it also
contains the dates.
I was going to suggest to have dired-find-file bind
file-name-coding-system to the value used for reading the "ls -l"
output, but that will break when the date and the file names use
different encodings.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-25 13:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 11:43 Strange behaviour with dired and UTF8 Jan D.
2003-04-25 13:20 ` Kai Großjohann [this message]
2003-05-01 6:52 ` Kenichi Handa
2003-05-02 6:41 ` Kai Großjohann
2003-05-02 8:16 ` Jan D.
2003-05-02 8:56 ` Kenichi Handa
2003-05-02 9:59 ` Jan D.
2003-05-02 11:22 ` Kenichi Handa
2003-05-02 12:44 ` Jan D.
2003-05-03 15:03 ` Richard Stallman
2003-05-03 18:04 ` Jan D.
2003-05-05 14:32 ` Richard Stallman
2003-05-07 15:51 ` Jan D.
2003-05-07 16:09 ` Stefan Monnier
2003-05-09 11:19 ` Richard Stallman
2003-05-03 15:59 ` Stephen J. Turnbull
2003-05-03 17:59 ` Jan D.
2003-05-05 9:20 ` Kenichi Handa
2003-05-06 18:05 ` Jan D.
2003-05-07 1:08 ` Kenichi Handa
2003-05-07 15:43 ` Jan D.
2003-05-03 15:03 ` Richard Stallman
2003-05-03 18:11 ` Jan D.
2003-05-06 5:39 ` Kenichi Handa
2003-05-06 14:41 ` Richard Stallman
2003-05-07 15:49 ` Jan D.
2003-05-07 16:31 ` Stefan Monnier
2003-05-07 17:40 ` Jan D.
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=84he8mogsa.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).