[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

RE: st: Parsing issue?

From   "Nick Cox" <>
To   <>
Subject   RE: st: Parsing issue?
Date   Fri, 25 Apr 2008 18:32:17 +0100

Eva is correct. 

The way you can be backstabbed by backslashes is explained in a handy
paperback, the 
User's Guide. See [U] 18.3.11. 

In all operating systems it supports, Stata is happy to accept / as a
separator within 
filenames. Under various flavours of Unix, including modern Mac OSs,
that is standard any way. Under Windows, Stata translates when


Eva Poen

a backslash is an escape character in Stata. In front of a local
macro, a backslash prevents execution. I.e., - \`x'- becomes `x' after
Stata executed the line. This can be useful in programming.

For your problem, try replacing the backslash with a forward slash. At
least in Windows this works fine. I don't know about other operating

2008/4/25 E. Paul Wileyto <>:

> I cannot fathom what is going on here, and I'm hoping someone out
> might have a clue.  The twoway command correctly interprets the local
> `x' and puts up the graph.  The graph save command does not seem to
know the
> meaning of `x', and lops off the backslash in front of it.  Any
> I'm appending the main output, and then a trace...  I'm not seeing
> useful in the trace.

*   For searches and help try:

© Copyright 1996–2017 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index