unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: snogglethorpe@gmail.com, emacs-devel@gnu.org,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	miles@gnu.org
Subject: Re: New undo element (fun . args)
Date: Mon, 31 Jan 2005 14:02:03 +0100	[thread overview]
Message-ID: <m3sm4hbvlg.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1CvaFP-0002xI-Rj@fencepost.gnu.org> (Richard Stallman's message of "Mon, 31 Jan 2005 07:01:39 -0500")

Richard Stallman <rms@gnu.org> writes:

>     100% agreement.  I even suggest we pass the BEG and END args to FUN.
>     I.e. basically keep the current setup, except require the first 2 args to be
>     BEG and END.
>
> That would be a nuisance; you would be unable to use existing functions
> for this purpose.
>
> By the way, note that we would have to change SES to handle the new
> format, if we change the format.

We have two othogonal issues:

a) the format of the undo entry

Here I guess we can agree on (apply DELTA BEG END FUN . ARGS)
And that FUN is called with ARGS only  (if necessary, the
BEG END etc. can be included explicitly in ARGS).

b) the undo-in-region support

I don't know, but in the case of ses, it may not make sense to have
undo in a region, and consequently may be quite hard to put something
sensible into DELTA, BEG and END.

For this purpose, I suppose that we have an alternate, short format
that omits the undo-in-region information:

    (apply FUN . ARGS)

For undo-in-region, this simply says that undo-in-region is not
supported beyond this element in the undo list.

It is trivial to distinguish the two formats - if second element is
an integer, it is the long format, otherwise it is the short format.

That makes it trivial to change ses.el.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2005-01-31 13:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30  0:47 New undo element (fun . args) Kim F. Storm
2005-01-30  1:24 ` Miles Bader
2005-01-30 15:07   ` Stefan Monnier
2005-01-30 17:22     ` Kim F. Storm
2005-01-30 18:11     ` Kim F. Storm
2005-01-31 12:01     ` Richard Stallman
2005-01-31 13:02       ` Kim F. Storm [this message]
2005-01-31 22:53         ` Kim F. Storm
2005-02-02  7:28           ` Richard Stallman
2005-02-02  7:28         ` Richard Stallman
2005-02-02 14:35           ` Stefan Monnier
2005-02-02 15:41             ` Kim F. Storm
2005-02-03 19:13               ` Richard Stallman
2005-02-04 15:40                 ` Kim F. Storm
2005-02-05 17:39                   ` Richard Stallman
2005-02-07  8:23                     ` Kim F. Storm
2005-02-07 20:51                       ` Richard Stallman
2005-02-09 21:50                         ` Kim F. Storm
2005-02-07 11:51                   ` Kim F. Storm
2005-02-07 12:25                     ` David Kastrup
2005-02-07 14:14                       ` Stefan Monnier
2005-02-08 11:47                       ` Richard Stallman
2005-02-08 11:46                     ` Richard Stallman
2005-02-08 12:53                       ` Kim F. Storm
2005-02-03 19:13             ` Richard Stallman
2005-01-31  0:19 ` 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=m3sm4hbvlg.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=snogglethorpe@gmail.com \
    /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).