Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Authinfo situation
Date: 20 Feb 1998 12:43:41 +0000	[thread overview]
Message-ID: <m390r6fnuq.fsf@org.com> (raw)

Using the new .authinforc authentication setup - very nice-
No more typing in passwords- whoopee

Once I removed the old 'send authinfo' which was making sunsite.auc.dk
ask for authentication and choking. Then qgnus works slicker than bear
grease.


The only problem I have had with it is because I am trying to run
Emacs/qgnus  and Xemacs/With Gnus5.5
When I start Gnus5.5 in Xemacs it  asks for the password, when I insert
it gnus, just sets there with the line drawing of the gnus showing (for
ever).
 
Tried inserting the:
 (add-hook 'nntp-server-opened-hook 'nntp-send-authinfo)
 In .xemacs-options and tried the nosey version too but xemacs isn't
going for it.

To you experienced lispers this is probably no problem and would be
handled with a 'condition statement' in .emacs.

But rather than have to condition different things as I add new stuff,
isn't there a way to make xemacs use a completely different
inititialization file than emacs.

Not just from the command line, but something in .emacs that will make
xemacs look elswhere for its instructions.

I do have this in .emacs but do not really understand what it is
supposed to do.

>(cond
> ((and (string-match "XEmacs" emacs-version)
>       (boundp 'emacs-major-version)
>       (or (and
>            (= emacs-major-version 19)
>            (>= emacs-minor-version 14))
>           (= emacs-major-version 20))
>       (fboundp 'load-options-file))
>  (load-options-file "/home/reader/.xemacs-options")))
  

-- 

Harry Putnam  reader@newsguy.com


             reply	other threads:[~1998-02-20 12:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-20 12:43 Harry Putnam [this message]
1998-02-20 23:02 ` Lars Magne Ingebrigtsen
1998-02-20 15:52   ` Harry Putnam
1998-02-22 17:18     ` 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=m390r6fnuq.fsf@org.com \
    --to=reader@newsguy.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).