Passing parameters completely untouched

Passing parameters completely untouched

[zzapper]

Hi,
In the same family as previous posting



I want to be able to pass a string with backquotes w/o them being interpreted

eg

> convert_path "c:\aaa\fred\file.txt"

now I KNOW I can do

> convert_path "c:\\aaa\\fred\\file.txt"

 I guess I know that it's impossible (for any shell)
-- 
zzapper
vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?"
http://www.rayninfo.co.uk/tips/ vim, zsh & success tips

Re: Passing parameters completely untouched

[Bart Schaefer]

On May 5, 11:02pm, zzapper wrote:
}
} I want to be able to pass a string with backquotes w/o them being
} interpreted

You mean backslashes, apparently, not backquotes?

} > convert_path "c:\aaa\fred\file.txt"

Use single quotes, man.

> convert_path 'c:\aaa\fred\file.txt'

(I presume "> " is a zsh prompt and not a Windows "MS-DOS Prompt" prompt.
If the latter, you're out of luck.)

Re: Passing parameters completely untouched

[zzapper]

On Fri, 06 May 2005 04:02:07 +0000,  wrote:

>On May 5, 11:02pm, zzapper wrote:
>}
>} I want to be able to pass a string with backslashes w/o them being
>} interpreted

>
>} > convert_path "c:\aaa\fred\file.txt"
>
>Use single quotes, man.
>
Bart,
Doesn't work for me on Cygwin zsh 4.2.4 (i686-pc-cygwin) even with single quotes the backslash is
interpreted.

I've solved my problem though by reading the paste buffer from within the zsh function
-- 
zzapper
vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?"
http://www.rayninfo.co.uk/tips/ vim, zsh & success tips

Re: Passing parameters completely untouched

[Hannu Koivisto]

zzapper <david@tvis.co.uk> writes:

> On Fri, 06 May 2005 04:02:07 +0000,  wrote:

Your MUA's quoting functionality seems a bit broken.

>>On May 5, 11:02pm, zzapper wrote:
...
>>} > convert_path "c:\aaa\fred\file.txt"
>>
>>Use single quotes, man.
>>
> Bart,
> Doesn't work for me on Cygwin zsh 4.2.4 (i686-pc-cygwin) even with
> single quotes the backslash is
> interpreted.

Works fine here with Cygwin zsh 4.2.4:

[prompt] > kala
#!/bin/zsh

echo -E $*
[prompt] chmod +x kala
[prompt] ./kala 'c:\kala\lahna.txt'
c:\kala\lahna.txt

It is probably that convert_path thing of yours that doesn't work.
For example, if I had omitted -E from my example, the output would
have been "c:kalalahna.txt".

-- 
Hannu

Re: Passing parameters completely untouched

[zzapper]

On Fri, 06 May 2005 16:16:01 +0300,  wrote:

>zzapper <david@tvis.co.uk> writes:
>
>> On Fri, 06 May 2005 04:02:07 +0000,  wrote:
>
>Your MUA's quoting functionality seems a bit broken.
>
>>>On May 5, 11:02pm, zzapper wrote:
>...
>>>} > convert_path "c:\aaa\fred\file.txt"
>>>
>>>Use single quotes, man.
>>>
>> Bart,
>> Doesn't work for me on Cygwin zsh 4.2.4 (i686-pc-cygwin) even with
>> single quotes the backslash is
>> interpreted.
>
>Works fine here with Cygwin zsh 4.2.4:
>
>[prompt] > kala
>#!/bin/zsh
>
>echo -E $*
>[prompt] chmod +x kala
>[prompt] ./kala 'c:\kala\lahna.txt'
>c:\kala\lahna.txt
>
>It is probably that convert_path thing of yours that doesn't work.
>For example, if I had omitted -E from my example, the output would
>have been "c:kalalahna.txt".

Hannu,
Thnx that works fine with echo -E

Funny the doc says that -E is default?!?

-E     disable interpretation of backslash escapes (default)




-- 
zzapper
vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?"
http://www.rayninfo.co.uk/tips/ vim, zsh & success tips

Re: Passing parameters completely untouched

[Bart Schaefer]

On May 6,  2:27pm, zzapper wrote:
}
} Thnx that works fine with echo -E
} 
} Funny the doc says that -E is default?!?
} 
} -E     disable interpretation of backslash escapes (default)

Are you perhaps reading the doc for Cygwin's /bin/echo?  The Zsh doc entry
for the echo builtin looks like this:

----------
echo [ -neE ] [ ARG ... ]
     Write each ARG on the standard output, with a space separating
     each one.  If the -n flag is not present, print a newline at the
     end.  echo recognizes the following escape sequences:

    \a
          bell character
    [...and so on for other escapes...]
    \UNNNNNNNN
          unicode character code in hexadecimal

     The -E flag, or the BSD_ECHO option, can be used to disable these
     escape sequences.  In the latter case, -e flag can be used to
     enable them.
----------

Re: Passing parameters completely untouched

[zzapper]

On Fri, 06 May 2005 15:16:30 +0000,  wrote:

>On May 6,  2:27pm, zzapper wrote:
>}
>} Thnx that works fine with echo -E
>} 
>} Funny the doc says that -E is default?!?
>} 
>} -E     disable interpretation of backslash escapes (default)
>
>Are you perhaps reading the doc for Cygwin's /bin/echo?  The Zsh doc entry
>for the echo builtin looks like this:
>
drat!,  I un-thinkingly do a >man echo

http://zsh.sunsite.dk/Doc/Release/index-frame.html
-- 
zzapper
vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?"
http://www.rayninfo.co.uk/tips/ vim, zsh & success tips

Re: Passing parameters completely untouched

[zzapper]

Hi,thanx to all!

Of course the moral here is that it wasn't the parameter passing that was changing my parameters but
rather echo itself!!!

-- 
zzapper
vim -c ":%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg?"
http://www.rayninfo.co.uk/tips/ vim, zsh & success tips