unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tak Kunihiro <homeros.misasa@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
	37700@debbugs.gnu.org, tkk@misasa.okayama-u.ac.jp
Subject: bug#37700: 27.0.50; undo mouse-drag-and-drop-region ineffective
Date: Sat, 12 Oct 2019 10:55:23 +0900	[thread overview]
Message-ID: <m28spq20dw.fsf@misasa.okayama-u.ac.jp> (raw)
In-Reply-To: <5be797bb-9d6b-cebe-edf4-21b4a5944595@gmx.at> (martin rudalics's message of "Fri, 11 Oct 2019 20:26:23 +0200")

> But I also faintly remember a discussion with the author of
> 'mouse-drag-and-drop-region' on whether it is a good idea to activate
> the mark after dropping - IIRC he did have some argument in favor of
> it.  Maybe it would be easier to add an option for not activating the
> region when dropping than adding one for 'undo'.

On revision of writing, I often want to move a sentence around to fit
into right place, without loosing the sentence from sight.  Most of the
time I cannot relocate the sentence to the best place by single
drag-and-drop operation thus I want to maintain region active.

I found that I did not notice problem pointed by Mattias because I
assign `undo' by `redo+.el' to C-/.  I agree that undo behavior by C-/
with Emacs -Q is inconvenient!

https://www.emacswiki.org/emacs/redo+.el





  parent reply	other threads:[~2019-10-12  1:55 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
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 [this message]
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=m28spq20dw.fsf@misasa.okayama-u.ac.jp \
    --to=homeros.misasa@gmail.com \
    --cc=37700@debbugs.gnu.org \
    --cc=mattiase@acm.org \
    --cc=rudalics@gmx.at \
    --cc=tkk@misasa.okayama-u.ac.jp \
    /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).