Gnus development mailing list
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: One more use for gnus-expert-user
Date: Sat, 05 Jun 2010 07:30:36 +0300	[thread overview]
Message-ID: <87k4qehzir.fsf@mithlond.arda> (raw)
In-Reply-To: <87y6eukyay.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 04 Jun 2010 21:28:37 -0500")

* 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?

I could but I have no idea what "corresponding update" might mean in
this case. The only place where variable gnus-expert-user is mentioned
in the manual (in GNU Emacs 23.2) is section 8.2 Interactive:

    `gnus-expert-user'
         If this variable is non-`nil', you will seldom be asked any
         questions by Gnus.  It will simply assume you know what you're
         doing, no matter how strange.

And that description covers everything.

Section 6.9.6 Agent Expiry is only about user-interface. There is
nothing about files and such things nor about current uses of
gnus-expert-user (which do exist in the expiry mechanism).

So, to be honest, I feel that my patch fits there just fine without
changes in the manual.



  reply	other threads:[~2010-06-05  4:30 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 [this message]
2010-06-05 21:38     ` Ted Zlatanov
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=87k4qehzir.fsf@mithlond.arda \
    --to=tlikonen@iki.fi \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.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).