From: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: 'a' to post in *group* buffer should...
Date: 28 Feb 2001 08:17:21 -0800 [thread overview]
Message-ID: <sdae76ixym.fsf@wanderer.hardakers.net> (raw)
In-Reply-To: <sxbbsro9ct5.fsf@torus.tenzing.com> ("Steven E. Harris"'s message of "27 Feb 2001 10:54:30 -0800")
>>>>> On 27 Feb 2001 10:54:30 -0800, "Steven E. Harris" <sharris@speakeasy.org> said:
Steven> I think that "C-u a" does what you're asking for right
Steven> now. Are you proposing that the "C-u" shouldn't be necessary?
Steven> I always forget to hit "C-u."
Hmm. Didn't know about it.
I don't know if it should be necessary or not. Probably configurable
would be the best way to go. I'd have it off, but I bet a lot of
people would want it on.
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~2001-02-28 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 18:48 Wes Hardaker
2001-02-27 18:54 ` Steven E. Harris
2001-02-28 16:17 ` Wes Hardaker [this message]
2001-02-28 16:39 ` Steven E. Harris
2001-03-02 14:46 ` Wes Hardaker
2001-03-02 19:58 ` Kai Großjohann
2001-03-05 21:38 ` Wes Hardaker
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=sdae76ixym.fsf@wanderer.hardakers.net \
--to=wes@hardakers.net \
--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).