public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew Schulman <schulman.andrew@epamail.epa.gov>
To: cygwin@cygwin.com
Subject: Re: Script to Auto CYGWIN -U all environment varialbes
Date: Tue, 08 Feb 2011 13:44:00 -0000	[thread overview]
Message-ID: <qhh2l6dstmdp8s9a9usp1sgeki5sotrtnv@4ax.com> (raw)
In-Reply-To: <011c01cbc717$766ecfe0$634c6fa0$@com>

> Has anyone written anything into their bash profile or whatever that goes
> through each windows environment variable currently extant, and resets them
> via CYGPATH
> 
> e.g.
> 
> Before, @ start of .bashrc
> ETC=C:\WINDOWS\ETC
> 
> After run of .bashrc
> ETC=`$(cygpath -u '$ETC')`; EXPORT ETC  (--> /cygpath/c/windows/etc)
> 
> Or something like that. So, by the time you hit your cygwin prompt all your
> environment variables are already cleaned up.

Here's my solution.  Ugly quoting, but it works.

I chose to convert just a fixed list of environment variables that I know I
want to convert.  I guess it would be easy to cycle through all environment
variables and 'bashify' any that look like paths, i.e. any that have
backslashes in them.

    # Convert Win32-style paths to Cygwin-style
    function bashify {
        local p
        for p ; do
            if [ "${!p}" ] ; then
                eval 'export '$p'=$(cygpath -pu "$'$p'")'
            fi
        done
    }
    bashify MSDEV PROGRAMFILES WINDIR


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

      parent reply	other threads:[~2011-02-08 13:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07 22:36 Gary Furash
2011-02-07 22:59 ` David Sastre
2011-02-08 13:44 ` Andrew Schulman [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=qhh2l6dstmdp8s9a9usp1sgeki5sotrtnv@4ax.com \
    --to=schulman.andrew@epamail.epa.gov \
    --cc=cygwin@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).