From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@hpc.uh.edu
Subject: Re: getting comfortable again after upgrade to emacs 21
Date: Sat, 23 Feb 2002 12:42:56 +0100 [thread overview]
Message-ID: <a57vhb$i9g$1@quimby2.netfonds.no> (raw)
In-Reply-To: <m3y9hli56q.fsf@lugabout.jhcloos.org> (cloos@jhcloos.com's message of "22 Feb 2002 16:21:01 -0500")
cloos@jhcloos.com (James H. Cloos Jr.) writes:
> The two most noticible problems are keeping the current article's
> summary line in the middle of the summary buffer window when summary
> and article are both displayed, and dealing w/ non 7-bit ASCII
> characters.
For the scrolling, please have a look at the corresponding Gnus
variables. For example, gnus-auto-center-summary appears to be a
relevant variable.
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-02-23 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-22 21:21 James H. Cloos Jr.
2002-02-23 11:42 ` Kai Großjohann
2002-02-23 11:42 ` Kai Großjohann [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-22 21:21 James H. Cloos Jr.
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='a57vhb$i9g$1@quimby2.netfonds.no' \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@hpc.uh.edu \
/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).