[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: avoid interpretation of \n, \t, ... in string

From: Kevin Rodgers
Subject: Re: avoid interpretation of \n, \t, ... in string
Date: Wed, 28 Jan 2009 00:52:16 -0700
User-agent: Thunderbird (Macintosh/20081209)

Peter Tury wrote:
I would like to pass paths to shell (extrenal command line programs)
on MS Windows. The paths may contain \n, \t etc. (Eg. c:
\directory-1\new-dir\temp...). However, the string is "evaluated" and
only the result arrives to the shell program. (In the above example: c:
ew-dir  emp...)

I try to use `call-process-shell-command'.

I know I could use double back-slash (e.g. c:\directory-1\\new-dir\
\temp...), but I want to be able to handle any paths in their
"natural" form. How to do it?

Where do these strings come from?

Kevin Rodgers
Denver, Colorado, USA

reply via email to

[Prev in Thread] Current Thread [Next in Thread]