Re: wait_for_file ?? [print via pipes - help testing on Windows?]

[bpabbott]

On Sep 17, 2010, at 02:02 PM, Marco Atzeri <address@hidden> wrote:

--- Ven 17/9/10,  ha scritto:

> Data: Venerdì 17 settembre 2010, 18:06
> --- Ven 17/9/10, Michael D
> Godfrey  ha scritto:
>
> 
>   On 09/17/2010 05:58 AM, bpabbott wrote:
>     Unfortunately, I should
>         have been more clear. The
> changeset attached to the prior email
>         has not been pushed. You'll
> need to patch your sources with that
>         changeset.
>     I did that.
>
>       Michael
>
>      
> I did not. After applying it I have some strange effects.
>
> It partially worked but after a "make" it stopped to work
> with a "feval: function `__init_ftlk__' not found"
>
> I am rebuilding as eventually some configures went wrong.
>
>
> Marco   
>  
>

Ok, configured, built and istalled again.

octave:2> source "test_printing.m"
octave:3> test_printing("fltk")
backend is fltk
print fltk-aifm  -daifm

the file is built but octave hangs and I need to kill it.

 

I have encountered hangs as well. In my case, Octave would hang when a function was called that both existed locally and in the private directory of the calling function. If there were no local m-files, except test_printing.m, then I haven't seen a hang.

In each case I've examined, the problem appears to be with Octave's internals (i.e. not a problem with the m-files). Unfortunately, I've not been successful creating an example that reliably demonstrates the problem.

In any event, what m-files do you have locally?

You can test specific devices for specific backends. For example the test eps only ...

test_printing fltk -depsc -debug

Adding "-debug" will also provide more info. For the command above, I get ...

octave:1> test_printing fltk -depsc -debug

backend is fltk

print fltk-epsc  -depsc -debug

epstool command: ' cat > 'fltk-epsc.eps' '

fltk-pipeline: ' cat > 'fltk-epsc.eps' '

epstool command: 'cat > /var/tmp/oct-RkjJfC.eps ; /sw/bin/epstool --quiet --copy --bbox /var/tmp/oct-RkjJfC.eps 'fltk-epsc-tight.eps'  ; rm /var/tmp/oct-RkjJfCeps '

fltk-pipeline: 'cat > /var/tmp/oct-RkjJfC.eps ; /sw/bin/epstool --quiet --copy --bbox /var/tmp/oct-RkjJfC.eps 'fltk-epsc-tight.eps'  ; rm /var/tmp/oct-RkjJfC.eps '

epstool command: 'cat > /var/tmp/oct-lOmHox.eps ; /sw/bin/epstool --quiet --add-tiff-preview --device tiffg3 --dpi 150 /var/tmp/oct-lOmHox.eps 'fltk-epsc-tiff.eps'  ; rm /var/tmp/oct-lOmHox.eps '

fltk-pipeline: 'cat > /var/tmp/oct-lOmHox.eps ; /sw/bin/epstool --quiet --add-tiff-preview --device tiffg3 --dpi 150 /var/tmp/oct-lOmHox.eps 'fltk-epsc-tiff.eps'  ; rm /var/tmp/oct-lOmHox.eps '

The epsc output will produce three files. The normal one, one with a tight bbox and a 3rd with a tiff preview.

If you can't produce eps output, what does the following give you?

__parse_print_opts__ ("test.eps", "-depsc")

Ben