Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: "Miles Bader" <miles@gnu.org>
Cc: ding@gnus.org
Subject: Re: Emacs unicode merge changes to Gnus
Date: Wed, 20 Feb 2008 20:34:20 +0100	[thread overview]
Message-ID: <v9hcg3cthf.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <fc339e4a0802191629m781597f8o8f756d43321fbb76@mail.gmail.com> (Miles Bader's message of "Wed, 20 Feb 2008 09:29:12 +0900")

On Wed, Feb 20 2008, Miles Bader wrote:

> On Feb 16, 2008 9:39 AM, Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>> >   1) Should gnus write the cookie?   (obviously yes, I think)
>> >
>> >   2) Should Gnus stop forcing the coding system when it reads the file?
>> >      (i.e., should Gnus let coding: do its job)
>> >
>> >   3) Should Gnus switch to utf-8-emacs as the default coding system for
>> >      writing files?
>>
>> Sounds reasonable.  Please apply (1) and (2).
>
> ... However I now notice that Gnus has used "utf-8-emacs" by default
> for a _long_ time, if it's supported!!  Here's the ChangeLog entry:
>
> 2003-04-24  Dave Love  <fx@gnu.org>
>
>         * mm-util.el (mm-make-temp-file, mm-insert-byte): New.
>         (mm-auto-save-coding-system): Consider utf-8-emacs.
>
> That means anybody who's been running the unicode branch (a lot of
> people), or the trunk (since the branch was merged) has had their Gnus
> files encoding using utf-8-emacs for quite a while...
>
> So I'm not sure what to do, really...  It seems like a step backward
> (and perhaps dangerous) to explicitly change that to emacs-mule.

Okay, let's use utf-8-emacs.

We should warn about the incompatibility in GNUS-NEWS (info "(gnus)No
Gnus") and emacs/etc/NEWS.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  reply	other threads:[~2008-02-20 19:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06  2:30 Miles Bader
2008-02-06 22:10 ` Reiner Steib
2008-02-06 22:44   ` Miles Bader
2008-02-06 23:06     ` Reiner Steib
2008-02-06 23:22       ` Miles Bader
2008-02-06 23:27   ` Katsumi Yamaoka
2008-02-07  8:24     ` Reiner Steib
2008-02-07  9:19       ` Katsumi Yamaoka
2008-02-07 10:24         ` Miles Bader
2008-02-15  0:42           ` Miles Bader
2008-02-15 17:30             ` Reiner Steib
2008-02-15 21:59               ` Miles Bader
2008-02-16  0:39                 ` Reiner Steib
2008-02-20  0:29                   ` Miles Bader
2008-02-20 19:34                     ` Reiner Steib [this message]
2008-02-26 21:17                       ` Reiner Steib
2008-02-20  0:30                   ` Miles Bader
2008-02-20 19:23                     ` Reiner Steib
2008-02-23 18:07                       ` Reiner Steib
2008-02-24  1:41                         ` Miles Bader

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=v9hcg3cthf.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=miles@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.
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 NNTP newsgroup(s).