all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Laurence Warne <laurencewarne@gmail.com>
Cc: 60381@debbugs.gnu.org
Subject: bug#60381: [PATCH] Preserve Window Position with Proced
Date: Sat, 07 Jan 2023 11:28:38 +0200	[thread overview]
Message-ID: <835ydiu20p.fsf@gnu.org> (raw)
In-Reply-To: <CAE2oLqgPburj4+SX_y0gid8LKwzUs7VRyOLorKUysEM3W0M0JQ@mail.gmail.com> (message from Laurence Warne on Thu, 5 Jan 2023 15:59:57 +0000)

> From: Laurence Warne <laurencewarne@gmail.com>
> Date: Thu, 5 Jan 2023 15:59:57 +0000
> Cc: 60381@debbugs.gnu.org
> 
> Minor update, whilst working on the first case, I've come across some strange behaviour which causes the
> window position to be reset to (point-min) in some circumstances.  To reproduce this with a more minimal
> setup than proced-update (I've also asked here:
> https://emacs.stackexchange.com/questions/75165/window-point-reset-after-update):

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?





  reply	other threads:[~2023-01-07  9:28 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 [this message]
2023-01-07 11:58                   ` Laurence Warne
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=835ydiu20p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60381@debbugs.gnu.org \
    --cc=laurencewarne@gmail.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
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.