From: Ted Zlatanov <tzz@lifelogs.com>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: ding@gnus.org
Subject: Re: One more use for gnus-expert-user
Date: Sat, 05 Jun 2010 16:38:56 -0500 [thread overview]
Message-ID: <87d3w540sv.fsf@lifelogs.com> (raw)
In-Reply-To: <87k4qehzir.fsf@mithlond.arda> (Teemu Likonen's message of "Sat, 05 Jun 2010 07:30:36 +0300")
On Sat, 05 Jun 2010 07:30:36 +0300 Teemu Likonen <tlikonen@iki.fi> wrote:
TL> * 2010-06-04 21:28 (-0500), Ted Zlatanov wrote:
>> On Sat, 29 May 2010 09:40:53 +0300 Teemu Likonen <tlikonen@iki.fi> wrote:
TL> Here's a patch that implements my suggestion:
TL> diff --git i/lisp/gnus/gnus-agent.el w/lisp/gnus/gnus-agent.el
>> I'm OK with this (although it's pretty esoteric for most users), but
>> the Gnus manual should be updated correspondingly as well. Can you
>> include that in your patch?
TL> I could but I have no idea what "corresponding update" might mean in
TL> this case. The only place where variable gnus-expert-user is mentioned
TL> in the manual (in GNU Emacs 23.2) is section 8.2 Interactive:
TL> `gnus-expert-user'
TL> If this variable is non-`nil', you will seldom be asked any
TL> questions by Gnus. It will simply assume you know what you're
TL> doing, no matter how strange.
(removing emacs-devel for now)
Hmm, I could have sworn that variable was covered in more detail.
Sorry. Here's a manual change that lists some of the more interesting
uses of gnus-expert-user; I omitted the agent expiry. WDYT?
Thanks
Ted
diff --git a/texi/gnus.texi b/texi/gnus.texi
index abb84de..a921cc6 100644
--- a/texi/gnus.texi
+++ b/texi/gnus.texi
@@ -22906,8 +22906,11 @@ default.
@item gnus-expert-user
@vindex gnus-expert-user
If this variable is non-@code{nil}, you will seldom be asked any
-questions by Gnus. It will simply assume you know what you're doing, no
-matter how strange.
+questions by Gnus. It will simply assume you know what you're doing,
+no matter how strange. For example, quitting Gnus, exiting a group
+without an update, catching up with a group, deleting expired
+articles, and replying by mail to a news message will not require
+confirmation.
@item gnus-interactive-catchup
@vindex gnus-interactive-catchup
next prev parent reply other threads:[~2010-06-05 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 6:40 Teemu Likonen
2010-06-05 2:28 ` Ted Zlatanov
2010-06-05 4:30 ` Teemu Likonen
2010-06-05 21:38 ` Ted Zlatanov [this message]
2010-06-06 8:51 ` Teemu Likonen
2010-06-07 16:20 ` Ted Zlatanov
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=87d3w540sv.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=tlikonen@iki.fi \
/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).