Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: missing sha1-maximum-internal-length
Date: Wed, 14 Jan 2004 08:05:57 +0900	[thread overview]
Message-ID: <b9yn08rqwiy.fsf@jpl.org> (raw)
In-Reply-To: <yovazncr259y.fsf@relaskop.wsl.ch>

>>>>> In <yovazncr259y.fsf@relaskop.wsl.ch>
>>>>>	Adrian Lanz <lanz@fowi.ethz.ch> wrote:

> On 13 Jan 2004, yamaoka@jpl.org wrote:

>> Probably, it is because sha1-maximum-internal-length is bound to
>> nil in the message-canlock-generate function when sha1-el.el is
>> autoloaded.  I've fixed it in CVS.

> That solved the problem for me. Thanks for the prompt fix!

Thanks for the confirmation.

> BTW and always on search of a sane configuration for my system: do you
> think I have some special/wrong configuration, as nobody else on the
> list claimed having had the sha-el problem?

> Thanks, Adrian.

You are not wrong.  There won't be those who have set the
canlock-password variable in advance.  Since it is required for
posting, canceling and superseding news articles, Gnus will
generate and save the value automatically using sha1-el only at
the first time.  The problem arises just at that time.  However,
people will forget it wholly, since it does not occur in the
second time. :)
-- 
Katsumi Yamaoka <yamaoka@jpl.org>



      reply	other threads:[~2004-01-13 23:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13  7:51 Adrian Lanz
2004-01-13  9:03 ` Simon Josefsson
2004-01-13 13:39   ` Katsumi Yamaoka
2004-01-13 16:16     ` Adrian Lanz
2004-01-13 23:05       ` Katsumi Yamaoka [this message]

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=b9yn08rqwiy.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --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).