From: Junio C Hamano <gitster@pobox•com>
To: Teemu Likonen <tlikonen@iki•fi>
Cc: Reece Dunn <msclrhd@googlemail•com>,
Felipe Contreras <felipe.contreras@gmail•com>,
Sverre Rabbelier <srabbelier@gmail•com>,
Christian Couder <chriscool@tuxfamily•org>,
git@vger•kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx•de>
Subject: Re: Gnus content transfer encoding
Date: Sun, 05 Apr 2009 17:30:13 -0700 [thread overview]
Message-ID: <7vskkmoc8a.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87r60626c9.fsf_-_@iki.fi> (Teemu Likonen's message of "Sun, 05 Apr 2009 23:28:22 +0300")
Teemu Likonen <tlikonen@iki•fi> writes:
> On 2009-04-05 13:02 (-0700), Junio C Hamano wrote:
>
>> Reece Dunn <msclrhd@googlemail•com> writes:
>>> I think Junio is trying to learn base64 :)!
>>
>> I think that is what my Gnus/message-mode did. I do not know which
>> letter triggered it to decide it is UTF-8 to begin with, though. As
>> far as I am aware, I didn't type anything non-ascii in my message.
>
> You can customize the encoding decision mechanism, for example:
>
> (setq mm-body-charset-encoding-alist
> '((iso-8859-1 . 8bit)
> (utf-8 . 8bit)))
>
> For more info, see:
>
> C-h v mm-body-charset-encoding-alist RET
Interesting.
I have had these for a long time:
(setq mm-coding-system-priorities '(us-ascii iso-2022-jp utf-8 iso-8859-1))
(setq mm-content-transfer-encoding-defaults
'(("text/.*" 8bit)
("message/rfc822" 8bit)
("application/emacs-lisp" qp-or-base64)
("application/x-emacs-lisp" qp-or-base64)
("application/x-patch" qp-or-base64)
(".*" base64)))
I did not have any customization on my own to body-charset-encoding-alist
and C-h v gave me:
mm-body-charset-encoding-alist's value is
((iso-2022-jp . 7bit)
(iso-2022-jp-2 . 7bit)
(utf-16 . base64)
(utf-16be . base64)
(utf-16le . base64))
I'll have the following in my .emacs in addition to the coding-system-prio
and c-t-e-defaults I already have:
(setq mm-body-charset-encoding-alist
'((iso-2022-jp . 7bit)
(iso-2022-jp-2 . 7bit)
(iso-8859-1 . 8bit)
(utf-8 . 8bit)))
and will see what happens, but I wonder how this new one interacts with
the c-t-e-defaults.
Thanks.
next prev parent reply other threads:[~2009-04-06 0:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 20:59 [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1 Christian Couder
2009-04-05 10:17 ` Sverre Rabbelier
2009-04-05 14:41 ` Jeff King
2009-04-05 14:42 ` Sverre Rabbelier
2009-04-05 18:59 ` Junio C Hamano
2009-04-05 19:06 ` Sverre Rabbelier
2009-04-05 19:59 ` Jeff King
2009-04-05 20:05 ` Sverre Rabbelier
2009-04-05 19:19 ` Felipe Contreras
[not found] ` <87vdpi29a4.fsf@iki.fi>
2009-04-05 19:30 ` Felipe Contreras
2009-04-05 19:31 ` Reece Dunn
2009-04-05 20:02 ` Junio C Hamano
2009-04-05 20:25 ` Jeff King
2009-04-05 20:35 ` Sverre Rabbelier
2009-04-05 20:28 ` Gnus content transfer encoding (was: [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1) Teemu Likonen
2009-04-06 0:30 ` Junio C Hamano [this message]
2009-04-05 20:39 ` [PATCH 1/4] sha1-lookup: add new "sha1_pos" function to efficiently lookup sha1 Reece Dunn
2009-04-05 20:17 ` Jeff King
2009-04-05 20:34 ` Jay Soffian
2009-04-05 13:11 ` Johannes Schindelin
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=7vskkmoc8a.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=chriscool@tuxfamily$(echo .)org \
--cc=felipe.contreras@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=msclrhd@googlemail$(echo .)com \
--cc=srabbelier@gmail$(echo .)com \
--cc=tlikonen@iki$(echo .)fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox