Re: Frescobaldi custom script

[Peter Bjuhr]

On 2014-10-26 13:31, Vaughan McAlley wrote:
> Sorry if I’m wrong, but can’t you type anything you like into
> Frescobaldi’s Engrave (Custom) command line window? Something like:
>
> python ~/scripts/myLilypondScript.py $filename
>
> ...should run the script and pass it the filename, however that works in Python.

The command line window is of course expecting a command to run 
LilyPond. The flexibility of changing the command that is executed is 
thought for custom LilyPond calls. But as I understand it any command 
would be executed. The advantage is that you can make use of the 
shortcut $filename for the current document. Otherwise it's hard to see 
any benefits of that approach, I think.
> There are two issues I have at the moment- one is that it doesn’t seem
> to be possible to direct Lilypond output to stdout (Postscript in my
> case for piping to Ghostscript with lots of special options), and the
> second is that Frescobaldi forgets the custom command every time it
> quits, so you have to store it elsewhere.

The ability to save a custom commands could perhaps be argued. At the 
moment the command is construed by the other settings.

To catch the stdout message I think the best approach is to run the 
python script as a Snippet and to add the functionality to handle this.

Best
Peter