From: Rick M. Cox [mailto:address@hidden
Sent: Thursday, June 13, 2013 8:15 PM
To: 'Ben Abbott'
Cc: 'Nicholas Jankowski'; 'help-octave Octave'
Subject: RE: Help with saveas and fltk From: Ben Abbott [mailto:address@hidden]
Sent: Thursday, June 13, 2013 8:05 PM
To: Rick M. Cox
Cc: 'Nicholas Jankowski'; 'help-octave Octave'
Subject: Re: Help with saveas and fltk From: Ben Abbott [mailto:address@hidden]
Sent: Thursday, June 13, 2013 7:40 PM
To: Rick M. Cox
Cc: 'Nicholas Jankowski'; 'help-octave Octave'
Subject: Re: Help with saveas and fltk From: Ben Abbott [mailto:address@hidden]
Sent: Thursday, June 13, 2013 5:58 PM
To: Rick M. Cox
Cc: 'Nicholas Jankowski'; 'help-octave Octave'
Subject: Re: Help with saveas and fltk Nick and Ben: I hope some of this helps: 1. I haven’t seen the “D:\Program” error in a long time. 2. I installed Octave 3.7.2+ and Ghostscript v9.07 in paths with no white spaces. Even though I don’t use it anymore, I never deleted Octave 3.6.4. It still resides in a path with white spaces. I certainly could delete it if you thought it was a problem. 3. I thought I correctly added Ghostscript to the system path/environment variables per the setup instructions. 4. When I type system (“gswin32c.exe”) I get a Ghostscript 9.07 header. I’m cheered that my routines work on your systems. I’d like it to work on mine. J Thanks again, Rick
I'm not sure it will help resolve the problem, but please type EXEC_PATH at Octave's prompt and copy-n-paste the text it returns into you reply. Also tell us if you've installed more than one version of Ghostscript and where they are. Ben Ben: Using the diary command I captured the following in response to EXEC_PATH: ans = D:\Octave\Octave-3.7.2+\msys\bin;D:\Octave\Octave-3.7.2+\libexec\octave\3.7.2+\site\exec\i686-pc-mingw32;D:\Octave\Octave-3.7.2+\libexec\octave\api-v48+\site\exec\i686-pc-mingw32;D:\Octave\Octave-3.7.2+\libexec\octave\site\exec\i686-pc-mingw32;D:\Octave\Octave-3.7.2+\libexec\octave\3.7.2+\exec\i686-pc-mingw32;D:\Octave\Octave-3.7.2+\bin Rick
Oh! ... I didn't know you were running a mingw version of Octave. Are you using the MSYS shell or a DOS COMMAND shell? If I recall correctly, the MSYS shell allows copy, cut, and paste. Thus, my guess is you are using the DOS COMMAND shell. Please try running Octave from the MSYS shell and let us know if the printing functionality improves. Ben Ben: How do I do this? Rick
From the DOS COMMAND shell you can type "msys.bat". When you run Octave now, do you start it from a DOS COMMAND shell or do you select Octave from the Start menu? If the latter, you are likely already running the msys shell. I don't recall if msys qualifies as a unix shell, but you can try the command "isunix" in Octave to see what is says. Ben Ben: I start Octave 3.7.2+ either from the Start Menu or from a shortcut I set up on my Desktop. I’ve never used a DOS COMMAND shell to start any version of Octave. When I typed “isunix” the result was ans = 0. Rick Ben and Nick: When I start Octave 3.7.2+ the header includes a line: MSYS shell available (D:\Octave\Octave-3.7.2+\msys) That said, I can’t find a msys.bat file anywhere in the Octave-3.7.2+ directories. Is it a problem that I am using Octave 3.7.2+? It loads much faster and I like the GUI but if it is experimental I can return to Octave 3.6.4. Rick |