From: Helmut Eller <eller.helmut@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 16752@debbugs.gnu.org
Subject: bug#16752: 24.3.50; pp-to-string deactivates mark
Date: Tue, 18 Feb 2014 09:31:14 +0100 [thread overview]
Message-ID: <m2y518kejx.fsf@gmail.com> (raw)
In-Reply-To: <jwv38jhmqnv.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Mon, 17 Feb 2014 15:27:49 -0500")
On Mon, Feb 17 2014, Stefan Monnier wrote:
> After thinking some more about it, I wonder, tho: why don't we just make
> deactivate-mark buffer-local?
After adding (make-variable-buffer-local 'deactivate-mark) to my .emacs
I didn't see any problems.
I noticed that mark is no longer deactivated by C-x C-e or M-C-x in the
*scratch* buffer. Presumably because prin1 now only modifies the
deactivate-mark variable in the *Messages* buffer.
I also discovered that add-text-properties doesn't deactivate mark. That
was surprising to me because usually changing text properties counts as
modifying the buffer and supposedly "all the primitives that change the
buffer set `deactivate-mark'".
Helmut
next prev parent reply other threads:[~2014-02-18 8:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 9:46 bug#16752: 24.3.50; pp-to-string deactivates mark Helmut Eller
2014-02-14 10:11 ` Eli Zaretskii
2014-02-14 11:02 ` Helmut Eller
2014-02-14 11:16 ` Eli Zaretskii
2014-02-14 11:22 ` Eli Zaretskii
2014-02-14 11:23 ` Helmut Eller
2014-02-14 11:39 ` Eli Zaretskii
2014-02-14 17:42 ` Stefan Monnier
2014-02-14 18:17 ` Eli Zaretskii
2014-02-14 18:27 ` Helmut Eller
2014-02-14 18:38 ` Eli Zaretskii
2014-02-14 21:00 ` Stefan Monnier
2014-02-15 7:14 ` Eli Zaretskii
2014-02-17 3:11 ` Stefan Monnier
2014-02-17 5:31 ` Eli Zaretskii
2014-02-17 20:27 ` Stefan Monnier
2014-02-17 20:46 ` Eli Zaretskii
2014-02-18 0:05 ` Stefan Monnier
2014-02-18 8:31 ` Helmut Eller [this message]
2014-02-18 15:18 ` Eli Zaretskii
2014-02-18 15:33 ` Helmut Eller
2014-02-18 16:52 ` Eli Zaretskii
2016-09-18 23:55 ` Alex
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=m2y518kejx.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=16752@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).