From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-devel@gnu.org, ding@gnus.org, Kenichi Handa <handa@m17n.org>
Subject: Gnus compatibility with Emacs 23 (unicode branch) (was: gnus doesn't encode non-ascii attachment filenames)
Date: Tue, 14 Feb 2006 11:59:21 +0100 [thread overview]
Message-ID: <v9pslqcik6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: buo64ni392v.fsf@dhapc248.dev.necel.com
On Tue, Feb 14 2006, Miles Bader wrote:
> Kenichi Handa <handa@m17n.org> writes:
>> For Emacs 23, we can have a better/simpler fix. But, could someone
>> tell me the maintenance policy of Gnus codes? Should we modify codes
>> in cvs HEAD so that it works also with emacs-unicode-2 (perhaps with
>> version check here and there)?
(Or feature check, if possible.) But please don't break compatibility
with Emacs 21 and Emacs 20.7 [1].
>> Or, should we directly modify codes in cvs emacs-unicode-2?
>
> It seems to me better keep the code in both branches the same, if
> possible.
>
> Changes to Emacs 22 will be propagated to Gnus 5.10 and the Gnus
> development branch (No Gnus); as people may wish to use the Gnus
> development branch with Emacs 23, it would be a good thing to avoid
> changes which are only in the Emacs 23 sources.
I agree. AFAICS, Dave Love already installed some changes to make
Gnus work with emacs-unicode-2 (often referred as "Emacs 22" [2] in
code comments). But there are probably also some open issues:
E.g. "Wrong for Emacs 23" in `message-fix-before-sending'.
Bye, Reiner.
[1] We are currently discussing if we should drop Emacs 20.7
compatibility also for the stable branch (Gnus 5.10, v5-10) as we
have already done for the development version of Gnus (No Gnus).
[2] We should probably check out the before-renaming-to-emacs-22
version, look for strings like "Emacs 22" and replace the comments
with "Emacs 23 (unicode)"
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-02-14 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 7:00 gnus doesn't encode non-ascii attachment filenames Zhang Wei
[not found] ` <E1F8oEg-0007Q6-Vf@fencepost.gnu.org>
2006-02-14 1:25 ` Zhang Wei
2006-02-14 2:13 ` Kenichi Handa
2006-02-14 3:36 ` Miles Bader
2006-02-14 10:59 ` Reiner Steib [this message]
2006-02-23 21:03 ` Gnus compatibility with Emacs 23 (unicode branch) Reiner Steib
2006-03-23 5:58 ` gnus doesn't encode non-ascii attachment filenames Kenichi Handa
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=v9pslqcik6.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.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 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.