From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org, rms@gnu.org, monnier@iro.umontreal.ca
Subject: Re: Incompatible change without "warning"
Date: Sun, 1 May 2005 10:18:36 -0500 (CDT) [thread overview]
Message-ID: <200505011518.j41FIa323379@raven.dms.auburn.edu> (raw)
In-Reply-To: <17012.57973.677404.342871@farnswood.snap.net.nz> (message from Nick Roberts on Mon, 2 May 2005 02:06:45 +1200)
Nick Roberts wrote:
I wasn't sure how to remove executing-macro as it is a builtin variable:
Please wait before removing this, until the following has been considered.
Richard Stallman wrote:
19.34
executing-macro
Please delete that too.
I believe that Richard may have been unaware of the fact that, until
very recently, executing-macro and _not_ executing-kbd-macro were
documented in the Elisp manual. This only got changed in August 2004
in CVS. (Actually, I changed one occurrence of executing-kbd-macro
just moments ago.) 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?
Sincerely,
Luc.
next prev parent reply other threads:[~2005-05-01 15:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 14:48 Incompatible change without "warning" Frank Schmitt
2005-04-19 19:09 ` Eli Zaretskii
2005-04-19 20:53 ` Nick Roberts
2005-04-19 21:25 ` Stefan Monnier
2005-04-19 22:10 ` Kevin Rodgers
2005-04-20 14:57 ` Richard Stallman
2005-04-20 23:21 ` Nick Roberts
2005-04-21 14:17 ` Lute Kamstra
2005-04-21 22:35 ` Nick Roberts
2005-04-22 9:46 ` Lute Kamstra
2005-04-22 21:32 ` Nick Roberts
2005-04-23 7:17 ` Lute Kamstra
2005-04-23 7:31 ` David Kastrup
2005-04-23 19:25 ` Lute Kamstra
2005-04-23 8:10 ` Nick Roberts
2005-04-23 9:44 ` Eli Zaretskii
2005-04-23 19:27 ` Lute Kamstra
2005-04-21 19:56 ` Richard Stallman
2005-04-21 23:14 ` Nick Roberts
2005-04-21 23:56 ` Lute Kamstra
2005-04-23 16:15 ` Richard Stallman
2005-04-26 9:15 ` Nick Roberts
2005-04-26 21:06 ` Stefan Monnier
2005-04-26 21:35 ` Nick Roberts
2005-04-26 21:45 ` Stefan Monnier
[not found] ` <20050430231856.CE9369F511@mirror.positive-internet.com>
2005-05-01 3:50 ` Nick Roberts
2005-05-01 12:07 ` Richard Stallman
2005-05-01 14:06 ` Nick Roberts
2005-05-01 15:18 ` Luc Teirlinck [this message]
2005-05-01 23:39 ` Richard Stallman
2005-05-02 2:28 ` Luc Teirlinck
2005-05-01 18:57 ` Richard Stallman
2005-05-01 21:18 ` Luc Teirlinck
2005-05-01 18:57 ` Richard Stallman
2005-05-01 18:57 ` Richard Stallman
2005-05-01 22:43 ` Nick Roberts
2005-05-02 7:38 ` David Kastrup
2005-05-02 22:55 ` Nick Roberts
2005-05-03 4:31 ` Luc Teirlinck
2005-05-03 7:17 ` David Kastrup
2005-05-04 22:04 ` Richard Stallman
2005-05-03 17:12 ` Richard Stallman
2005-05-02 23:40 ` Richard Stallman
2005-05-02 15:21 ` Richard Stallman
2005-04-20 14:57 ` Richard Stallman
2005-04-19 21:35 ` Nick Roberts
2005-04-20 23:14 ` Luc Teirlinck
2005-04-21 0:56 ` Nick Roberts
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=200505011518.j41FIa323379@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
/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).