Gnus development mailing list
 help / color / mirror / Atom feed
From: Steven L Baur <steve@miranova.com>
Subject: Re: September Gnus 0.31 is released
Date: 26 Jan 1996 09:37:47 -0800	[thread overview]
Message-ID: <m2ohrqeu1g.fsf@miranova.com> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 26 Jan 1996 08:46:09 -0800

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

Lars> Steven L Baur <steve@miranova.com> writes:
>> When changing the pointer to the glyph directory for XEmacs, you need
>> to add the gnus subdirectory now:
>> 
>> (setq gnus-xmas-glyph-directory "/usr/local/lib/xemacs/etc-0.4/gnus/")

Lars> Or you can rename "etc-0.4" to "etc" and put it in the "sgnus"
Lars> directory.  Gnus searches the load path, strips off trailing "lisp"
Lars> elements from the paths and sees whether it can find the "etc/gnus"
Lars> directory.

I assume you mean:
$ cd /usr/local/lib/xemacs/sgnus-0.32
$ ls -l
-rw-r--r--   1 steve    devel         161 Jan 26 08:11 Makefile
lrwxrwxrwx   1 steve    devel          12 Jan 26 08:10 RCS -> ../sgnus/RCS/
lrwxrwxrwx   1 steve    devel          10 Jan 26 09:30 etc -> ../etc-0.4/
drwxr-xr-x   2 steve    devel        2048 Jan 26 08:21 lisp/
-rw-r--r--   1 steve    devel        1893 Jan 26 08:11 readme
drwxr-xr-x   2 steve    devel        1024 Jan 26 08:11 texi/

I don't have a problem adding this link by hand, since I run a script
anyway to link new source trees to the RCS tree I keep.  But perhaps
for the non-beta releases you could put that symbolic link in the
distribution.

-- 
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.


  reply	other threads:[~1996-01-26 17:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-25 16:12 Lars Magne Ingebrigtsen
1996-01-25 18:36 ` Steven L Baur
1996-01-25 21:50   ` Wes Hardaker
1996-01-25 22:44   ` luis fernandes
1996-01-26  1:07     ` Steven L Baur
1996-01-26 15:28     ` Colin Rafferty
1996-01-26 17:47       ` Wes Hardaker
1996-01-26 17:48       ` Steven L Baur
1996-01-27 20:33       ` Lars Magne Ingebrigtsen
1996-01-26 16:46   ` Lars Magne Ingebrigtsen
1996-01-26 17:37     ` Steven L Baur [this message]
1996-01-27 20:33       ` Lars Magne Ingebrigtsen
1996-01-28  0:13         ` Steven L Baur
1996-01-30 16:29           ` Lars Magne Ingebrigtsen
1996-01-25 23:54 ` srivasta
1996-01-26 19:33   ` Mark Borges
1996-01-26 20:28     ` Steven L Baur
1996-01-26 20:29     ` Manoj Srivastava
1996-01-26 20:39     ` Colin Rafferty
1996-01-26 20:50     ` Mark Borges
1996-01-26 23:17       ` Steven L Baur

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=m2ohrqeu1g.fsf@miranova.com \
    --to=steve@miranova.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).