From: martin rudalics <rudalics@gmx.at>
To: "Mattias Engdegård" <mattiase@acm.org>, 37700@debbugs.gnu.org
Subject: bug#37700: 27.0.50; undo mouse-drag-and-drop-region ineffective
Date: Fri, 11 Oct 2019 14:19:07 +0200 [thread overview]
Message-ID: <dc143df4-981e-6965-8e3d-20fb80337231@gmx.at> (raw)
In-Reply-To: <3311689D-B1DF-4BAC-86BA-E3D2C6D2ECF1@acm.org>
> Undoing mouse-drag-and-drop-region doesn't work:
>
> 1. (setq mouse-drag-and-drop-region t)
> 2. mark a region
> 3. use the mouse to drag the region elsewhere
> 4. Undo (twice)
>
> Result: the dragged text disappears from its destination, but does not reappear where it was dragged from.
> Instead, we get the "No further undo information for region" error.
>
> The action can be undone by moving point and backing up a different undo branch a few steps, but that is hardly ideal.
I suppose this the effect of undo working on the active region only.
A very nasty invention. Try deactivating the region right after 3.
martin
next prev parent reply other threads:[~2019-10-11 12:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 11:51 bug#37700: 27.0.50; undo mouse-drag-and-drop-region ineffective Mattias Engdegård
2019-10-11 12:19 ` martin rudalics [this message]
2019-10-11 12:51 ` Mattias Engdegård
2019-10-11 14:43 ` Eli Zaretskii
2019-10-11 17:18 ` Mattias Engdegård
2019-10-11 18:36 ` Eli Zaretskii
2019-10-11 18:51 ` Eli Zaretskii
2019-10-12 8:24 ` martin rudalics
2019-10-11 18:57 ` Eli Zaretskii
2019-10-11 18:26 ` martin rudalics
2019-10-11 19:12 ` Eli Zaretskii
2019-10-12 1:55 ` Tak Kunihiro
2019-10-12 8:24 ` martin rudalics
2019-10-12 16:42 ` Mattias Engdegård
2019-10-12 17:17 ` Eli Zaretskii
2019-10-12 17:53 ` Eli Zaretskii
2019-10-16 15:27 ` Mattias Engdegård
2019-10-26 10:15 ` Eli Zaretskii
2019-10-28 20:01 ` Stefan Monnier
2019-10-30 19:09 ` Mattias Engdegård
2019-10-30 19:56 ` Stefan Monnier
2019-10-31 11:00 ` Mattias Engdegård
2019-10-31 14:45 ` Eli Zaretskii
2019-10-31 16:04 ` Mattias Engdegård
2019-10-31 16:10 ` Eli Zaretskii
2019-10-31 16:47 ` Mattias Engdegård
2019-10-11 12:26 ` Eli Zaretskii
2019-10-11 12:53 ` Mattias Engdegård
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=dc143df4-981e-6965-8e3d-20fb80337231@gmx.at \
--to=rudalics@gmx.at \
--cc=37700@debbugs.gnu.org \
--cc=mattiase@acm.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).