From: Juri Linkov <juri@jurta.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 10056@debbugs.gnu.org
Subject: bug#10056: 24.0.91; Mark deactivation
Date: Sun, 09 Dec 2012 02:29:27 +0200 [thread overview]
Message-ID: <87pq2kvzix.fsf@mail.jurta.org> (raw)
In-Reply-To: <F780B46B05284D9BB1A4574E54947D43@us.oracle.com> (Drew Adams's message of "Sat, 8 Dec 2012 16:00:36 -0800")
> Let's try first to fix (only) the commands that Dani
> or others report such have a problem.
That means adding `(setq deactivate-mark t)' to some functions,
but this is not user-configurable. Maybe like delsel.el puts
the property `delete-selection' on some functions, we should use
the property `deactivate-mark', e.g.:
(put 'fill-paragraph 'deactivate-mark t)
next prev parent reply other threads:[~2012-12-09 0:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 20:06 bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark Dani Moncayo
2011-11-15 20:15 ` Dani Moncayo
2011-11-15 20:36 ` Dani Moncayo
2011-11-15 20:18 ` Dani Moncayo
2011-11-21 6:30 ` Chong Yidong
2012-06-05 7:44 ` Dani Moncayo
2012-07-28 19:01 ` Dani Moncayo
2012-07-29 4:45 ` Chong Yidong
2012-07-29 9:46 ` Dani Moncayo
2012-07-29 4:50 ` Chong Yidong
2012-07-29 10:01 ` Dani Moncayo
2012-08-01 21:17 ` Alan Mackenzie
2012-08-01 22:07 ` Dani Moncayo
2012-08-03 21:47 ` Alan Mackenzie
2012-09-08 20:21 ` Stefan Monnier
2012-09-09 20:20 ` Dani Moncayo
2012-09-11 14:42 ` Bastien
2012-12-05 8:04 ` bug#10056: 24.0.91; Mark deactivation Dani Moncayo
2012-12-08 10:09 ` Dani Moncayo
2012-12-08 23:03 ` Juri Linkov
2012-12-09 0:00 ` Drew Adams
2012-12-09 0:29 ` Juri Linkov [this message]
2012-12-09 3:21 ` Drew Adams
2012-12-09 9:07 ` Dani Moncayo
2013-01-25 12:34 ` Dani Moncayo
2013-01-25 17:41 ` Drew Adams
2013-01-25 19:07 ` Dani Moncayo
2013-01-25 19:34 ` Drew Adams
2013-01-25 19:01 ` Stefan Monnier
2022-04-26 13:50 ` bug#10056: 24.0.91; `copy-to-register' does not deactivate the mark 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=87pq2kvzix.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=10056@debbugs.gnu.org \
--cc=drew.adams@oracle.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).