From: matt_jones@blueyonder.co.uk (Matt N. Jones)
Subject: Re: How to redefine keys?
Date: Mon, 21 Feb 2005 08:19:08 GMT [thread overview]
Message-ID: <m2u0o6pbqm.fsf@siteswap.co.uk> (raw)
In-Reply-To: <87psyurcm0.fsf@nowhere.org>
Glyn Millington <wistanswick@linuxmail.org> writes:
> An alternative approach - putting this in your .gnus will make Gnus
> check whether you _really_ want to send an e-mail in reply instead of
> following up
>
> ;; prompt for mail replies to newsgroups!!!!!
> (defadvice gnus-summary-reply (around reply-in-news activate)
> (interactive)
> (when (or (not (gnus-news-group-p gnus-newsgroup-name))
> (y-or-n-p "REALLY reply with a personal mail? "))
> ad-do-it))
That's fantastic. I've been having exactly the same problem. I've lost
count of the number of times I've accidentally replied with a personal email
when I should have followed up to a newsgroup.
Thanks very much.
Matt
next prev parent reply other threads:[~2005-02-21 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 21:36 Colin Paul Adams
2005-02-20 23:10 ` Jesper Harder
2005-02-21 0:16 ` Glyn Millington
2005-02-21 8:19 ` Matt N. Jones [this message]
[not found] ` <cvc5sn$kgs$1@news.sap-ag.de>
2005-02-21 11:12 ` Glyn Millington
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=m2u0o6pbqm.fsf@siteswap.co.uk \
--to=matt_jones@blueyonder.co.uk \
/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).