From: Steven Degutis <sbdegutis@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: `auto-dim-other-windows` -- scrutiny invited
Date: Wed, 3 Apr 2013 15:22:31 -0500 [thread overview]
Message-ID: <CACeWA3jPM97a_dxxscR41RG2-g_eq_Lch526DHJ_w+2G6=WiAg@mail.gmail.com> (raw)
In-Reply-To: <jwvd2ubcrck.fsf-monnier+gmane.emacs.help@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
The problem with `window-configuration-change-hook` is that it isn't called
all the times we would need it. For example, it's not called when you do
`other-window` via `C-x o`.
-Steven
On Wed, Apr 3, 2013 at 3:13 PM, Stefan Monnier <monnier@iro.umontreal.ca>wrote:
> > We could add overlays to every buffer, and whenever you change windows,
> > remove the overlay from the current buffer and add it back to the
> previous
> > buffer.
>
> Auto-adding the overlays can be done in window-configuration-change-hook.
> We're talking about N overlays per buffer where N is small (it's number of
> windows where the buffer is displayed), so there's no performance
> problem there.
>
> > Or, we could have it reversed. We could only have an overlay on the
> current
> > buffer at any given time, and give it the window of (selected-window),
> and
> > keep updating these any time you change buffers or windows.
>
> That would be a lot simpler, indeed, but I think it will be difficult
> to make it look good.
>
>
> Stefan
>
>
>
[-- Attachment #2: Type: text/html, Size: 1567 bytes --]
next prev parent reply other threads:[~2013-04-03 20:22 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 21:06 `auto-dim-other-windows` -- scrutiny invited Steven Degutis
2013-04-02 22:19 ` Óscar Fuentes
2013-04-02 22:48 ` Steven Degutis
2013-04-02 23:14 ` Óscar Fuentes
2013-04-02 23:19 ` Steven Degutis
[not found] ` <mailman.23338.1364944796.855.help-gnu-emacs@gnu.org>
2013-04-03 13:03 ` Michael Heerdegen
2013-04-03 13:27 ` Steven Degutis
[not found] ` <mailman.23335.1364941179.855.help-gnu-emacs@gnu.org>
2013-04-03 13:11 ` Michael Heerdegen
2013-04-03 13:19 ` Steven Degutis
2013-04-03 14:44 ` Steven Degutis
2013-04-03 14:47 ` Mark Skilbeck
2013-04-03 14:52 ` Steven Degutis
2013-04-03 14:55 ` Mark Skilbeck
2013-04-03 15:09 ` Steven Degutis
2013-04-03 15:17 ` Óscar Fuentes
2013-04-03 15:15 ` Óscar Fuentes
2013-04-03 15:32 ` Steven Degutis
2013-04-03 16:03 ` Steven Degutis
2013-04-03 17:03 ` Óscar Fuentes
2013-04-03 17:13 ` Steven Degutis
2013-04-03 17:17 ` Óscar Fuentes
2013-04-03 17:42 ` Steven Degutis
2013-04-03 18:10 ` Óscar Fuentes
2013-04-03 18:54 ` Steven Degutis
2013-04-03 19:19 ` Steven Degutis
2013-04-03 20:13 ` Stefan Monnier
2013-04-03 20:22 ` Steven Degutis [this message]
2013-04-03 22:23 ` Stefan Monnier
2013-04-04 21:55 ` Drew Adams
2013-04-04 22:01 ` Steven Degutis
2013-04-05 12:49 ` Stefan Monnier
2013-04-06 19:23 ` Drew Adams
[not found] ` <mailman.23406.1365005023.855.help-gnu-emacs@gnu.org>
2013-04-03 17:20 ` Michael Heerdegen
2013-04-03 17:44 ` Steven Degutis
2013-04-03 20:55 ` Steven Degutis
2013-04-04 16:02 ` Steven Degutis
2013-04-04 7:27 ` Joost Kremers
2013-04-04 20:52 ` Ludwig, Mark
2013-04-04 20:53 ` Steven Degutis
2013-04-04 21:31 ` Steven Degutis
2013-04-03 15:57 ` Ludwig, Mark
2013-04-03 16:06 ` Steven Degutis
2013-04-03 16:37 ` Drew Adams
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='CACeWA3jPM97a_dxxscR41RG2-g_eq_Lch526DHJ_w+2G6=WiAg@mail.gmail.com' \
--to=sbdegutis@gmail.com \
--cc=help-gnu-emacs@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.
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).