From: Kenichi Handa <handa@m17n.org>
Cc: emacs-devel@gnu.org
Subject: Re: "coding" in file variable list not effective
Date: Wed, 7 Jan 2004 10:48:16 +0900 (JST) [thread overview]
Message-ID: <200401070148.KAA03549@etlken.m17n.org> (raw)
In-Reply-To: <C88E4100-405E-11D8-9520-000393861220@sage.com> (message from Sébastien Kirche on Tue, 6 Jan 2004 16:41:24 +0100)
In article <C88E4100-405E-11D8-9520-000393861220@sage.com>, Sébastien Kirche <sebastien.kirche@sage.com> writes:
> i have have a file that i am currently editing under osx (actually my
> .emacs) where i use the euro sign.
> So i save it with iso-latin-9-mac (iso-8859-15) encoding.
> To avoid typing the whole "C-x ret c iso-latin-9-mac C-x C-f filename"
> for further editing, i placed the setting "coding: iso-latin-9-mac" in
> my variable list at the end of file.
> I found that it has no effect : M-x describe-current-coding-system
> shows that i am still in iso-latin-1 which is my default file coding
> system.
> But if I place the setting in the first line between the -*- marks, the
> coding is used accordingly.
Thank you for the report. I've just installed the attached
fix.
---
Ken'ichi HANDA
handa@m17n.org
* international/mule.el (set-auto-coding): Fix for the case that
end-of-line is only CR.
*** mule.el.~1.196.~ Wed Dec 3 16:34:51 2003
--- mule.el Wed Jan 7 10:41:30 2004
***************
*** 1662,1692 ****
(setq coding-system nil)))))
;; If no coding: tag in the head, check the tail.
(when (and tail-found (not coding-system))
(goto-char tail-start)
! (search-forward "\n\^L" nil t)
(if (re-search-forward
! "^\\(.*\\)[ \t]*Local Variables:[ \t]*\\(.*\\)$" tail-end t)
! ;; The prefix is what comes before "local variables:" in its
! ;; line. The suffix is what comes after "local variables:"
;; in its line.
(let* ((prefix (regexp-quote (match-string 1)))
(suffix (regexp-quote (match-string 2)))
(re-coding
(concat
! "^" prefix
;; N.B. without the \n below, the regexp can
;; eat newlines.
! "[ \t]*coding[ \t]*:[ \t]*\\([^ \t\n]+\\)[ \t]*"
! suffix "$"))
(re-unibyte
(concat
! "^" prefix
! "[ \t]*unibyte[ \t]*:[ \t]*\\([^ \t\n]+\\)[ \t]*"
! suffix "$"))
(re-end
! (concat "^" prefix "[ \t]*End *:[ \t]*" suffix "$"))
! (pos (point)))
(re-search-forward re-end tail-end 'move)
(setq tail-end (point))
(goto-char pos)
--- 1662,1697 ----
(setq coding-system nil)))))
;; If no coding: tag in the head, check the tail.
+ ;; Here we must pay attention to the case that the end-of-line
+ ;; is just "\r" and we can't use "^" nor "$" in regexp.
(when (and tail-found (not coding-system))
(goto-char tail-start)
! (re-search-forward "[\r\n]\^L" nil t)
(if (re-search-forward
! "[\r\n]\\([^[\r\n]*\\)[ \t]*Local Variables:[ \t]*\\([^\r\n]*\\)[\r\n]"
! tail-end t)
! ;; The prefix is what comes before "local variables:" in its
! ;; line. The suffix is what comes after "local variables:"
;; in its line.
(let* ((prefix (regexp-quote (match-string 1)))
(suffix (regexp-quote (match-string 2)))
(re-coding
(concat
! "[\r\n]" prefix
;; N.B. without the \n below, the regexp can
;; eat newlines.
! "[ \t]*coding[ \t]*:[ \t]*\\([^ \t\r\n]+\\)[ \t]*"
! suffix "[\r\n]"))
(re-unibyte
(concat
! "[\r\n]" prefix
! "[ \t]*unibyte[ \t]*:[ \t]*\\([^ \t\r\n]+\\)[ \t]*"
! suffix "[\r\n]"))
(re-end
! (concat "[\r\n]" prefix "[ \t]*End *:[ \t]*" suffix
! "[\r\n]?"))
! (pos (1- (point))))
! (forward-char -1) ; skip back \r or \n.
(re-search-forward re-end tail-end 'move)
(setq tail-end (point))
(goto-char pos)
prev parent reply other threads:[~2004-01-07 1:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-06 15:41 "coding" in file variable list not effective Sébastien Kirche
2004-01-06 20:27 ` Eli Zaretskii
2004-01-07 9:43 ` Sébastien Kirche
2004-01-07 9:48 ` Sébastien Kirche
2004-01-07 1:48 ` Kenichi Handa [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=200401070148.KAA03549@etlken.m17n.org \
--to=handa@m17n.org \
--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).