From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Problems starting Oort Gnus 0.13
Date: Fri, 24 Jan 2003 19:44:14 +0100 [thread overview]
Message-ID: <m37kcu9ym9.fsf@defun.localdomain> (raw)
In-Reply-To: <u8yxaaane.fsf@softechnics.com>
jeff.rancier@softechnics.com (Jeffery B. Rancier) writes:
> The error which *appeared* to prevent me from running it was:
>
> Reading h:/HOME/JRANCIER/.newsrc.eld...
> gnus-read-newsrc-file: Symbol's value as variable is void: gnus-default-format-specs
>
> It appears that the Gnus within the Emacs tarball was loading
Yes, it does. Do `M-x list-load-path-shadows' to see if the default
Gnus installation shadows the Oort installation.
> | TinyPath: tinypath-cache-p-1-new ASSOC ("gnus-ems.elc" (2213 . "c:/usr/pkg/emacs-21.2/lisp/gnus/"))
> | TinyPath: cache hit: gnus-ems [c:/usr/pkg/emacs-21.2/lisp/gnus/gnus-ems.elc]
What's this TinyPath stuff? I don't know anything about it, but maybe
it needs to configured to somehow find Oort.
prev parent reply other threads:[~2003-01-24 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 14:24 Jeffery B. Rancier
2003-01-24 18:44 ` Jesper Harder [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=m37kcu9ym9.fsf@defun.localdomain \
--to=harder@myrealbox.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).