From: Ralf Angeli <angeli@caeruleus.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>, ding@gnus.org
Cc: 662@emacsbugs.donarmstrong.com, Chong Yidong <cyd@stupidchicken.com>
Subject: Re: bug#662: 23.0.60; Constant recentering with scroll-margin set
Date: Tue, 12 Aug 2008 20:51:51 +0200 [thread overview]
Message-ID: <87ej4u3w3c.fsf@photon.caeruleus.net> (raw)
In-Reply-To: <jwvod43b54p.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Fri, 08 Aug 2008 16:56:06 -0400")
* Stefan Monnier (2008-08-08) writes:
> BTW, shouldn't Gnus "just" set scroll-margin (and such things)
> buffer-locally in its article buffer, so as to isolate it from
> such problems?
> Or maybe not buffer-locally but let-bound around a call to redisplay?
I guess this is something to decide for the Gnus developers, so I am
forwarding the message to the Gnus list.
Note that this discussion is centered around the recentering bug I
reported earlier on the Gnus list, so this is not related to a new bug.
--
Ralf
parent reply other threads:[~2008-08-12 18:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <jwvod43b54p.fsf-monnier+emacsbugreports@gnu.org>]
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=87ej4u3w3c.fsf@photon.caeruleus.net \
--to=angeli@caeruleus.net \
--cc=662@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=ding@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.
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 NNTP newsgroup(s).