emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gustavo Barros <gusbrs.2016@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
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	[thread overview]
Message-ID: <87pmy7fq1q.fsf@gmail.com> (raw)
In-Reply-To: <87mttbimpf.fsf@gnu.org>

Hi Bastien,

On Mon, 03 May 2021 at 17:31, Bastien <bzg@gnu.org> wrote:

> Hi Gustavo,
> Gustavo Barros <gusbrs.2016@gmail.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? 


  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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pmy7fq1q.fsf@gmail.com \
    --to=gusbrs.2016@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).