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: Thu, 20 Feb 2003 22:29:24 +0100	[thread overview]
Message-ID: <84n0kq7ia3.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: 5xfzqibr72.fsf@kfs2.cua.dk

no-spam@cua.dk (Kim F. Storm) writes:

> Now, emacs 21.4 includes a newer version of CUA-mode, and the old
> version actually doesn't work very well with 21.4 (due to changes in
> the way the key-translation-map works).  So if a user upgrade from,
> say, 21.2 with the old version of cua.el in the load-path to release
> 21.4, CUA-mode will appear to be broken, but there is no indication
> that anything is wrong.

Actually, list-load-path-shadows is executed when you install Emacs.

But I think the output gets lost in lots of other output, so it
doesn't help that much.

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.
-- 
A preposition is not a good thing to end a sentence with.

  parent reply	other threads:[~2003-02-20 21:29 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 [this message]
2003-02-21  0:35   ` Kim F. Storm
2003-02-21 16:41     ` Kai Großjohann
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=84n0kq7ia3.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).