Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <4024F1AD.7030008@cox.net>
Date: Sat, 07 Feb 2004 09:09:49 -0500
From: "David A. Cobb" <Superbiskit AT cox DOT net>
Reply-To: Cygwin General Discussion <cygwin AT cygwin DOT com>,
   "David A. Cobb" <superbiskit AT cox DOT net>
User-Agent: Mozilla Thunderbird 0.5b (Windows/20040204)
MIME-Version: 1.0
To: Cygwin General Discussion <cygwin AT cygwin DOT com>
Subject: Xemacs not finding things in a reasonable place
Content-Type: multipart/mixed; boundary="------------080302000702020609080103"
X-IsSubscribed: yes

--------------080302000702020609080103
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

My Cygwin-provided version of Xemacs was complaining upon launch about 
not finding things in a reasonable place.
I see that the latest update notes a "workaround".  It could, I believe, 
be corrected by appropriate entries in
`path.c'.  This would still leave our version rather different from the 
upstream one, because the "normal" place for things is in
`/usr/local/lib/$EMACSVERSION/$MACHTYPE' -- very much not in the spirit 
of the FHS layout.

The most-critical thing to note is that the executable searches among 
its "cousins."  When we put the exe in
/usr/bin while the lisp remained in /usr/share/$EMACSVERSION, we made 
the search fail.  A very simple correction,
used in the standard distribution, is to place the executable in 
`/usr/share/$EMACSVERSION/$MACHTYPE' and the
lisp where it is in `/usr/share/$EMACSVERSION/lisp' -- then put a link 
in `/usr/bin'.

Similarly, the associated binaries could well be in the same directory 
with the executable.
And the DOC and whatever data files in `/usr/share/$EMACSVERSION/etc'.

Finally, a `/etc/profile.d/xemacs.sh' script to set up $EMACSPATH => 
<path to associated binaries>,
$EMACSDATA => <path to DOC and data files>, and $EMACSLOADPATH => <path 
to lisp> should do the trick.

-- 
David A. Cobb, Software Engineer, Public Access Advocate
"By God's Grace, I am a Christian man; by my actions a great sinner." -- The Way of a Pilgrim: R.French, Tr.
Life is too short to tolerate crappy software!




--------------080302000702020609080103
Content-Type: text/x-vcard; charset=utf8;
 name="Superbiskit.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="Superbiskit.vcf"

begin:vcard
fn:David A. Cobb
n:Cobb;David A.
adr:;;7 Lenox Av #1;West Warwick;RI;02893-3918;USA
email;internet:Superbiskit AT cox DOT net
title:Independent Software Consultant
x-mozilla-html:TRUE
version:2.1
end:vcard



--------------080302000702020609080103
Content-Type: text/plain; charset=us-ascii

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/
--------------080302000702020609080103--