Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
Subject: Re: contrib/ucs-tables.el obsolete for Emacs 21.3
Date: Sun, 11 May 2003 15:04:13 +0100	[thread overview]
Message-ID: <rzqel35shpe.fsf@albion.dl.ac.uk> (raw)
In-Reply-To: <84bryc8u6s.fsf@lucy.is.informatik.uni-duisburg.de> ( =?iso-8859-1?q?Kai_Gro=DFjohann's_message_of?= "Fri, 09 May 2003 09:18:03 +0200")

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> Didn't you say previously that ucs-tables.el would benefit from an
> improved utf-8.el?

I hope not.  ucs-tables provides tables that the utf-8 coding systems
(and others) use, not vice versa.

> The version that's now in the Gnus contrib directory has
> unify-8859-on-{de,en}coding-mode which need to be called.

Yes, but that's a feature.  Loading the file shouldn't invoke them.

> If the version that's now in Gnus' contrib directory is not the one
> you distributed,

I don't know what it is -- I haven't checked.  I was commenting on the
web page referenced and I didn't understand the recommendation to get
a version out of Emacs CVS specifically.

> Yes.  There was a recommendation to add the Gnus contrib directory to
> load-path.  Or even to move the files to the Gnus lisp directory.
>
> It's the wrong approach.

Perhaps someone could correct that if it's in the doc or add such
instructions for using anything that might appear in future Emacs
versions.  (I know that's difficult to tell in some cases, like
ucs-tables, so it's best to play safe.)



  reply	other threads:[~2003-05-11 14:04 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
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 [this message]
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=rzqel35shpe.fsf@albion.dl.ac.uk \
    --to=d.love@dl.ac.uk \
    /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).