From: Gustavo Barros <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Bug: org-agenda-later scrolls buffer unnecessarily [9.4 (9.4-7-g3eccc5-elpaplus @ /home/gustavo/.emacs.d/elpa/org-plus-contrib-20200921/)] Date: Mon, 03 May 2021 18:47:14 -0300 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi Bastien, On Mon, 03 May 2021 at 17:31, Bastien <firstname.lastname@example.org> wrote: > Hi Gustavo, > > Gustavo Barros <email@example.com> writes: > >> since some time I've been facing a small annoyance in the agenda, as >> when I move point in my weekly agenda to a day which is not the first >> one display and then hit "f" (`org-agenda-later') the agenda buffer >> is >> scrolled up, hiding the top of the buffer, even though there is no >> lack >> of space in the frame to fit the whole window. > > Fixed in maint, thanks. Thank you for looking into this. But I think the commit, though indeed avoids the reported undue scrolling, brings other undesired side effects. Usually, `org-agenda-later' will carry over the current day of the week to the next week. If we call it on Thursday, point will be placed on the same week day of the next week. Just calling `(set-window-start nil 1)' there breaks this regularity. It is easy to generate a case where this happens. Just squeeze the height of your window on a "populated" agenda, and choose a day for which that day next week won't fit in the window if position 1 is shown, and call it from there. Perhaps doing so before the call to `org-agenda-find-same-or-today-or-agenda' would be a possibility? (untested) Best, Gustavo.
next prev parent reply other threads:[~2021-05-03 21:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 21:53 Gustavo Barros 2021-05-03 20:31 ` Bastien 2021-05-03 21:47 ` Gustavo Barros [this message] 2021-05-03 22:26 ` Bastien 2021-05-03 22:47 ` Gustavo Barros
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://orgmode.org * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
Org-mode mailing list This inbox may be cloned and mirrored by anyone: git clone --mirror https://orgmode.org/list/0 list/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 list list/ https://orgmode.org/list \ firstname.lastname@example.org public-inbox-index list Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.yhetil.org/yhetil.emacs.orgmode nntp://news.gmane.io/gmane.emacs.orgmode AGPL code for this site: git clone https://public-inbox.org/public-inbox.git