From: Kenichi Handa <handa@m17n.org>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: detecting charset of directories
Date: Sat, 21 Oct 2006 09:55:02 +0900 [thread overview]
Message-ID: <E1Gb58g-0000kE-00@etlken> (raw)
In-Reply-To: <20061020142038.99914.qmail@web51005.mail.yahoo.com> (message from Kevin Rodgers on Fri, 20 Oct 2006 07:20:38 -0700 (PDT))
In article <20061020142038.99914.qmail@web51005.mail.yahoo.com>, Kevin Rodgers <ihs_4664@yahoo.com> writes:
> > > Also, how can one ensure that `C-x m c CODING-SYSTEM g' will (1) have
> > > its intended effect and (2) persist its effect, for subsequent `g'
> > > commands?
> >
> > Sorry, I don't understand what you mean. Could you please
> > paraphrase it?
> [Sorry, `C-x m c ...' should have been `C-x C-m c ...']
> Let's say you are in a Dired buffer and you realize the coding system is
> wrong, so you try to re-read it with `C-x RET c CODING-SYSTEM g'. Does
> that work? If later you decide to simply run `g', does it use
> CODING-SYSTEM to re-read the directory?
> I think to make that work, dired-revert needs the same fix as
> dired-mode, namely:
> (set (make-local-variable 'file-name-coding-system)
> (or coding-system-for-read file-name-coding-system))
> Or perhaps that should be done later in just one place: dired-readin.
I basically agree with you, but as I don't know the code of
dired, I don't know which part is the right place to fix.
I'd like to ask maintainers of dired.el to work on it.
---
Kenichi Handa
handa@m17n.org
next parent reply other threads:[~2006-10-21 0:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061020142038.99914.qmail@web51005.mail.yahoo.com>
2006-10-21 0:55 ` Kenichi Handa [this message]
2006-10-21 12:05 ` detecting charset of directories Richard Stallman
2006-10-23 18:05 ` Kevin Rodgers
2006-10-24 17:42 ` Richard Stallman
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=E1Gb58g-0000kE-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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).