Re: 27.0.50: How can I test a buffer-local window-configuration-change-hook in batch mode?

[martin rudalics]

> The example is actually pretty close to the real use-case.  If so-long
> sees a file with very long lines being visited, it (now) only triggers
> its mitigations if and when that buffer is first displayed.  So if the
> buffer is never displayed then nothing is done.

Eli, do you think that Phil's use case would warrant a special hook
say 'buffer-first-display-functions' triggered when a buffer's
display-count changes from 0?  It would be stunningly simple to
implement that.  OTOH, scanning all window changes to find out whether
a buffer has been displayed for the first time just produces lots of
wasted cyles.

> Without `run-window-configuration-change-hook' I'd have to replicate
> some of that functionality myself, and the test would be getting even
> further away from the real processes, and therefore becoming less and
> less useful as a test.  I'd like to have to fake as little as possible.

Understandable.  Rewriting this in Elisp is no fun.

martin