On 11/6/2017 2:46 PM, Will Parsons wrote:
>
> But regardless of solving the original problem, I'd still like to know why
> the original script doesn't work under tcsh only.
>
>From what I read of your original thread, it did work. You asked tr to
substitute ':' for '\n' and it did. Your PATH c
On Tuesday, November 07, 2017 7:12 AM Brian Inglis wrote:
>On 2017-11-06 14:59, Will Parsons wrote:
>> Will Parsons wrote:
>>> I asked about what I thought was a shell scripting problem:
>>>
>>> PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/c/Windows/system32:/c/Windows:/c/Windows/system32/wbem:
On 2017-11-06 14:59, Will Parsons wrote:
> Will Parsons wrote:
>> I asked about what I thought was a shell scripting problem:
>>
>> 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 P
Will Parsons wrote:
> I asked about what I thought was a shell scripting problem:
>
> 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/Wi
I asked about what I thought was a shell scripting problem:
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,
Lemke, Michael ST/HZA-ZIC2 wrote:
> On Mon, 6 Nov 2017 00:15:25 + (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, o
Andrey Repin wrote:
> Greetings, Will Parsons!
>
>> 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'
>
> Try
>
> echo "$P
On Mon, 6 Nov 2017 00:15:25 + (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
Greetings, Will Parsons!
> 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'
Try
echo "$PATH"
next time.
Never trust rando
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
10 matches
Mail list logo
