public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Enrico Spinielli" <Enrico.Spinielli@marconi.com>
To: "Pavel Tsekov <ptsekov" <ptsekov@syntrex.com>
Cc: "cygwin" <cygwin@cygwin.com>
Subject: Re: semicolon colon separated env vars to unix and viceversa
Date: Thu, 08 Nov 2001 10:13:00 -0000	[thread overview]
Message-ID: <OFC7914ABF.633EFF1F-ONC1256AFE.0063FCEB@uk.marconicomms.com> (raw)

On 08/11/2001 18.54.42 ptsekov wrote:
>
> Ciao, Enrico
>
> You can try the "cygpath" utility to perform this task.
>

That is exactly what I did, but I had to decompose the
list of path before using it...

> Enrico Spinielli wrote:
> >
> > Hi,
> > I wanted to transform my CLASSPATH env var settings (yes, I
> > am using Java :-) from Windows format (semicoln-separated
> > list of win paths) to Unix format (colon separated list of
> > unix paths) and here is an excerpt of the script I have written:
> >      #!/bin/bash
> >      # change an env var from Windows format (semicolon separated)
> >      # to Unix format (colon separated)
> >      IFS=@
> >      for i in ${1//;/@}
> >      do
> >           a=${a}:$(cygpath -u $i)
> >      done
> >      echo $a
> >
> > This works fine but I am wondering if there is something else
> > given that PATH is automatically converted by cygwin...
> >
> > Any idea?
> > bye
> > Enrico


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

             reply	other threads:[~2001-11-08 10:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 10:13 Enrico Spinielli [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-08  9:53 Karr, David
2001-11-08  9:48 Enrico Spinielli
2001-11-08  9:54 ` Pavel Tsekov
2001-11-08 10:13 ` Markus Hoenicka

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=OFC7914ABF.633EFF1F-ONC1256AFE.0063FCEB@uk.marconicomms.com \
    --to=enrico.spinielli@marconi.com \
    --cc=cygwin@cygwin.com \
    --cc=ptsekov@syntrex.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).