Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Eichwalder <keichwa@gmx.net>
Subject: Re: Superseding trick not working
Date: Wed, 15 Jan 2003 19:21:36 +0100	[thread overview]
Message-ID: <shy95mff4f.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <iluznq26d98.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 15 Jan 2003 09:14:27 +0100")

Simon Josefsson <jas@extundo.com> writes:

> This looks like a GNKSA feature.  The code indicates that
>
> (add-to-list 'message-shoot-gnksa-feet 'multiple-copies)
>
> would remove the error message.  The manual probably should be
> updated, or the code changed to not use this GNKSA feature when a
> Cancel/Supersede header is present.

Sounds reasonable; thanks for the info.

> Gnus should create and store such a "password" automatically and put
> it in your ~/.emacs, doesn't it?

Okay, it did.  But it's in (custom-set-variables ...) -- the question
is whether Gnus is allowed to touch this form.  I vote to write the
password to say ~/.gnus-canlock-password and read it from there.  I'm I
allowed to change it to something I'm able to remember like "emacs"? ;)

> Fixing whatever bugs in the cancel/supersede seems important IMHO,
> since if there are bugs in that code people will (rightly) get the
> feeling that Cancel Locks are a bad idea since it interfer with how
> they work.

Thanks for your commitment!

-- 
ke@suse.de (work) / keichwa@gmx.net (home):              |
http://www.gnu.franken.de/ke/                            |      ,__o
Free Translation Project:                                |    _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/             |   (*)/'(*)



  reply	other threads:[~2003-01-15 18:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-14 19:36 Karl Eichwalder
2003-01-14 21:43 ` Reiner Steib
2003-01-15 18:16   ` Karl Eichwalder
2003-01-15  8:14 ` Simon Josefsson
2003-01-15 18:21   ` Karl Eichwalder [this message]
2003-01-15 19:08     ` Simon Josefsson
2003-01-15 20:14 ` Lars Magne Ingebrigtsen

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=shy95mff4f.fsf@tux.gnu.franken.de \
    --to=keichwa@gmx.net \
    /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).