Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Why can't `gnus-draft-setup' be bytecompiled?
Date: 13 Mar 1998 22:39:32 +0100	[thread overview]
Message-ID: <m31zw6l17v.fsf@sparky.gnus.org> (raw)
In-Reply-To: Hrvoje Niksic's message of "10 Mar 1998 00:19:27 +0100"

From owner-ding@hpc.uh.edu  Fri Mar 13 14:36:19 1998
Return-Path: <owner-ding@hpc.uh.edu>
Received: from xemacs.org (xemacs.cs.uiuc.edu [128.174.252.16])
	by altair.xemacs.org (8.8.8/8.8.8) with ESMTP id OAA04416
	for <steve@altair.xemacs.org>; Fri, 13 Mar 1998 14:36:18 -0800
Received: from gizmo.hpc.uh.edu (gizmo.hpc.uh.edu [129.7.102.31])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id QAA25707
	for <steve@xemacs.org>; Fri, 13 Mar 1998 16:31:04 -0600 (CST)
Received: from sina.hpc.uh.edu (sina.hpc.uh.edu [129.7.3.5]) by gizmo.hpc.uh.edu (8.7.6/8.7.3) with ESMTP id RAS09966; Fri, 13 Mar 1998 17:05:50 -0600
Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 13 Mar 1998 16:27:04 -0600 (CST)
Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by sina.hpc.uh.edu (8.7.3/8.7.3) with SMTP id QAA15029 for <ding@hpc.uh.edu>; Fri, 13 Mar 1998 16:25:54 -0600 (CST)
Received: (qmail 6630 invoked by uid 504); 13 Mar 1998 22:25:41 -0000
Received: (qmail 6627 invoked from network); 13 Mar 1998 22:25:40 -0000
Received: from xyplex35.uio.no (HELO sparky.gnus.org) (129.240.154.55)
  by claymore.vcinet.com with SMTP; 13 Mar 1998 22:25:13 -0000
Received: (from larsi@localhost)
	by sparky.gnus.org (8.8.5/8.8.5) id XAA06882;
	Fri, 13 Mar 1998 23:19:51 +0100
Mail-Copies-To: never
To: ding@gnus.org
Subject: Re: no forced authinfo in 5.6.2?
References: <whzpj07vxd.fsf@norne.oslo.metis.no>
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Date: 13 Mar 1998 22:18:48 +0100
In-Reply-To: Steinar Bang's message of "08 Mar 1998 21:46:22 +0100"
Message-ID: <m3iupil26f.fsf@sparky.gnus.org>
X-Mailer: Gnus v5.6.3/Emacs 19.34
X-Face: &w!^oO<W.WBH]FsTP:P0f9X6M-ygaADlA_)eF$<UwQzj7:C=Gi<a?/_4$LX^@$Qq7-O&XHp
 lDARi8e8iT<(A$LWAZD*xjk^')/wI5nG;1cNB>~dS|}-P0~ge{$c!h\<y
Lines: 13
Sender: owner-ding@hpc.uh.edu
Precedence: list
X-Majordomo: 1.94.jlt7

Steinar Bang <sb@metis.no> writes:

> I just looked at the nntp.el in 5.6.2, doesn't seem to be any code
> there looking for some way to force authinfo on an NNTP server that
> doesn't ask for it.
> 
> Was this dropped because people disagreed with the proposed syntax?

Well, I didn't feel it was resolved.  Should I add a "force" tag?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1998-03-13 21:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-09 23:01 SL Baur
1998-03-09 23:19 ` Hrvoje Niksic
1998-03-13 21:39   ` Lars Magne Ingebrigtsen [this message]
1998-03-14  3:11   ` Hallvard B Furuseth
1998-03-14  3:23     ` Hrvoje Niksic
1998-03-14  4:09       ` Aaron M. Ucko
1998-03-19 12:30         ` Lars Magne Ingebrigtsen
1998-03-21  2:09           ` Aaron M. Ucko
1998-03-23 13:15             ` Lars Magne Ingebrigtsen
1998-03-14  2:29 ` Hallvard B Furuseth
1998-03-19 12:25   ` 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=m31zw6l17v.fsf@sparky.gnus.org \
    --to=larsi@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).