From: craffert@ml.com (Colin Rafferty)
Cc: Roderick Schertler <roderick@gate.net>
Subject: Re: position of point in the *Article* buffer
Date: 29 Feb 1996 16:59:24 -0500 [thread overview]
Message-ID: <ocr20ndaj43.fsf@spssunp.ml.com> (raw)
In-Reply-To: Roderick Schertler's message of Thu, 29 Feb 1996 14:22:04 -0500
Roderick Schertler writes:
> A last idea: How about moving point in the summary buffer to track
> which article you've got in the article buffer? As it is now point sits
> still in the summary buffer, so you've got to find the current article
> yourself if you switch to the summary after reading from the article
> buffer.
I agree with the idea of point following the article in the summary
buffer. However, you can type `h' (gnus-article-show-summary) in the
article buffer to get what you want.
--
Colin Rafferty
Violate the Communications Decency Act.
"...shit, piss, fuck, cunt, cocksucker, mother-fucker, and tits."
-FCC v. Pacifica Foundation 438 U.S. 726 (1978)
next prev parent reply other threads:[~1996-02-29 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-29 19:22 Roderick Schertler
1996-02-29 21:59 ` Colin Rafferty [this message]
1996-03-01 9:04 ` Lars Magne Ingebrigtsen
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=ocr20ndaj43.fsf@spssunp.ml.com \
--to=craffert@ml.com \
--cc=roderick@gate.net \
/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).