From: "Braun Gábor" <braungb88@gmail.com>
To: 26061@debbugs.gnu.org
Subject: bug#26061: Consider merging with 26287 and 34405
Date: Thu, 21 Nov 2019 10:53:09 +0100 [thread overview]
Message-ID: <17493981.Zn75uerUAy@gabor> (raw)
In-Reply-To: <87wpbvwv47.fsf@luca>
This seems to be a candidate to merge with 26287 and 34405,
the latter two being already merged.
All three bugs have similar Lisp code
(catch ... (atomic-change-group ... (throw ...)))
producing an "unrelated state" error after undo.
Best wishes,
Gábor
next prev parent reply other threads:[~2019-11-21 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 18:01 bug#26061: 26.0.50; cancel-change-group fails with "unrelated state" error if used after an undo Andreas Politz
2019-11-21 9:53 ` Braun Gábor [this message]
2019-11-21 11:47 ` bug#26061: Consider merging with 26287 and 34405 Lars Ingebrigtsen
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=17493981.Zn75uerUAy@gabor \
--to=braungb88@gmail.com \
--cc=26061@debbugs.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).