From: Richard Stallman <rms@gnu.org>
Cc: juri@jurta.org, yamaoka@jpl.org, jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: Re: undo in loaddefs.el buffer
Date: Sun, 02 Jan 2005 19:58:50 -0500 [thread overview]
Message-ID: <E1ClGYc-00054q-2H@fencepost.gnu.org> (raw)
In-Reply-To: <200501021602.j02G23x08404@raven.dms.auburn.edu> (message from Luc Teirlinck on Sun, 2 Jan 2005 10:02:03 -0600 (CST))
As I already pointed out, the only non-obvious requirement is that one
way or the other they have to take care of undo correctly.
Yes. If you could make sure that this issue is clearly explained
in comments in the code, that would be a good thing.
It has been explained clearly in mail on this list,
but the explanation needs to be in the code to ensure people see it.
next prev parent reply other threads:[~2005-01-03 0:58 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 14:14 undo in loaddefs.el buffer Luc Teirlinck
2004-12-21 15:41 ` Luc Teirlinck
2004-12-22 4:31 ` Katsumi Yamaoka
2004-12-22 4:58 ` Katsumi Yamaoka
2004-12-23 0:01 ` Richard Stallman
2004-12-23 0:26 ` David Kastrup
2004-12-25 15:13 ` Richard Stallman
2004-12-24 1:45 ` Juri Linkov
2004-12-24 21:39 ` Luc Teirlinck
2004-12-26 9:14 ` Richard Stallman
2004-12-27 5:29 ` Luc Teirlinck
2004-12-27 22:35 ` Richard Stallman
2004-12-24 23:59 ` Luc Teirlinck
2004-12-25 15:12 ` Richard Stallman
2004-12-26 2:06 ` Luc Teirlinck
2004-12-26 2:32 ` Juri Linkov
2004-12-26 3:59 ` Luc Teirlinck
2004-12-27 2:40 ` Luc Teirlinck
2004-12-27 20:16 ` Juri Linkov
2004-12-28 4:57 ` Richard Stallman
2004-12-27 4:09 ` Richard Stallman
2004-12-26 16:15 ` Jan D.
2004-12-27 2:31 ` Luc Teirlinck
2004-12-27 10:21 ` Jan D.
2004-12-27 11:05 ` Jan D.
2004-12-27 22:35 ` Richard Stallman
2004-12-28 13:16 ` Jan D.
2004-12-28 20:57 ` Richard Stallman
2004-12-29 12:59 ` Jan D.
2004-12-28 5:03 ` Luc Teirlinck
2004-12-28 17:25 ` Richard Stallman
2004-12-29 2:07 ` Luc Teirlinck
2004-12-29 20:46 ` Richard Stallman
2004-12-30 1:14 ` Luc Teirlinck
2004-12-30 16:43 ` Richard Stallman
2004-12-31 1:54 ` Luc Teirlinck
2004-12-31 9:22 ` David Kastrup
2004-12-31 15:04 ` Luc Teirlinck
2005-01-01 5:25 ` Richard Stallman
2005-01-02 16:02 ` Luc Teirlinck
2005-01-03 0:58 ` Richard Stallman [this message]
2005-01-04 3:07 ` Luc Teirlinck
2005-01-04 17:00 ` Richard Stallman
2004-12-31 2:14 ` Luc Teirlinck
2004-12-30 5:06 ` Luc Teirlinck
2004-12-30 20:58 ` Richard Stallman
2004-12-27 18:05 ` Richard Stallman
2004-12-27 19:33 ` Jan D.
2004-12-28 4:57 ` Richard Stallman
2004-12-28 8:11 ` Jan D.
2004-12-28 21:05 ` Jason Rumney
2004-12-29 23:22 ` Jan D.
2004-12-27 4:09 ` Richard Stallman
2004-12-27 4:42 ` Luc Teirlinck
2004-12-26 2:43 ` Juri Linkov
2004-12-27 4:09 ` Richard Stallman
2005-01-04 9:05 ` Juri Linkov
2004-12-21 21:57 ` Kevin Rodgers
2004-12-22 0:17 ` Luc Teirlinck
2004-12-22 0:17 ` 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=E1ClGYc-00054q-2H@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=juri@jurta.org \
--cc=yamaoka@jpl.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).