From: Sten Drescher <sten.drescher@tivoli.com>
Subject: Re: Xemacs and info
Date: 31 Oct 1996 11:48:38 -0600 [thread overview]
Message-ID: <vpaft3t47d.fsf@dogbert.tivoli.com> (raw)
In-Reply-To: Robert Nicholson's message of 30 Oct 1996 22:27:39 -0500
>>>>> Robert Nicholson writes:
RN> OK so I got my entry in localdir setup. * SGNUS:(gnus). An
RN> NNTP-based newsreader for XEmacs.
RN> Info-directory-list is
RN> Info-directory-list's value is
RN> ("/usr/local/lib/xemacs-19.14/info/" "/usr/local/info")
RN> When I select my node which is defined in /usr/local/info/localdir
RN> it _still_ insists on loading the gnus from the xemacs info
RN> directory.
Yup.
RN> Why?
Because the xemacs info directory is in the info search path
before the local info directory. Try reversing the Info-directory-list.
--
+---------------------- Tivoli Customer Support ----------------------+
| Sten Drescher Tivoli Systems, Inc |
| email: sten.drescher@tivoli.com 9442 Capital of Texas Hwy North |
| phone: (512) 794-9070 Arboretum Plaza One, Suite 500 |
| fax : (512) 345-2784 Austin, Texas 78759 |
+-----------------------------------------------------------------------+
prev parent reply other threads:[~1996-10-31 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-31 3:27 Robert Nicholson
1996-10-31 17:48 ` Sten Drescher [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=vpaft3t47d.fsf@dogbert.tivoli.com \
--to=sten.drescher@tivoli.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).