From: Stefan Monnier <monnier@iro.umontreal.ca>
To: mark.lillibridge@hp.com
Cc: emacs-devel@gnu.org
Subject: Re: Rmail and the raw-text coding system
Date: Fri, 14 Jan 2011 16:00:40 -0500 [thread overview]
Message-ID: <jwvwrm75hll.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <qmhhbdb2w0h.fsf@hp.com> (Mark Lillibridge's message of "Fri, 14 Jan 2011 10:14:06 -0800")
> It then decodes the BABYL message part:
> (unless (and coding-system
> (coding-system-p coding-system))
> (setq coding-system
> ;; Emacs 21.1 and later writes RMAIL files in emacs-mule, but
> ;; earlier versions did that with the current buffer's encoding.
> ;; So we want to favor detection of emacs-mule (whose normal
> ;; priority is quite low), but still allow detection of other
> ;; encodings if emacs-mule won't fit. The call to
> ;; detect-coding-with-priority below achieves that.
> (car (detect-coding-with-priority
> from to
> '((coding-category-emacs-mule . emacs-mule))))))
> (unless (memq coding-system
> '(undecided undecided-unix))
> (set-buffer-modified-p t) ; avoid locking when decoding
> (let ((buffer-undo-list t))
> (decode-coding-region from to coding-system))
> (setq coding-system last-coding-system-used))
> (set-buffer-modified-p modifiedp)
> (setq buffer-file-coding-system nil)
> (setq save-buffer-coding-system
> (or coding-system 'undecided))))
> This process leaves the buffer as a unibyte buffer.
The question for me is why did it choose raw-text here (which results
indeed in a unibyte buffer)? It should have been emacs-mule.
Stefan
next prev parent reply other threads:[~2011-01-14 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 18:14 Rmail and the raw-text coding system Mark Lillibridge
2011-01-14 21:00 ` Stefan Monnier [this message]
2011-01-15 0:06 ` Mark Lillibridge
2011-01-15 2:55 ` Stefan Monnier
2011-01-16 22:11 ` Mark Lillibridge
2011-01-17 19:19 ` Stefan Monnier
2011-01-17 22:31 ` Mark Lillibridge
2011-01-18 2:05 ` Stefan Monnier
2011-01-19 5:16 ` Mark Lillibridge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvwrm75hll.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=mark.lillibridge@hp.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.