Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: ding@gnus.org
Subject: Re: Congratulations, Larsi
Date: 17 Nov 1998 16:15:57 -0200	[thread overview]
Message-ID: <orvhketcbm.fsf@araguaia.dcc.unicamp.br> (raw)
In-Reply-To: Karl Kleinpaste's message of "17 Nov 1998 12:47:56 -0500"



On Nov 17, 1998, Karl Kleinpaste <karl@justresearch.com> wrote:

> Jonas Luster <jonas@newsbone.org> writes:
>> Gnus p0.44 violates `soft' GNKSA requirements (SHOULDs)
>> in the following way:
>> 10e  Does not let the user indicate which part to followup to

> I believe `C-c C-v' qualifies.  I used it on this message.

I don't think so.  Suppose you've received a digest with several
messages as attachments, and you want to followup to one of the
attached messages, not to the full message.

Anyway, I think gnus can already do that, if you C-d the digest and
followup to some of the individual messages.

>> 16b  Does not refuse posting an empty article
>> 16d  Does not refuse to post quoted text only
>> 16f  Does not try to prevent posting multiple copies entirely

> These are bogus "SHOULDs" anyhow -- I wouldn't want Gnus to do these
> things.  (I often post "empty" notes to our internal newsgroups
> jprc.support.* whose entire [still very useful] content is in the
> Subject -- status messages about things that have been fixed, changed,
> or are otherwise in flux.)

Although gnus currently provides an option for the user to do that, it 
might be nice if it would only do so if a certain variable (custom?)
was set.  If such variable is not enabled, gnus would just refuse to
post such messages, possibly indicating a section of the manual in
order to allow such behavior.  Group parameters could also be used to
selectively enable/disable this.

-- 
Alexandre Oliva  http://www.dcc.unicamp.br/~oliva  aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org.au}
Universidade Estadual de Campinas, SP, Brasil



  parent reply	other threads:[~1998-11-17 18:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-17 17:20 Jonas Luster
1998-11-17 17:45 ` GNKSA (was: Re: Congratulations, Larsi) Per Abrahamsen
1998-11-17 17:54   ` Karl Kleinpaste
1998-11-17 18:08   ` Jonas Luster
1998-11-18  9:17     ` Per Abrahamsen
1998-11-17 17:47 ` Congratulations, Larsi Karl Kleinpaste
1998-11-17 18:12   ` Jonas Luster
1998-11-17 18:15   ` Alexandre Oliva [this message]
1998-11-18  0:54     ` Lars Magne Ingebrigtsen
1998-11-18  3:20       ` Alexandre Oliva
1998-11-18  6:34         ` Lars Magne Ingebrigtsen
1998-11-17 18:18 ` Kai.Grossjohann

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=orvhketcbm.fsf@araguaia.dcc.unicamp.br \
    --to=oliva@dcc.unicamp.br \
    --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).