From: Michael Heerdegen <michael_heerdegen@web.de>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-agenda-later sometimes creates a void display [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/31.0.50/lisp/org/)]
Date: Tue, 14 Jan 2025 04:36:10 +0100 [thread overview]
Message-ID: <87a5buvzh1.fsf@web.de> (raw)
In-Reply-To: <87a5bw79g2.fsf@localhost> (Ihor Radchenko's message of "Sun, 12 Jan 2025 07:55:25 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> > One step back: What problem does this hack solve? [...]
>
> https://orgmode.org/list/87lfh2hk4k.fsf@gmail.com/
I asked rhetorically ;-) But thanks, this is what I expected.
> > How about something like this?
> >
> > - If point is at bob, we ensure that point is restored at bob - and
> > likewise for eob.
> >
> > - When bob was visible in the prior view, we use window-start = 1
> > for the new view, too
> >
> > - But when bob was not visible in the last view, we try to restore the
> > visible line number containing the window point, so that hitting f
> > will show the cursor at the same vertical position as in the last
> > view. Or maybe better: restore the vertical position of the
> > beginning of the weekday point was in.
>
> I hope that my idea in the patch is good enough and that we do not need
> to go into redisplay complications.
These points would not mess with redisplay, just set window-start to
something different than now.
> - (set-window-start nil wstart)))
> + (set-window-start nil wstart 'noforce)))
Nice trick (or workaround), thanks.
Yes, this solves my problem indeed, and behaves quite ok. Time will
show whether I like the behavior, but it's a definite improvement, so I
suggest we go with it for now.
Thanks for your help,
Michael.
next prev parent reply other threads:[~2025-01-14 3:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 0:29 [BUG] org-agenda-later sometimes creates a void display [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/31.0.50/lisp/org/)] Michael Heerdegen
2025-01-05 8:52 ` Ihor Radchenko
2025-01-05 18:18 ` Michael Heerdegen
2025-01-05 18:31 ` Ihor Radchenko
2025-01-05 20:12 ` Michael Heerdegen
2025-01-11 14:39 ` Ihor Radchenko
2025-01-12 0:20 ` Michael Heerdegen
2025-01-12 7:55 ` Ihor Radchenko
2025-01-14 3:36 ` Michael Heerdegen [this message]
2025-01-14 17:58 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a5buvzh1.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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/org-mode.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).