From: Steinar Bang <sb@metis.no>
Subject: Re: no forced authinfo in 5.6.2?
Date: 17 Mar 1998 09:01:47 +0100 [thread overview]
Message-ID: <whd8fliw44.fsf@norne.oslo.metis.no> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Mon, 16 Mar 1998 14:22:42 -0500"
>>>>> "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>:
[...]
> Besides, I also see many advantages to this syntax. When people post
> to the mailing list asking how to make Gnus automatically send
> authinfo for certain servers, I will get a great thrill out of
> replying to them and writing "Use the FORCE tag, Luke!" :-)
Indeed. :-)
I caught a bit of flak from the "point and click" generation about
Gnus needing Emacs lisp customization to be about to force authinfo on
a server, and this sounds like a good line to throw at them at a later
stage...
> Please go ahead and implement it, Lars.
Yep!
next prev parent reply other threads:[~1998-03-17 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-08 20:46 Steinar Bang
[not found] ` <m3iupil26f.fsf@sparky.gnus.org>
1998-03-14 0:06 ` Hallvard B Furuseth
1998-03-16 19:22 ` Edward J. Sabol
1998-03-17 8:01 ` Steinar Bang [this message]
1998-03-19 12:09 ` Lars Magne Ingebrigtsen
1998-03-20 10:44 ` Hallvard B Furuseth
1998-03-19 12:08 ` 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=whd8fliw44.fsf@norne.oslo.metis.no \
--to=sb@metis.no \
/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).