Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Vox <vox@gnulinux.org.mx>
Subject: Re: .gnus not being found when I start Gnus, but .emacs is...
Date: Sun, 20 Oct 2002 15:57:51 -0500	[thread overview]
Message-ID: <m2k7kcbzg0.fsf@isis.the-vox.com> (raw)
In-Reply-To: <Xns92AD4AE49BD96chrislak@216.168.3.40>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]


This time Chris <chrisl_ak@hotmail.com> 
becomes daring and writes:

> [posted and mailed]
>
> on 01 Oct 2002, Ed <ed@telestoconsulting.com> spake thusly:
>
>> Howdy all!
>> 
>> I had been messing about with my .gnus file, and also upgraded to a
>> new version of emacs (20.2). All this is on a Windows 200 machine
>> (obviously I have emacs NT).
>> 
>> Somehow emacs stopped finding my .gnus file. I put all my gnus
>> initialization (and there is a lot) into my .emacs file, and
>> everything works fine. I move it back to my .gnus file and gnus
>> breaks. (Hangs trying to find NNTP server).
>
> Did you ever find an answer to this problem? I am having the same 
> problem...

  In your .emacs file add:

  (setq gnus-init-file "~/elisp/gnusrc.el")

  Pointing to the correct .gnus or whatever you want to call it.

  Vox

-- 
Think of the Linux community as a niche economy isolated by its beliefs.  Kind
of like the Amish, except that our religion requires us to use _higher_
technology than everyone else.	     -- Donald B. Marti Jr.

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM d- s:+ a C++++ U++++ P++ L+++ E+ W++ N++ o+ K- w--- 
O- M- V- PS+ PE Y PGP t 5++ X-- R tv+ b+++ DI++ D--- 
G e++ h+ r++ y** 
------END GEEK CODE BLOCK------

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

           reply	other threads:[~2002-10-20 20:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <Xns92AD4AE49BD96chrislak@216.168.3.40>]

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=m2k7kcbzg0.fsf@isis.the-vox.com \
    --to=vox@gnulinux.org.mx \
    /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).