Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: cancel locks
Date: Wed, 31 Oct 2001 18:45:37 +0100	[thread overview]
Message-ID: <ilug07z7lfi.fsf@dhcp128.extundo.com> (raw)

Cancel locks is part of Gnus now, so maybe it should be integrated
better.  How/when should the cancel lock password be
initialized/generated?  Maybe a popup question similar to when you try
to use C-x n n the first time?  It could appear when you try to post
an article the first time?  Should Gnus really generate this password,
as has been suggested previously? (If so, you're restricted to using
only one installation of Gnus which has access to the same generated
password.  And you can't lose the file.  No, the user should chose the
password.)

On the other hand, as cancel locks isn't something that is commonly
supported out there, maybe Gnus shouldn't worry about it by default?
On the third hand, if this stuff just happens in the background, the
user probably wouldn't care, and it might be nice to have cancel locks
in all Gnus posts.




             reply	other threads:[~2001-10-31 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-31 17:45 Simon Josefsson [this message]
2001-10-31 18:11 ` Bjørn Mork
2001-10-31 19:06   ` Simon Josefsson
2001-11-01  0:13     ` Robin S. Socha
2001-11-01 11:28     ` Florian Weimer
2001-11-01  8:23 ` Per Abrahamsen
2001-11-01 11:34   ` Florian Weimer
2001-11-01 11:59     ` Per Abrahamsen
2001-11-01 16:34       ` Matt Armstrong
2001-11-01 17:21         ` Per Abrahamsen
2001-11-01 17:41         ` Jesper Harder
2001-11-01 17:23           ` Simon Josefsson
2001-11-01 18:47             ` Matt Armstrong
2001-11-01 21:09               ` Florian Weimer
2001-11-01 21:10             ` Florian Weimer

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=ilug07z7lfi.fsf@dhcp128.extundo.com \
    --to=jas@extundo.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).