Gnus development mailing list
 help / color / mirror / Atom feed
From: "François Pinard" <pinard@iro.umontreal.ca>
Cc: "Richard M. Stallman" <rms@gnu.org>
Subject: Re: Not a timetable
Date: 13 Aug 1998 15:44:41 -0400	[thread overview]
Message-ID: <oqr9yk3bva.fsf@icule.progiciels-bpi.ca> (raw)
In-Reply-To: Stainless Steel Rat's message of "13 Aug 1998 15:10:45 -0400"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> 
> Lars> Since Emacs 20.3 looks like it's going to be usable, and since there
> Lars> have been quite a lot of nice things introduced in (X)Emacs 20 over
> Lars> (X)Emacs 19 (lisp-wise), pgnus will ditch support for (X)Emacs 19.
> 
> That is a shame.  Regardless of FSF Emacs 20.3's usability, it will still
> have MULE.  That, in and of itself, is a big reason why many will not be
> downgrading from 19.34.

For a while, pretesting for Emacs 20.3, I have `export EMACS_UNIBYTE=1'
in `~/.bash_login', and this makes Emacs pretty usable for me.

But I do not have anymore those ultra-nice displays of Asian characters,
and *that* is a shame.  I do intend to stop using EMACS_UNIBYTE at some time,
but given my humble abilities, I just cannot pretest everything at once.

All this to say that you should not fear Emacs 20.3.  I honestly think it
has a lot of features well worth switching away from Emacs 19.  If MULE
works well, just take it as a gift.  If it creates problem, then stick
EMACS_UNIBYTE in your environment, until MULE gets fully dependable.

-- 
François Pinard                            mailto:pinard@iro.umontreal.ca
Join the free Translation Project!    http://www.iro.umontreal.ca/~pinard


  parent reply	other threads:[~1998-08-13 19:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-12 22:41 Lars Magne Ingebrigtsen
1998-08-13 15:17 ` Edward J. Sabol
1998-08-13 16:33   ` Lars Magne Ingebrigtsen
1998-08-14 11:22     ` Jan Vroonhof
1998-08-14 17:45       ` Lars Magne Ingebrigtsen
     [not found] ` <x7r9ykaea2.fsf@peorth.gweep.net>
1998-08-13 19:41   ` Lars Magne Ingebrigtsen
1998-08-13 20:25     ` Jake Colman
1998-08-13 20:42       ` William M. Perry
1998-08-14  7:27     ` Steinar Bang
1998-08-22 12:01       ` Dave Love
1998-08-13 19:44   ` François Pinard [this message]
     [not found]     ` <x7hfzgv8is.fsf@peorth.gweep.net>
1998-08-13 23:06       ` François Pinard
1998-08-14  7:28         ` Steinar Bang
     [not found]         ` <x7soize2td.fsf@peorth.gweep.net>
1998-08-17 12:53           ` Hrvoje Niksic
1998-08-17 13:47             ` Robert Bihlmeyer
1998-08-14 10:58       ` Kai Grossjohann
1998-08-14 13:00         ` luis fernandes
1998-08-14 18:15           ` SL Baur
     [not found]         ` <x7pve3e2md.fsf@peorth.gweep.net>
1998-08-22 12:24           ` Dave Love
     [not found]             ` <x7d89rrg0f.fsf@peorth.gweep.net>
1998-08-24 22:31               ` Dave Love
1998-08-24 22:58               ` Dave Love
1998-08-25  6:13                 ` Lars Magne Ingebrigtsen
     [not found]                 ` <x7r9y5di7z.fsf@peorth.gweep.net>
1998-08-26 18:12                   ` Dave Love
     [not found]                     ` <x7zpcq2ws8.fsf@peorth.gweep.net>
1998-08-27 20:51                       ` Dave Love
1998-08-25  1:15             ` SL Baur

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=oqr9yk3bva.fsf@icule.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=rms@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).