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
X-Authentication-Warning: diannao.ittc.ku.edu: james set sender to james AT eecs DOT ku DOT edu using -f
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.4-1: Problem with XEmacs, fonts, and subprocesses.
From: Jerry James <james AT xemacs DOT org>
References: <CFF3E15126A0EF4F96D9FABED7A40266715A49 AT mail DOT i DOT turbinegames DOT com> <3F7F1883 DOT 4070809 AT urth DOT org>
 <20031004230945 DOT GC9651 AT redhat DOT com> <blnm3d$tsg$1 AT sea DOT gmane DOT org>
 <20031005001746 DOT GB10341 AT redhat DOT com>
Date: Sat, 11 Oct 2003 15:13:13 -0500
Message-ID: <pspth3jzxi.fsf@diannao.ittc.ku.edu>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion,
 linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-VirusScan: Clean

I wandered over here to see what was up with the bug report that started
this thread.  Igor's solution works for me.  Thanks, Igor!

Christopher Faylor wrote:
> But seriously, if anyone would like to be an official Xemacs liason and
> officially test snapshots when they happen that would certainly be
> welcome.  I will not be running Xemacs to test things, unfortunately.  I
> would be glad to work with someone who was willing to test debug
> versions of the Cygwin DLL and provide intelligent feedback on problems.

I'll do that.  I'm one of the XEmacs developers, by the way.  Also, if I
take on this role, it is with the caveat that I'm a professor, so I
reserve the right to be pedantic at the drop of a hat.  Er, no, what I
meant to say is that my schedule is somewhat unpredictable, except for
around finals time, when I can confidently predict that I will be
extremely busy.  If you're willing to work with a guy who might take 2
or 3 days to answer your email, I'm your man.

> I'll even give an automatic subscription to cygwin-developers to anyone
> who is willing to perform this service to the community.  I do this
> because I know that Xemacs is a popular package and, despite what I said
> above, I would like to ensure that it works correctly.

So would we XEmacs developers. :-)  It sounds good to me.  What other
lists should I subscribe to?  (I'm not subscribed to any Cygwin lists at
the moment.)

> If someone is interested in doing this perhaps they might also be
> interested in providing an Xemacs package for the cygwin distribution.
> This would be automatically preapproved.

Sure thing.  Do you want X with that?  (I prefer fries.)

Also, FWIW, I compared the environments of an XEmacs started from the
shell (working) and an XEmacs started from an icon (not working).  The
one started from the shell had these environment settings that were not
present in the nonworking version:

"!::=::\\"
"!C:=C:\\cygwin\\bin"
"MAKE_MODE=unix"
"MANPATH=:/usr/ssl/man"
"OLDPWD=/cygdrive/f/build-21.5"
"PKG_CONFIG_PATH=:/usr/X11R6/lib/pkgconfig"
"PROMPT=$P$G"
"PS1=\\[\\033]0;\\w\\007\n\\033[32m\\]\\u@\\h \\[\\033[33m\\w\\033[0m\\]\n$ "
"PWD=/cygdrive/f"
"SHLVL=1"
"TEXMF={/usr/share/lilypond/2.0.1,/usr/share/texmf}"
"USER=[censored by Jerry]"
"_=/usr/local/test/bin/xemacs-21.5-b16.exe"

The PATH variables are different for the two versions, also.  The
difference is that the one started from the shell starts with
"/usr/local/bin:/usr/bin:/bin:", and ends with ":/usr/X11R6/bin", both
of which are missing in the nonworking version.  If I'm reading the FAQ
correctly (http://cygwin.com/faq/faq_4.html#SEC35), this could be the
source of the problem.

Are we doing something wrong, or should the PATH have been magically
modified somehow?
-- 
Jerry James
http://www.ittc.ku.edu/~james/

--
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/