From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Richard Stallman <rms@gnu.org>
Cc: help-gnu-emacs@gnu.org, npostavs@gmail.com
Subject: Re: Editing change groups
Date: Fri, 09 Nov 2018 15:14:24 +0200 [thread overview]
Message-ID: <83k1lmbdfz.fsf@gnu.org> (raw)
In-Reply-To: <87bm6ywhli.fsf@web.de> (message from Michael Heerdegen on Fri, 09 Nov 2018 13:39:05 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Fri, 09 Nov 2018 13:39:05 +0100
> Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
>
> Noam Postavsky <npostavs@gmail.com> writes:
>
> > Possible alternative approach with prior art in string-rectangle: fake
> > the change with overlays for preview, then it's easy to remove.
>
> Hmm - does that mean you also don't know how these change groups work
> ;-)
If we want an explanation how it should work, we should ask Richard
(CC'ed), because he designed and implemented this.
FWIW, the following does work for me as expected:
(catch 'foo
(atomic-change-group
(insert "a\n")
(insert "b\n")
(throw 'foo 1)))
If you evaluate this, you get 1 as the value, and nothing inserted
into the buffer.
next prev parent reply other threads:[~2018-11-09 13:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 7:52 Editing change groups Michael Heerdegen
2018-11-09 8:39 ` Joost Kremers
2018-11-09 11:58 ` Noam Postavsky
2018-11-09 12:39 ` Michael Heerdegen
2018-11-09 13:14 ` Eli Zaretskii [this message]
2018-11-09 13:12 ` Michael Heerdegen
2018-11-09 13:52 ` Stefan Monnier
2018-11-10 4:53 ` Michael Heerdegen
2018-11-10 13:15 ` Stefan Monnier
2018-11-10 16:23 ` Michael Heerdegen
2018-11-10 18:07 ` Stefan Monnier
2018-11-11 8:01 ` Michael Heerdegen
[not found] <mailman.3697.1541749970.1284.help-gnu-emacs@gnu.org>
2018-11-09 11:41 ` Ben Bacarisse
2018-11-09 12:10 ` Michael Heerdegen
[not found] ` <mailman.3721.1541765458.1284.help-gnu-emacs@gnu.org>
2018-11-09 13:36 ` Ben Bacarisse
2018-11-09 13:58 ` Michael Heerdegen
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=83k1lmbdfz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@gmail.com \
--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.
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).