From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: darthandrus@gmail.com, 11068@debbugs.gnu.org
Subject: bug#11068: 24.0.94; Face-remapped background does not extend to end of window
Date: Sat, 24 Mar 2012 20:48:31 +0100 [thread overview]
Message-ID: <4F6E250F.3080906@gmx.at> (raw)
In-Reply-To: <jwviphtj2zm.fsf-monnier+INBOX@gnu.org>
> If you want such a feature,
Personally I'd have no use for it. But the request for such a feature
reappears from time to time on help-gnu-emacs.
> I'd suggest you start by looking at every
> place that observes Vface_remapping_alist and change it to also consider
> Fwindow_parameter (selected_window, Qface_remapping_alist).
> I can't guarantee this will be sufficient, but it should be a good
> starting point.
These are all in xfaces.c and I doubt they have any idea about the
window currently drawn.
Anyway, I'll rather redraw my request - the feature as Eli currently
implements it is all I need (for more than 10 years, meanwhile).
martin
next prev parent reply other threads:[~2012-03-24 19:48 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 20:49 bug#11068: 24.0.94; Face-remapped background does not extend to end of window Ivan Andrus
[not found] ` <handler.11068.B.13324512277363.ack@debbugs.gnu.org>
2012-03-22 21:18 ` bug#11068: Acknowledgement (24.0.94; Face-remapped background does not extend to end of window) Ivan Andrus
2012-03-22 21:33 ` Glenn Morris
2012-03-22 21:31 ` bug#11069: 24.0.94; Face-remapped background does not extend to end of window Glenn Morris
2012-03-23 10:36 ` bug#11068: " Eli Zaretskii
2012-03-23 10:48 ` Ivan Andrus
2012-03-24 12:37 ` Eli Zaretskii
2012-03-24 13:42 ` martin rudalics
2012-03-24 14:12 ` Eli Zaretskii
2012-03-24 19:48 ` martin rudalics
2012-03-24 20:47 ` Eli Zaretskii
2012-03-25 12:54 ` martin rudalics
2012-03-25 17:22 ` Eli Zaretskii
2012-03-25 19:19 ` martin rudalics
2012-03-25 19:53 ` Stefan Monnier
2012-03-25 20:44 ` martin rudalics
2012-03-25 21:49 ` Eli Zaretskii
2012-03-25 21:53 ` Eli Zaretskii
2012-03-26 7:05 ` martin rudalics
2012-03-26 19:32 ` Eli Zaretskii
2012-03-27 9:23 ` martin rudalics
2012-03-27 18:40 ` Eli Zaretskii
2012-03-30 7:35 ` martin rudalics
2012-03-30 8:18 ` Eli Zaretskii
2012-03-30 10:14 ` martin rudalics
2012-03-30 11:42 ` Eli Zaretskii
2012-03-31 10:29 ` Eli Zaretskii
2012-03-30 10:47 ` martin rudalics
2012-03-24 18:04 ` Stefan Monnier
2012-03-24 19:48 ` martin rudalics [this message]
2012-03-24 14:17 ` Chong Yidong
2012-03-24 14:40 ` Eli Zaretskii
2012-03-25 3:01 ` Chong Yidong
2012-03-25 4:02 ` Eli Zaretskii
2012-03-25 6:20 ` Chong Yidong
2012-03-25 12:55 ` martin rudalics
2012-03-25 17:26 ` Eli Zaretskii
2012-03-25 19:20 ` martin rudalics
2012-03-25 17:51 ` Eli Zaretskii
2012-03-26 4:16 ` Chong Yidong
2012-03-26 19:35 ` Eli Zaretskii
2012-03-30 8:49 ` Eli Zaretskii
2012-03-25 12:54 ` martin rudalics
2012-03-25 17:25 ` Eli Zaretskii
2012-03-25 19:19 ` martin rudalics
2012-03-25 21:50 ` 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=4F6E250F.3080906@gmx.at \
--to=rudalics@gmx.at \
--cc=11068@debbugs.gnu.org \
--cc=darthandrus@gmail.com \
--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).