From: Drew Adams <drew.adams@oracle.com>
To: 20829@debbugs.gnu.org
Subject: bug#20829: 25.0.50; `compilation-set-window' calls `window-fringes' with wrong window selected
Date: Tue, 16 Jun 2015 12:40:52 -0700 (PDT) [thread overview]
Message-ID: <5cae4e00-2db4-4d31-83db-f1f1dcbae095@default> (raw)
Debugging shows me that when I use `C-x `' from another frame than the
compilation-buffer frame, `compilation-goto-locus' calls
`compilation-set-window', and that then calls `window-fringes', the
compilation-buffer window is not selected (not in some contexts anyway),
so the test for no left window fringe is done in the wrong window.
It is probably enough, to repro this (but I haven't tried), to have
`default-frame-alist' show left fringe bug have `special-display-alist'
not show left fringe, and to have the compilation buffer (e.g. `*grep*')
be special-display.
In the debugger I see that `compilation-goto-locus' calls
`display-buffer' but does not select the compilation-buffer window.
Then `compilation-set-window' is called without the compilation-buffer
window being selected. Eventually that window is selected, but that
happens after the call to `compilation-set-window'.
In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
of 2014-10-20 on LEG570
Bzr revision: 118168 rgm@gnu.org-20141020195941-icp42t8ttcnud09g
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2015-06-16 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 19:40 Drew Adams [this message]
2015-07-04 8:47 ` bug#20829: 25.0.50; `compilation-set-window' calls `window-fringes' with wrong window selected martin rudalics
2015-07-04 15:03 ` Drew Adams
2015-07-05 10:57 ` 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
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=5cae4e00-2db4-4d31-83db-f1f1dcbae095@default \
--to=drew.adams@oracle.com \
--cc=20829@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 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).