public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygx <cygwin-xfree@cygwin.com>
Subject: Re: cygwin/xfree86/emacs problems after upgrading
Date: Thu, 05 Feb 2004 00:48:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0402041943420.17546@slinky.cs.nyu.edu> (raw)
In-Reply-To: <40218BC0.3010100@msu.edu>

On Wed, 4 Feb 2004, Harold L Hunt II wrote:

> Igor,
>
> > This (and the existence of CYGWIN_ROOT in your environment) is an artifact
> > of using startxwin.bat.  Unless you have a default directory for the
> > Cygwin root, you can't use that file OOTB -- you'll have to edit it and
> > replace "\cygwin" with the value of your Cygwin root (in your case,
> > "d:\ProgramFiles\Cygwin".
> >
> >> CYGWIN_ROOT = `\cygwin'
> >
>
> Well, you can always just set CYGWIN_ROOT to \ProgramFiles\Cygwin, with
> no leading drive letter and colon.  I think you probably knew that
> already...  I am still amazed at the number of times I have seen people
> go in and change \cygwin to c:\cygwin when they have problems... even
> after reading my comment immediately above it that describes why doing
> this is not necessary.  Sheesh, I thought it was a quite beautiful trick
> to allow the path to be set correctly no matter what drive the cygwin
> folder is on.  :)
>
> Harold

Yes, it's a neat trick *if* the only thing people changed was the install
drive.  If they change the path, all bets are off.  I'm surprised you
don't actually customize startxwin.bat (and similar files, like
startxdmcp.bat) in a postinstall script (which can run under a Cygwin
shell, and thus know the root of the install).  You could choose a
template value, e.g. "%$CYGWIN_ROOT$%", and replace that with "`cygpath -w
/`" using, say, sed.  If you're interested, I could whip up an example
postinstall script for you in the next week or so.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton


  reply	other threads:[~2004-02-05  0:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05  0:18 Harold L Hunt II
2004-02-05  0:48 ` Igor Pechtchanski [this message]
2004-02-26 17:46   ` Takuma Murakami
2004-02-26 20:53     ` Igor Pechtchanski
2004-02-27  8:41       ` Igor Pechtchanski
     [not found] <mailman.1828.1075842639.928.help-gnu-emacs@gnu.org>
2004-02-08  8:51 ` Jari Aalto+mail.linux
  -- strict thread matches above, loose matches on Subject: below --
2004-02-03 21:10 Thomas L Roche
2004-02-04 21:21 ` Igor Pechtchanski

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=Pine.GSO.4.56.0402041943420.17546@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin-xfree@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).