octave-maintainers
[Top][All Lists]
Advanced

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

Re: Print to PDF under Windows [changeset-2]


From: Ben Abbott
Subject: Re: Print to PDF under Windows [changeset-2]
Date: Sat, 21 Nov 2009 11:17:30 -0500

On Nov 21, 2009, at 11:05 AM, Benjamin Lindner wrote:

> Ben Abbott wrote:
> 
>> Ok, my understanding is that EXEC_PATH is equivalent to the PATH environment 
>> variable that was in place when Octave was run. Which is likely to include 
>> the default shell's PATH as well as additions needed to run Octave. In the 
>> event  ghostscript is bundled with Octave, then EXEC_PATH is preferred over 
>> PATH.
> 
> I see your point.
> It's currently not bundled, but maybe will be
> 
>> The attached changeset looks for the console version of ghostscript, 
>> "gswin32c.exe", and still searches EXEC_PATH for gswin32c.exe.
> 
> looks fine to me.
> Although I haven't checked in action yet, as I'm working on getting
> the build process to run again.
> 
> benjamin

I'm also not able to build the developers sources at the moment. So I'm testing 
m-files under 3.2.3.

Can you/somone-else test this changeset under 3.2.3?

TiA
Ben


reply via email to

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