Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: contrib/ucs-tables.el obsolete for Emacs 21.3
Date: Thu, 08 May 2003 09:31:31 -0400	[thread overview]
Message-ID: <m3brydtvik.fsf@heechee.beld.net> (raw)
In-Reply-To: <84r879lvds.fsf@lucy.is.informatik.uni-duisburg.de> ( =?iso-8859-1?q?Kai_Gro=DFjohann's_message_of?= "Thu, 08 May 2003 10:01:35 +0200")

On Thu, 08 May 2003, kai.grossjohann@gmx.net wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> 
>> Emacs 21.3 (and Emacs' CVS HEAD) comes with `ucs-tables.el'.  It
>> might cause problems if a user adds `.../gnus/contrib' to
>> `load-path'.
>>
>> Therefore, I guess we should remove `contrib/ucs-tables.el'.
> 
> I don't think so: what about people using Gnus on older versions of
> Emacs?  ucs-tables.el was put there for older versions, after all.
> 
> Maybe the documented treatment of the contrib directory should be
> different.  I think it's too simplistic to just add it to load-path.
> Maybe we should tell people to take the files they need and copy
> them to site-lisp or something.

Maybe contrib/ucs-tables.el should throw an error if emacs-version is
21.3 or greater?  The user could set gnus-load-contrib-ucs-tables if
they really, really want to use contrib/ucs-tables.el.

Another option is to rename it to ucs-tables-compat.el and make sure
nothing in it conflicts with the new ucs-tables.el.

Ted




  reply	other threads:[~2003-05-08 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 18:21 Reiner Steib
2003-05-07 23:41 ` Xavier Maillard
2003-05-08  8:01 ` Kai Großjohann
2003-05-08 13:31   ` Ted Zlatanov [this message]
2003-05-08 14:13     ` Kai Großjohann
2003-05-11 14:03     ` Dave Love
2003-05-08 23:09 ` Dave Love
2003-05-09  7:18   ` Kai Großjohann
2003-05-11 14:04     ` Dave Love
2003-05-12 15:39       ` Kai Großjohann

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=m3brydtvik.fsf@heechee.beld.net \
    --to=tzz@lifelogs.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.
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).