From: Eli Zaretskii <eliz@gnu.org>
To: sds@gnu.org
Cc: 57837@debbugs.gnu.org, gregory@heytings.org
Subject: bug#57837: 29.0.50; fit-window-to-buffer should reposition the buffer
Date: Fri, 16 Sep 2022 08:45:57 +0300 [thread overview]
Message-ID: <83wna350tm.fsf@gnu.org> (raw)
In-Reply-To: <lz5yhop890.fsf@3c22fb11fdab.ant.amazon.com> (message from Sam Steingold on Thu, 15 Sep 2022 18:45:15 -0400)
> Cc: 57837@debbugs.gnu.org
> From: Sam Steingold <sds@gnu.org>
> Date: Thu, 15 Sep 2022 18:45:15 -0400
>
> > * Gregory Heytings <tertbel@urlgvatf.bet> [2022-09-15 19:34:38 +0000]:
> >
> >>
> >> When the buffer is smaller than the window, move the point to the end
> >> and do `C-x w -` (fit-window-to-buffer).
> >>
> >> The window shrinks, but it is empty - the whole buffer is above.
> >>
> >
> > (advice-add 'fit-window-to-buffer :after
> > (lambda () (and (= (count-lines (point-min) (point-max)) (1- (window-height)))
> > (or (< (point) (point-max)) (forward-line -1) t)
> > (set-window-start nil (point-min)))))
>
> Thank you.
>
> Why shouldn't this be the default behavior?
I thought I explained that it wasn't needed?
prev parent reply other threads:[~2022-09-16 5:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 17:31 bug#57837: 29.0.50; fit-window-to-buffer should reposition the buffer Sam Steingold
2022-09-15 18:03 ` Eli Zaretskii
2022-09-15 18:30 ` Sam Steingold
2022-09-15 18:55 ` Sam Steingold
2022-09-15 19:07 ` Eli Zaretskii
2022-09-15 22:52 ` Sam Steingold
2022-09-16 5:53 ` Eli Zaretskii
2022-09-15 19:00 ` Eli Zaretskii
2022-09-15 19:34 ` Gregory Heytings
2022-09-15 22:45 ` Sam Steingold
2022-09-15 22:59 ` Gregory Heytings
2022-09-16 18:52 ` Sam Steingold
2022-09-16 19:34 ` Gregory Heytings
2022-09-16 21:25 ` Sam Steingold
2022-09-16 21:34 ` Gregory Heytings
2022-09-17 6:48 ` Eli Zaretskii
2022-09-17 7:10 ` Gregory Heytings
2022-09-17 7:25 ` Eli Zaretskii
2022-09-18 8:34 ` Gregory Heytings
2022-09-16 5:45 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wna350tm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57837@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=sds@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.