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

Karl Eichwalder <keichwa@gmx.net> writes:

>> 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.

Gnus uses `customize-save-variable'.  The problem with
~/.gnus-canlock-password is that we'll have yet another ~/.newsrc.eld
file that we must document and be backwards compatible with.  IMHO it
seems better to use an API for handling that, and all the boring stuff
can be hidden inside custom, and documented in one place.  Maybe it is
a good idea to hear what the Emacs gurus feel.

> I'm I allowed to change it to something I'm able to remember like
> "emacs"? ;)

Yup.  Since no servers use it yet, it doesn't even have to be secret
just as long as you remember it.




  reply	other threads:[~2003-01-15 19:08 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
2003-01-15 19:08     ` Simon Josefsson [this message]
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=ilu3cnugrj4.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).