Hooks for new buffers?

Hooks for new buffers?

[Steven Degutis]

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

I wrote auto-dim-other-buffers.el (
https://github.com/sdegutis/auto-dim-other-buffers.el) a few days ago,
which applies a "dimmed" face to non-current buffers.

It adds to post-command-hook and after-change-major-mode-hook, the first as
a catch-all "something changed" and the second as a hacky way of saying "a
new buffer just got created".

This mostly works. But sometimes new buffers are created that don't change
major modes. For example, *magit-process* gets created at some point, and
when I show it via $ inside magit-status, it's not dimmed. So it's not
changing major modes.

When I show the buffer via $, it probably triggers the post-command-hook,
but my hook tries to be efficient, by only looking at the previous
current-buffer and the new current-buffer. And this isn't either of those,
since it just shows up in a new window but isn't given focus. I'm sure
there are other situations like this.

The easiest way to solve this is to find a hook that's called when new
buffers are created, even if that's not its official purpose. Apparently
after-change-major-mode-hook isn't enough, presumably because these never
changed major modes. So is there such a hook?

And if not, is there at least some hook that happens whenever new windows
are opened?

-Steven

[-- Attachment #2: Type: text/html, Size: 1624 bytes --]

Re: Hooks for new buffers?

[W. Greenhouse]

Steven Degutis <sbdegutis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> The easiest way to solve this is to find a hook that's called when
> new buffers are created, even if that's not its official purpose.
> Apparently after-change-major-mode-hook isn't enough, presumably
> because these never changed major modes. So is there such a hook?
>
> And if not, is there at least some hook that happens whenever new
> windows are opened?
>
> -Steven

`window-configuration-change-hook', maybe?

-- 
BOFH excuse #39:

terrorist activities

Re: Hooks for new buffers?

[Andreas Röhler]

Am 04.04.2013 22:12, schrieb Steven Degutis:
> I wrote auto-dim-other-buffers.el (
> https://github.com/sdegutis/auto-dim-other-buffers.el) a few days ago,
> which applies a "dimmed" face to non-current buffers.
>
> It adds to post-command-hook and after-change-major-mode-hook, the first as
> a catch-all "something changed" and the second as a hacky way of saying "a
> new buffer just got created".
>
> This mostly works. But sometimes new buffers are created that don't change
> major modes.

Hi Steven,

AFAIU it's quite simple: there is only one buffer current, where all other will be subject to "dimmed".
If right, solution will not be to look what others do, but run-with-idle timer a routine dimming
everything except the current buffer.

Just my thoght,

Andreas

For example, *magit-process* gets created at some point, and
> when I show it via $ inside magit-status, it's not dimmed. So it's not
> changing major modes.
>
> When I show the buffer via $, it probably triggers the post-command-hook,
> but my hook tries to be efficient, by only looking at the previous
> current-buffer and the new current-buffer. And this isn't either of those,
> since it just shows up in a new window but isn't given focus. I'm sure
> there are other situations like this.
>
> The easiest way to solve this is to find a hook that's called when new
> buffers are created, even if that's not its official purpose. Apparently
> after-change-major-mode-hook isn't enough, presumably because these never
> changed major modes. So is there such a hook?
>
> And if not, is there at least some hook that happens whenever new windows
> are opened?
>
> -Steven
>

Re: Hooks for new buffers?

[Andreas Röhler]

Am 05.04.2013 10:47, schrieb Andreas Röhler:
> Am 04.04.2013 22:12, schrieb Steven Degutis:
>> I wrote auto-dim-other-buffers.el (
>> https://github.com/sdegutis/auto-dim-other-buffers.el) a few days ago,
>> which applies a "dimmed" face to non-current buffers.
>>
>> It adds to post-command-hook and after-change-major-mode-hook, the first as
>> a catch-all "something changed" and the second as a hacky way of saying "a
>> new buffer just got created".
>>
>> This mostly works. But sometimes new buffers are created that don't change
>> major modes.
>
> Hi Steven,
>
> AFAIU it's quite simple: there is only one buffer current, where all other will be subject to "dimmed".
> If right, solution will not be to look what others do, but run-with-idle timer a routine dimming
> everything except the current buffer.
>
> Just my thoght,
>
> Andreas
>

Apropos if some other buffers like *Help* should not be dimmed though, register them in a list.

Re: Hooks for new buffers?

[Lowell Gilbert]

wgreenhouse@riseup.net (W. Greenhouse) writes:

> Steven Degutis <sbdegutis@gmail.com> writes:
>
>> The easiest way to solve this is to find a hook that's called when
>> new buffers are created, even if that's not its official purpose.
>> Apparently after-change-major-mode-hook isn't enough, presumably
>> because these never changed major modes. So is there such a hook?
>>
>> And if not, is there at least some hook that happens whenever new
>> windows are opened?
>>
>> -Steven
>
> `window-configuration-change-hook', maybe?

I was going to suggest that, but I wanted to test it first because its
documentation is unclear on whether it gets run for a new buffer in an
existing window (and haven't gotten around to said testing). Another
possibility was buffer-list-update-hook, but you'd have to figure out on
your own whether there was a new buffer and if so, which it was.

'advice'ing get-buffer-create should catch all the cases, but that's a C
function, and it might be wandering into deep magic (and intractable
debugging).