From: Helmut Eller <eller.helmut@gmail.com>
To: 16752@debbugs.gnu.org
Subject: bug#16752: 24.3.50; pp-to-string deactivates mark
Date: Fri, 14 Feb 2014 19:27:30 +0100 [thread overview]
Message-ID: <m2wqgx5z3h.fsf@gmail.com> (raw)
In-Reply-To: <m28uteowm7.fsf@gmail.com>
On Fri, Feb 14 2014, Eli Zaretskii wrote:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Date: Fri, 14 Feb 2014 12:42:25 -0500
>> Cc: 16752@debbugs.gnu.org
>>
>> 1- let-bind deactivate-mark in functions like pp-to-string so as to
>> eliminate those spurious deactivations. But there can be many of
>> them, and it doesn't solve the problem where the buffer-modification
>> is done in a non-temporary buffer.
>> 2- make deactivate-mark buffer-local. This is "The Right Way" but
>> might introduce new problems.
>> E.g. we really should deactivate the mark in all the buffers that
>> have their deactivate-mark set.
>
> 3- Save and restore deactivate-mark inside with-temp-buffer, which
> will probably solve 99.99% of these unexpected side effects.
4- Introduce something like buffer-disable-undo that disables this
automatic deactivate-mark updating. BTW, with-temp-buffer should
disable undo by default.
Helmut
next prev parent reply other threads:[~2014-02-14 18:27 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wqgx5z3h.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=16752@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.