unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@iro.umontreal.ca, 52385@debbugs.gnu.org
Subject: bug#52385: 29.0.50; Doc-View can't view separate pages in separate windows
Date: Fri, 17 Dec 2021 10:29:22 +0200	[thread overview]
Message-ID: <86lf0j3a8t.fsf@mail.linkov.net> (raw)
In-Reply-To: <83czlwfh27.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 Dec 2021 22:09:04 +0200")

>> Sorry for misleading info: actually, it's not about overlay priorities.
>> When an overlay has the ‘window’ property, then this overlay should apply
>> only on that window, but currently it's applied to all windows.
>
> Please show a recipe for reproducing this from "emacs -Q".

Please see the recipe for "emacs -Q" in https://debbugs.gnu.org/52385#20

It works correctly in 28.0.90, but fails in master.





  reply	other threads:[~2021-12-17  8:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09  4:20 bug#52385: 29.0.50; Doc-View can't view separate pages in separate windows Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-10 11:55 ` Lars Ingebrigtsen
2021-12-10 15:05   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-11  3:23     ` Lars Ingebrigtsen
2021-12-11 18:46 ` Juri Linkov
2021-12-16 17:04   ` Juri Linkov
2021-12-16 17:44     ` Eli Zaretskii
2021-12-16 19:33       ` Juri Linkov
2021-12-16 20:09         ` Eli Zaretskii
2021-12-17  8:29           ` Juri Linkov [this message]
2021-12-17 12:08             ` Eli Zaretskii
2021-12-18 17:18               ` Juri Linkov
2021-12-18  9:11     ` Eli Zaretskii
2021-12-19 10:37       ` Lars Ingebrigtsen
2021-12-19 13:49         ` Eli Zaretskii
2021-12-19 13:54           ` Lars Ingebrigtsen
2021-12-19 14:09             ` Eli Zaretskii
2021-12-19 17:12               ` Juri Linkov
2021-12-19 17:31                 ` Eli Zaretskii

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=86lf0j3a8t.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=52385@debbugs.gnu.org \
    --cc=eliz@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).