From: Noam Postavsky <npostavs@gmail.com>
To: Markus Triska <triska@metalevel.at>
Cc: 35177@debbugs.gnu.org
Subject: bug#35177: 27.0.50; Binding deactivate-mark to nil unexpectedly deactivates the mark
Date: Mon, 08 Apr 2019 20:04:01 -0400 [thread overview]
Message-ID: <87a7h0cadq.fsf@gmail.com> (raw)
In-Reply-To: <87o95gfqdp.fsf@metalevel.at> (Markus Triska's message of "Mon, 08 Apr 2019 17:50:10 +0200")
Markus Triska <triska@metalevel.at> writes:
> (let (deactivate-mark)
> (switch-to-buffer (get-buffer-create "t"))
> (insert "hello")
> (set-mark-command nil)
> (move-beginning-of-line nil))
>
> It seems to play a role whether its buffer is modified or not, hence
> this receipe starting from a fresh file and an unmodified buffer.
I think the key detail is whether deactivate-mark has a buffer-local
value or not (modifying the buffer gives it one). If it does have a
buffer-local value, then the let-binding affects just the buffer-local
one, otherwise, it binds the global value. So C-x C-e on the following
always gives an active mark:
(progn
(make-local-variable 'deactivate-mark)
;; (kill-local-variable 'deactivate-mark)
(let (deactivate-mark)
(switch-to-buffer (get-buffer-create "t"))
(insert "hello")
(set-mark-command nil)
(move-beginning-of-line nil)))
And if you uncomment the kill-local-variable statement, then C-x C-e
will never give an active mark.
C-M-x and M-x eval-region still do give an active mark for all variants.
I'm not entirely sure why, but I'm guessing it's because they juggle
buffers in a slightly different way, such that the command loop ends up
consulting the value of deactivate-mark from somewhere else.
next prev parent reply other threads:[~2019-04-09 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 0:11 bug#35177: 27.0.50; Binding deactivate-mark to nil unexpectedly deactivates the mark Markus Triska
2019-04-07 15:42 ` Eli Zaretskii
2019-04-07 22:39 ` Markus Triska
2019-04-08 2:35 ` Eli Zaretskii
2019-04-08 10:03 ` Markus Triska
2019-04-08 15:09 ` Eli Zaretskii
2019-04-08 15:50 ` Markus Triska
2019-04-08 16:00 ` Eli Zaretskii
2019-04-09 0:04 ` Noam Postavsky [this message]
2019-04-09 15:26 ` Markus Triska
2019-04-09 23:46 ` Noam Postavsky
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=87a7h0cadq.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35177@debbugs.gnu.org \
--cc=triska@metalevel.at \
/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.