From: Laurence Warne <laurencewarne@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 60381@debbugs.gnu.org
Subject: bug#60381: [PATCH] Preserve Window Position with Proced
Date: Sat, 7 Jan 2023 11:58:28 +0000 [thread overview]
Message-ID: <CAE2oLqjpngWuro=q+GoXjMsBag7Fjphm3+zjTEhSqpsvCOnO+w@mail.gmail.com> (raw)
In-Reply-To: <835ydiu20p.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
> It is not easy to understand the convoluted example, but did you try
> to see whether switch-to-buffer-preserve-window-point has any effect
> on the behavior you consider strange?
After some more debugging, I found setting read-minibuffer-restore-windows
to nil gave the desired behaviour.
From the doc for read-minibuffer-restore-windows : "Non-nil means restore
window configurations on exit from minibuffer." I guess this includes
window points as well - so this is expected behaviour in that changes to
the window configuration as a result of a timer run whilst the minibuffer
is active are reverted?
[-- Attachment #2: Type: text/html, Size: 752 bytes --]
next prev parent reply other threads:[~2023-01-07 11:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 15:55 bug#60381: [PATCH] Preserve Window Position with Proced Laurence Warne
2022-12-28 17:14 ` Eli Zaretskii
2022-12-28 20:30 ` Laurence Warne
2022-12-29 6:09 ` Eli Zaretskii
2022-12-29 12:52 ` Laurence Warne
2022-12-29 14:09 ` Eli Zaretskii
[not found] ` <CAE2oLqh5i-fFVeYwyRufWhFZzrxDCfO+VrWFpe3tRLW9OJKUbg@mail.gmail.com>
2022-12-29 17:37 ` Eli Zaretskii
2023-01-05 15:59 ` Laurence Warne
2023-01-07 9:28 ` Eli Zaretskii
2023-01-07 11:58 ` Laurence Warne [this message]
2023-01-07 13:28 ` Eli Zaretskii
2023-01-07 17:23 ` Laurence Warne
2023-01-14 8:40 ` Eli Zaretskii
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='CAE2oLqjpngWuro=q+GoXjMsBag7Fjphm3+zjTEhSqpsvCOnO+w@mail.gmail.com' \
--to=laurencewarne@gmail.com \
--cc=60381@debbugs.gnu.org \
--cc=eliz@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.