From: William Goedicke <goedicke@world.std.com>
Subject: Re: Making read and ticked articles visible
Date: 30 Jul 2002 14:47:07 -0400 [thread overview]
Message-ID: <m3fzy1aw9g.fsf@nuthatch.booksonbits.com> (raw)
In-Reply-To: <m3lm7tgpuo.fsf@multivac.cwru.edu>
Dear Paul -
prj@po.cwru.edu (Paul Jarc) writes:
> William Goedicke <goedicke@world.std.com> wrote:
> > I would like, on occasion to make "read" articles visible in a
> > summary buffer that has "ticked" articles.
>
> Type / o in the *Summary* buffer or enter the group with C-u RET.
Mini-buffer says "/ o not defined" Sigghhh.... Do you know what
command you have that mapped to?
--
Yours - Billy
============================================================
William Goedicke goedicke@world.std.com
http://world.std.com/~goedicke
============================================================
Lest we forget:
We are all insecure.
- Joan Menard
next prev parent reply other threads:[~2002-07-30 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 11:11 New Stock Alert ptm Theodore Williamson
2002-07-30 16:02 ` Making read and ticked articles visible William Goedicke
2002-07-30 16:08 ` Paul Jarc
2002-07-30 18:47 ` William Goedicke [this message]
2002-07-30 18:53 ` Paul Jarc
2002-07-31 10:45 ` Kai Großjohann
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=m3fzy1aw9g.fsf@nuthatch.booksonbits.com \
--to=goedicke@world.std.com \
/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).