[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Incompatible change without "warning"
From: |
Luc Teirlinck |
Subject: |
Re: Incompatible change without "warning" |
Date: |
Sun, 1 May 2005 21:28:23 -0500 (CDT) |
Richard Stallman wrote:
So people using the Elisp manual for reference are
likely to have kept using executing-macro. Do we still want to remove
it given that?
They would still have gotten the warning messages when compiling their
code. However, it looks like a fair variety of programs have reasons
to look at this variable.
So we can put in a defvaralias call.
I replaced the make-obsolete-variable with a
define-obsolete-variable-alias, which is equivalent.
Sincerely,
Luc.
- Re: Incompatible change without "warning", Nick Roberts, 2005/05/01
- Re: Incompatible change without "warning", Richard Stallman, 2005/05/01
- Re: Incompatible change without "warning", Richard Stallman, 2005/05/01
- Re: Incompatible change without "warning", Nick Roberts, 2005/05/01
- Re: Incompatible change without "warning", Richard Stallman, 2005/05/02
- Re: Incompatible change without "warning", David Kastrup, 2005/05/02
- Re: Incompatible change without "warning", Nick Roberts, 2005/05/02
- Re: Incompatible change without "warning", Luc Teirlinck, 2005/05/03
- Re: Incompatible change without "warning", David Kastrup, 2005/05/03
- Re: Incompatible change without "warning", Richard Stallman, 2005/05/04
- Re: Incompatible change without "warning", Richard Stallman, 2005/05/03
- Re: Incompatible change without "warning", Richard Stallman, 2005/05/02