unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Can we add a check to see if user is using old or obsolete code?
Date: Fri, 21 Feb 2003 17:41:57 +0100	[thread overview]
Message-ID: <84heaxy4a2.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 5xfzqi4gik.fsf@kfs2.cua.dk

storm@cua.dk (Kim F. Storm) writes:

> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Actually, list-load-path-shadows is executed when you install Emacs.
>
> This requires that the conflicting files are named identically.  The
> problem with CUA is that the old and new files have different names,
> and the file name has actually changed three times, so this is
> unfortunately not a viable option for CUA.

Ayee!  I'm sorry.  As you can see, I know very little about CUA.
(But I like it :-)

> Also, the shadowing may easily be introduced later if the user
> modifies the load-path in his own .emacs file.

Sure.  But that's true for other packages, too.

>> IMHO it would be useful to make that output more prominent.
>> 
>> Doesn't Emacs include a versioned site-lisp directory in the
>> load-path by default?  So the installation instructions could suggest
>> to use that for such cases.  But it could be that the directory is in
>> load-path only for versions > 21.3.
>
> That only works if all existing users have installed the old cua
> package in those directories (provided they exist).  Not something
> I would rely on.

Of course.  I meant it as an additional suggestion.

> I now have a pretty good working solution for CUA based on
> eval-after-load.  I'll install it shortly.

Very good.  Sorry for the line-noise.
-- 
A preposition is not a good thing to end a sentence with.

  reply	other threads:[~2003-02-21 16:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 21:03 Can we add a check to see if user is using old or obsolete code? Kim F. Storm
2003-02-20 20:26 ` Stefan Monnier
2003-02-20 22:04   ` Kim F. Storm
2003-02-21 21:44   ` Richard Stallman
2003-02-21 23:20     ` Kim F. Storm
2003-02-22  0:28       ` Miles Bader
2003-02-22 22:37         ` Kim F. Storm
2003-02-22 17:54       ` Richard Stallman
2003-02-20 21:29 ` Kai Großjohann
2003-02-21  0:35   ` Kim F. Storm
2003-02-21 16:41     ` Kai Großjohann [this message]
2003-02-22  8:15   ` Richard Stallman
2003-02-23 11:06     ` Kai Großjohann
2003-02-24 16:38       ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84heaxy4a2.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).