From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Recentering during article scrolling with scroll-margin
Date: Thu, 14 Aug 2008 09:48:04 +0900 [thread overview]
Message-ID: <b4mzlngjubf.fsf@jpl.org> (raw)
In-Reply-To: <87vdy4buyf.fsf@marauder.physik.uni-ulm.de>
>>>>> In <87vdy4buyf.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>> + (move-to-window-line (if (featurep 'xemacs) -1 (- -1 scroll-margin)))
> Should we test for `scroll-margin' instead of (featurep 'xemacs)?
> E.g. (and (boundp 'scroll-margin) (numberp scroll-margin))?
That's right if XEmacs team plan to introduce the scroll-margin
control in the future. But the reason I arbitrarily decided to
use (featurep 'xemacs) is that I don't think so. It also makes
the source code be clean and makes the byte code be a little bit
fast. Is it a wrong approach? In other words, does XEmacs plan
to have the scroll-margin control in the future?
Regards,
prev parent reply other threads:[~2008-08-14 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 9:27 Ralf Angeli
2008-08-11 2:51 ` Katsumi Yamaoka
2008-08-11 16:35 ` Ralf Angeli
2008-08-11 22:54 ` Katsumi Yamaoka
2008-08-13 19:01 ` Reiner Steib
2008-08-14 0:48 ` Katsumi Yamaoka [this message]
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=b4mzlngjubf.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).