From: David <de_bb@arcor.de>
To: ding@gnus.org
Subject: scroll-margin woes
Date: Thu, 13 Mar 2008 16:12:39 +0100 [thread overview]
Message-ID: <kzfxuu8xp4.fsf@kafka.physik3.gwdg.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]
I've recently set my scroll-margin value to >0 and immediately had
problems using Gnus. First, I would recommend to apply the patch that
sets the scroll-margin to zero in summary buffers:
http://article.gmane.org/gmane.emacs.devel/85300
Even if this patch may only cure the symptom of a bug in Emacs I'd still
think it should be applied since a) it does no harm and b) the summary
buffer is otherwise practically unusable if scroll-margin > 0 and
Emacs 22 or newer.
Additionally, I noticed that when I hit ENTER in the summary buffer to
scroll the currently displayed article by one line, it often scrolls by
nearly a full page. This frequently happens in shimbun groups, but not
always - I can't really say why. My guess is this is due to
(move-to-window-line -1)
in gnus-article-next-page. I fixed this behavior by putting the cursor
in the middle of the article buffer before calling
gnus-article-next-page-1 (see attached patch). This works for me, but I
don't know if this is the correct thing to do. Scrolling in Emacs is a
deep mystery to me...
-David
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: gnus-art-patch.diff --]
[-- Type: text/x-diff, Size: 376 bytes --]
--- gnus-art.el 2008-03-13 15:51:23.000000000 +0100
+++ gnus-art.el-patched 2008-03-13 15:52:31.000000000 +0100
@@ -6100,6 +6100,9 @@
(gnus-narrow-to-page 1) ;Go to next page.
nil)
;; More in this page.
+ (when (and (boundp 'scroll-margin)
+ (not (zerop scroll-margin)))
+ (move-to-window-line nil))
(gnus-article-next-page-1 lines)
nil))
next reply other threads:[~2008-03-13 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 15:12 David [this message]
2008-03-13 17:25 ` Ralf Angeli
2008-03-14 9:01 ` David
2008-03-14 18:28 ` Ralf Angeli
2008-03-17 14:18 ` David
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=kzfxuu8xp4.fsf@kafka.physik3.gwdg.de \
--to=de_bb@arcor.de \
--cc=ding@gnus.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.
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).