From: Juri Linkov <juri@linkov.net>
To: martin rudalics <rudalics@gmx.at>
Cc: 36859@debbugs.gnu.org
Subject: bug#36859: Customizable fit-window-to-buffer
Date: Thu, 08 Aug 2019 01:01:10 +0300 [thread overview]
Message-ID: <87o910my8p.fsf@mail.linkov.net> (raw)
In-Reply-To: <87r25yq6se.fsf@mail.linkov.net> (Juri Linkov's message of "Wed, 07 Aug 2019 01:16:01 +0300")
>> The only practicable solution IMHO is to provide a plain
>> 'vc-adjust-window-size-function' option defaulting to
>> 'shrink-window-if-larger-than-buffer' and allowing 'ignore' and
>> 'fit-window-to-buffer' as alternatives.
>
> This looks like hooks. I too like hooks, I don't understand
> why vc uses such inconvenient macros as vc-run-delayed
> instead of more flexible hooks. Window management could use
> hooks more often, e.g. to delay setting window-start/window-point
> to later times when the buffer is ready, etc.
I see there is a hook already in vc: 'vc-post-command-functions'.
But it's unclear how to use it to call 'shrink-window-if-larger-than-buffer'
from the hook only on vc-log and vc-diff commands.
Maybe vc-log-internal-common and vc-diff-internal could provide new hooks,
e.g. vc-log-post-command-functions and vc-diff-post-command-functions.
next prev parent reply other threads:[~2019-08-07 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 20:23 bug#36859: Customizable fit-window-to-buffer Juri Linkov
2019-07-31 9:12 ` martin rudalics
2019-07-31 20:57 ` Juri Linkov
2019-08-03 7:57 ` martin rudalics
2019-08-03 21:16 ` Juri Linkov
2019-08-04 8:00 ` martin rudalics
2019-08-04 19:27 ` Juri Linkov
2019-08-05 9:23 ` martin rudalics
2019-08-05 22:03 ` Juri Linkov
2019-08-06 9:00 ` martin rudalics
2019-08-06 22:16 ` Juri Linkov
2019-08-07 22:01 ` Juri Linkov [this message]
2019-08-08 7:27 ` martin rudalics
2019-08-08 21:39 ` Juri Linkov
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=87o910my8p.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=36859@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).