Date: Wed, 23 Oct 2002 09:12:25 +0200
Sender: "SPSSX(r) Discussion" <SPSSX-L@LISTSERV.UGA.EDU>
From: Frederic Villamayor <firstname.lastname@example.org>
Subject: Re: End-of-line: A tale of two modes: Interactive vs batch (aka
Content-Type: text/plain; charset="iso-8859-1"
I've faced with this problem and , yes, the solution was to truncate
command lines. As a rule, I split command lines at convenience (but not in
the middle of a subcommand!) indenting 1 space all tn lines after the
first. As for long strings, you can split them where you want, but you
must end each line with a quote and a plus '+' symbol, and start next line
wit a quote. You can split by this methos a long string into as many lines
as you want.
For example, it a file names is:
"C:\My documents\Projects\XXXX\Data\Original\These are my data and the
file name is very long.sav"
you can split it as follows:
"These are my data "+
"and the file name is very long.sav"
Departamento de Toxicología
C.I.D.F. GRUPO FERRER
"McGee, Magnus" <email@example.com>
Enviado por: "SPSSX(r) Discussion" <SPSSX-L@LISTSERV.UGA.EDU>
Por favor, responda a "McGee, Magnus"
Asunto": End-of-line: A tale of two modes: Interactive vs batch (aka produ ction)
I'm having difficulty in finding a clear answer to the following
- I have some syntax that works in interactive mode.
- The same syntax fails in batch.
I think the reason is that some lines are too long.
- The lines contain filenames enclosed in quotes.
- One solution is to use file references however I still
need to know the answer to the original problem. )
1) How do you delimit a long line of syntax?
2) Will it still work in interactive mode?
Health Services Research Unit
University of Aberdeen
Tel: 01224 559219
Fax: 01224 663087