From: Kenichi Handa <handa@etl.go.jp>
Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE, emacs-devel@gnu.org
Subject: Re: Run coding system auto-detection manually?
Date: Thu, 8 Aug 2002 21:45:04 +0900 (JST) [thread overview]
Message-ID: <200208081245.VAA19702@etlken.m17n.org> (raw)
In-Reply-To: <200208080701.g7871vx04204@wijiji.santafe.edu> (message from Richard Stallman on Thu, 8 Aug 2002 01:01:57 -0600 (MDT))
In article <200208080701.g7871vx04204@wijiji.santafe.edu>, Richard Stallman <rms@gnu.org> writes:
> So, for the case of a precious file, I think we must check
> VISIT (if that is string) instead of FILENAME in
> find-operation-coding-system. What do you think about the
> this patch?
> It seems right to me.
Ok, I've just installed it for RC and HEAD.
In article <vafhei54tyf.fsf@INBOX.auto.emacs.devel.tok.lucy.cs.uni-dortmund.de>, Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Gro�johann) writes:
> Will there be a way for Tramp to decide whether the fix is in Emacs
> already? If at all possible, it would be great if the same version
> of Tramp worked on older Emacsen, the new Emacs, and XEmacs.
How about this?
(let ((file-coding-system-alist '(("test" emacs-mule))))
(find-operation-coding-system 'write-region 0 0 "" nil "test"))
If it returns non-nil, the fix is in Emacs already.
---
Ken'ichi HANDA
handa@etl.go.jp
next prev parent reply other threads:[~2002-08-08 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 14:22 Run coding system auto-detection manually? Kai Großjohann
2002-08-05 4:48 ` Eli Zaretskii
2002-08-05 10:43 ` Kai Großjohann
2002-08-06 1:50 ` Richard Stallman
2002-08-06 9:48 ` Kai Großjohann
2002-08-07 14:23 ` Richard Stallman
2002-08-06 9:50 ` Kai Großjohann
2002-08-07 8:24 ` Kenichi Handa
2002-08-07 15:18 ` Kai Großjohann
2002-08-08 1:09 ` Kenichi Handa
2002-08-08 7:01 ` Richard Stallman
2002-08-08 8:48 ` Kai Großjohann
2002-08-08 12:45 ` Kenichi Handa [this message]
2002-08-08 13:12 ` Kai Großjohann
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=200208081245.VAA19702@etlken.m17n.org \
--to=handa@etl.go.jp \
--cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
--cc=emacs-devel@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).