From: amu@MIT.EDU (Aaron M. Ucko)
Subject: Re: still puzzled by what should be a common idiom
Date: 06 Jul 1999 19:04:56 -0400 [thread overview]
Message-ID: <udlso71idlz.fsf@tux.mit.edu> (raw)
In-Reply-To: Bill White's message of "06 Jul 1999 18:39:29 -0400"
Bill White <billw@wolfram.com> writes:
> '/ n' narrows to articles marked with #. You can then use '/ w' to
> widen the Summary buffer back to the way it was before the narrowing.
Oops, that works too. I still think `/ m #' ought to work for
consistency, though.
--
Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu)
next prev parent reply other threads:[~1999-07-06 23:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-06 18:08 Randal L. Schwartz
1999-07-06 18:43 ` Aaron M. Ucko
1999-07-08 7:04 ` Lars Magne Ingebrigtsen
1999-07-06 19:32 ` Neil Crellin
1999-07-06 23:10 ` Harry Putnam
1999-07-07 22:32 ` Randal L. Schwartz
1999-07-06 22:36 ` Bill White
1999-07-06 23:04 ` Aaron M. Ucko [this message]
1999-07-06 23:34 ` François Pinard
1999-07-07 1:41 ` Aaron M. Ucko
1999-07-07 9:55 ` Kai.Grossjohann
1999-07-07 7:21 Jaap-Henk Hoepman
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=udlso71idlz.fsf@tux.mit.edu \
--to=amu@mit.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).