Hi Joe If you have the syntax edit screen opened there is a file button and when opened you find a "save as". The file you saved can be used in the terminal mode and with PSPP.
Furthermore you will find a pspp.jnl journal file which also includes all your commands. This can be very helpfull for building your syntax with the gui. Copying pspp.jnl to my-syntax.sps, or what ever, and remove the output and unnecessary parts can be a quick way to reach your goal. Have fun 2015-08-04 17:51 GMT+02:00 Joe Genshlea <j...@revolution-wines.com>: > I'll try both those suggestions. The main reason I want to script my > processes is that I need to apply the same meta data (Variable and value > labels) to different files. If there is a way to save the file layout > then I can do everything in PSPPIRE. > > > > On Tue, Aug 4, 2015 at 1:11 AM, Harry Thijssen <pspp4wind...@gmail.com> > wrote: > >> >> >>> Hello- >>> >>> I'm a big time NB, so please bear with me. >>> >>> When running PSPP in terminal mode on windows the first character of the >>> executed line carries forward to the following line. I can't seem to get >>> around this >>> >>> Examples: >>> >>> PSPP> GET DATA >>> G >>> >>> PSPP> DATA LIST LIST >>> D >>> >>> if I type "/" sometimes the cursor will tab forward and allow me to >>> enter a >>> subcommand, but then the following line will render with a "p" >>> >>> PSPP> GET DATA >>> GET DATA >>> > /TYPE=TXT >>> pTYPE=TXT >>> >>> .1-5: error: GET DATA: Syntax error at `pTYPE': expecting `/'. >>> >>> .1-5: error: GET DATA: Syntax error at `pTYPE': expecting TYPE. >>> >>> >>> I've installed two different versions on my Windows 7 computer and >>> observe >>> the same behavior. The version I'm currently running is PSPP-084-20150224 >>> >>> >>> I know this must be really obvious. Thanks for your patience. >>> >>> Joe >>> >>> >> Hi Joe >> >> I can confirm this behavior. But I don have an idea how to solve it. >> Software build from the current sources has the same problem. >> If PSPP is started from the commandline with a .sps file as parameter it >> works fine. >> >> A work around is using PSPPIRE and work from the syntax window. >> >> Have fun >> >> >> > > > -- > Joe Genshlea > Revolution Wines <http://www.revolution-wines.com> > 2831 S Street > Sacramento, CA 95816 > p: 916-444-7711 > m:916-201-3941 > f:916-290-0503 > > In theory there is no difference between theory and practice. In practice > there is. > > > - *Yogi Berra* >
_______________________________________________ Pspp-users mailing list Pspp-users@gnu.org https://lists.gnu.org/mailman/listinfo/pspp-users
