From: Helmut Eller <eller.helmut@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16752@debbugs.gnu.org
Subject: bug#16752: 24.3.50; pp-to-string deactivates mark
Date: Fri, 14 Feb 2014 12:23:02 +0100 [thread overview]
Message-ID: <m2d2iqlyzt.fsf@gmail.com> (raw)
In-Reply-To: <83a9duc5b2.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Feb 2014 13:16:49 +0200")
On Fri, Feb 14 2014, Eli Zaretskii wrote:
>> From: Helmut Eller <eller.helmut@gmail.com>
>> Cc: 16752@debbugs.gnu.org
>> Date: Fri, 14 Feb 2014 12:02:33 +0100
>>
>> >> (list deactivate-mark
>> >> (pp-to-string '1)
>> >> deactivate-mark)
>> >>
>> >> returns (nil "1" t). Deactivating the mark is a surprising and
>> >> unnecessary side effect.
>> >
>> > _Any_ change to _any_ buffer will set deactivate-mark, which is a
>> > global variable.
>>
>> What has that do to with pp-to-string? I didn't ask for _any_ change to
>> _any_ buffer.
>
> See pp-buffer, which is called by pp-string. You asked for pp-string,
> which does its job using a temporary buffer.
So you're saying that it's not a bug that pp-to-string modifies
deactivate-mark?
Helmut
next prev parent reply other threads:[~2014-02-14 11:23 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 [this message]
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
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=m2d2iqlyzt.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=16752@debbugs.gnu.org \
--cc=eliz@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 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).