public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* strange shell output using tcsh under Cygwin
@ 2017-11-06  0:15 Will Parsons
  2017-11-06  2:50 ` Andrey Repin
  2017-11-06 21:48 ` tcsh path conversion messed up? [was: strange shell output using tcsh under Cygwin] Will Parsons
  0 siblings, 2 replies; 12+ messages in thread
From: Will Parsons @ 2017-11-06  0:15 UTC (permalink / raw)
  To: cygwin

Under Unix-type platforms, checking on what the PATH variable is set to is
pretty easy - I typically use "env" and the displayed value of PATH is easily
parsed by eye.  Under Cygwin/Windows, one can do the same, but the value of
PATH is more likely to be considerably more complicated and harder for a
human to parse.  For example, this is what I see on my local machine under
Cygwin:

   PATH=/usr/local/bin:/usr/bin:/c/Windows/system32:/c/Windows:/c/Windows/system32/wbem:/c/ProgramData/Oracle/Java/javapath:/c/Program Files/Common Files/Microsoft Shared/Windows Live:/c/Program Files (x86)/Common Files/Microsoft Shared/Windows Live:/c/Program Files/Dell/DW WLAN Card:/c/Program Files (x86)/Intel/iCLS Client:/c/Program Files/Intel/iCLS Client:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/WIDCOMM/Bluetooth Software:/c/Program Files/WIDCOMM/Bluetooth Software/syswow64:/c/Program Files (x86)/Windows Live/Shared:/c/Program Files (x86)/Bazaar:/c/Program Files (x86)/QuickTime/QTSystem:/c/cygwin/home/william/bin:/c/ezwinports/bin:/c/Program Files (x86)/PuTTY:/usr/lib/lapack:/usr/sbin:/c/msys/1.0/local/bin

I thought it would be nice to write a simple script to make this more
comprehensible by breaking the path into separate lines, and so wrote the
following trivial script:

   #!/bin/sh
   echo $PATH | tr ':' '\n'

Oddly though, it does not give the expected results under Cygwin.  Running
this script under Cygwin under my normal interactive script (tcsh) yields the
following:

   % ./path
   /usr/local/bin
   /usr/bin
   /bin
   /usr/sbin
   /c/Windows/system32
   /c/Windows
   /c/Windows/system32/wbem
   /c/ProgramData/Oracle/Java/javapath
   /c/Program
   Files/Common
   Files/Microsoft
   Shared/Windows
   Live
   /c/Program
   Files
   (x86)/Common
   Files/Microsoft
   Shared/Windows
   Live
   /c/Program
   Files/Dell/DW
   WLAN
   Card
   /c/Program
   Files
   (x86)/Intel/iCLS
   Client
   /c/Program
   Files/Intel/iCLS
   Client
   /c/Windows/System32/WindowsPowerShell/v1.0
   /c/Program
   Files/WIDCOMM/Bluetooth
   Software
   /c/Program
   Files/WIDCOMM/Bluetooth
   Software/syswow64
   /c/Program
   Files
   (x86)/Windows
   Live/Shared
   /c/Program
   Files
   (x86)/Bazaar
   /c/Program
   Files
   (x86)/QuickTime/QTSystem
   /c/cygwin/home/william/bin
   /c/ezwinports/bin
   /c/Program
   Files
   (x86)/PuTTY
   /usr/lib/lapack

Clearly the path is being broken using spaces as well as colons.

Even thoush the shell script itself explicitly specifies "/bin/sh", the
result seems to depend on the shell being used to invoke it.  Using Cugwin
bash, the same script results in the following:

   sothis$ ./path
   /usr/local/bin
   /usr/bin
   /c/Windows/system32
   /c/Windows
   /c/Windows/system32/wbem
   /c/ProgramData/Oracle/Java/javapath
   /c/Program Files/Common Files/Microsoft Shared/Windows Live
   /c/Program Files (x86)/Common Files/Microsoft Shared/Windows Live
   /c/Program Files/Dell/DW WLAN Card
   /c/Program Files (x86)/Intel/iCLS Client
   /c/Program Files/Intel/iCLS Client
   /c/Windows/System32/WindowsPowerShell/v1.0
   /c/Program Files/WIDCOMM/Bluetooth Software
   /c/Program Files/WIDCOMM/Bluetooth Software/syswow64
   /c/Program Files (x86)/Windows Live/Shared
   /c/Program Files (x86)/Bazaar
   /c/Program Files (x86)/QuickTime/QTSystem
   /c/cygwin/home/william/bin
   /c/ezwinports/bin
   /c/Program Files (x86)/PuTTY
   /usr/lib/lapack
   /usr/sbin
   /c/msys/1.0/local/bin

For comparison, I tried running the same script under FreeBSD (where tcsh is
also my normal interactive shell).  Since paths with spaces are quite rare
under Unix-type systems, I added a dummy 'x x' (imaginary directory) to the
path.  The result was as follows:

   % ./path
   /sbin
   /bin
   /usr/sbin
   /usr/bin
   /home/william/bin
   /home/william/.gem/ruby/2.3/bin
   /usr/local/sbin
   /usr/local/bin
   x x

So, I am quite puzzled.

-- 
Will


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

^ permalink raw reply	[flat|nested] 12+ messages in thread
* Re: strange shell output using tcsh under Cygwin
@ 2017-11-06 11:42 Lemke, Michael  ST/HZA-ZIC2
  2017-11-06 19:46 ` Will Parsons
  0 siblings, 1 reply; 12+ messages in thread
From: Lemke, Michael  ST/HZA-ZIC2 @ 2017-11-06 11:42 UTC (permalink / raw)
  To: cygwin

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1984 bytes --]

On Mon, 6 Nov 2017 00:15:25 +0000 (UTC)
Will Parsons wrote:

>Under Unix-type platforms, checking on what the PATH variable is set to is
>pretty easy - I typically use "env" and the displayed value of PATH is easily
>parsed by eye.  Under Cygwin/Windows, one can do the same, but the value of
>PATH is more likely to be considerably more complicated and harder for a
>human to parse.  For example, this is what I see on my local machine under
>Cygwin:
>
>   PATH=/usr/local/bin:/usr/bin:/c/Windows/system32:/c/Windows:/c/Windows/system32/wbem:/c/ProgramData/Oracle/Java/javapath:/c/Program Files/Common Files/Microsoft Shared/Windows Live:/c/Program Files (x86)/Common Files/Microsoft Shared/Windows Live:/c/Program Files/Dell/DW WLAN Card:/c/Program Files (x86)/Intel/iCLS Client:/c/Program Files/Intel/iCLS Client:/c/Windows/System32/WindowsPowerShell/v1.0:/c/Program Files/WIDCOMM/Bluetooth Software:/c/Program Files/WIDCOMM/Bluetooth Software/syswow64:/c/Program Files (x86)/Windows Live/Shared:/c/Program Files (x86)/Bazaar:/c/Program Files (x86)/QuickTime/QTSystem:/c/cygwin/home/william/bin:/c/ezwinports/bin:/c/Program Files (x86)/PuTTY:/usr/lib/lapack:/usr/sbin:/c/msys/1.0/local/bin
>
>I thought it would be nice to write a simple script to make this more
>comprehensible by breaking the path into separate lines, and so wrote the
>following trivial script:
>
>   #!/bin/sh
>   echo $PATH | tr ':' '\n'
>
>Oddly though, it does not give the expected results under Cygwin.

As you wrote you are using tcsh try this:

#!/bin/tcsh
foreach i ( `seq 1 $#path` )
  echo $path[$i]
end

Or this slightly faster one:

#!/bin/tcsh
@ i = 1
while ( $i < $#path )
  echo $path[$i]
  @ i++
end


Lookup arrays in tcsh.

\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

^ permalink raw reply	[flat|nested] 12+ messages in thread
end of thread, other threads:[~2017-11-08 11:54 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-06  0:15 strange shell output using tcsh under Cygwin Will Parsons
2017-11-06  2:50 ` Andrey Repin
2017-11-06 19:14   ` Will Parsons
2017-11-06 21:48 ` tcsh path conversion messed up? [was: strange shell output using tcsh under Cygwin] Will Parsons
2017-11-06 21:59   ` Will Parsons
2017-11-07  6:12     ` Brian Inglis
2017-11-07  9:08       ` Lemke, Michael  ST/HZA-ZIC2
2017-11-07 22:08         ` [SOLVED] Re: tcsh path conversion messed up? Will Parsons
2017-11-08 11:54           ` Lemke, Michael  ST/HZA-ZIC2
2017-11-06 11:42 strange shell output using tcsh under Cygwin Lemke, Michael  ST/HZA-ZIC2
2017-11-06 19:46 ` Will Parsons
2017-11-07 14:58   ` cyg Simple

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).