From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 58175@debbugs.gnu.org, monnier@iro.umontreal.ca, miha@kamnitnik.top
Subject: bug#58175: 29.0.50; M-x window-swap-states during an active mark leaves behind a region overlay
Date: Thu, 06 Oct 2022 11:13:03 +0300 [thread overview]
Message-ID: <83a669qsj4.fsf@gnu.org> (raw)
In-Reply-To: <48874213-cfe4-dc07-fe0a-cb085d6549ef@gmx.at> (message from martin rudalics on Thu, 6 Oct 2022 09:48:12 +0200)
> Date: Thu, 6 Oct 2022 09:48:12 +0200
> Cc: miha@kamnitnik.top, 58175@debbugs.gnu.org, monnier@iro.umontreal.ca
> From: martin rudalics <rudalics@gmx.at>
>
> With emacs -Q put the following text into *scratch*
>
>
> (push '(internal-region-overlay . t) window-persistent-parameters)
>
> (defvar foo-conf nil)
>
> (defun foo-save ()
> (interactive)
> (setq foo-conf (current-window-configuration)))
>
> (defun foo-restore ()
> (interactive)
> (set-window-configuration foo-conf))
>
> (split-window)
>
> ;; (eval-buffer)
>
>
> evaluate it and do M-x foo-save followed by C-x o. Move point and
> activate the region. M-x foo-restore now gets me two overlays, one in
> the upper and one in the lower window.
>
> Now try again with 'internal-region-overlay' not made persistent, that
> is, the first line commented out. The same scenario gets me one (albeit
> illogical) overlay in the upper window only.
Both results in this scenario are wrong, IMO, so I don't see why we'd
prefer one of them. I also don't understand how this scenario could
happen in real life, FWIW.
next prev parent reply other threads:[~2022-10-06 8:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 17:29 bug#58175: 29.0.50; M-x window-swap-states during an active mark leaves behind a region overlay miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-29 18:34 ` Eli Zaretskii
2022-09-29 19:17 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-29 19:19 ` Eli Zaretskii
2022-10-02 16:50 ` Eli Zaretskii
2022-10-04 8:23 ` martin rudalics
2022-10-04 16:54 ` Eli Zaretskii
2022-10-04 20:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 21:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-04 21:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-05 5:42 ` Eli Zaretskii
2022-10-06 12:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-07 8:17 ` martin rudalics
2022-10-07 19:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-08 10:05 ` martin rudalics
2022-10-08 17:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-09 14:05 ` martin rudalics
2022-10-05 7:36 ` martin rudalics
2022-10-05 8:28 ` Eli Zaretskii
2022-10-06 7:48 ` martin rudalics
2022-10-06 8:13 ` Eli Zaretskii [this message]
2022-10-07 8:09 ` martin rudalics
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=83a669qsj4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58175@debbugs.gnu.org \
--cc=miha@kamnitnik.top \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.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.