Unfortunately that didn't work, it still leaves a .ps file behind.
> Am 15.09.2015 um 20:25 schrieb Simon Albrecht <simon.albre...@mail.de>:
>
> Am 15.09.2015 um 20:22 schrieb poto...@posteo.de:
>> Thanks, that works. I set up a build system for Sublime (which has Lilypond
>> syntax highlighting with the SubLilyPond package).
>>
>> {
>> "shell_cmd": "lilypond -dno-point-and-click '$file_base_name.ly';
>> pdfcrop --margins 1 '$file_base_name.pdf' '$file_base_name.pdf'; pdf2svg
>> '$file_base_name.pdf' '$file_base_name.svg'; rm -f '$file_base_name.pdf'; rm
>> -f '$file_base_name.ps'",
>> "selector": "source.lilypond",
>> }
>>
>> This will render and crop a pdf, convert it to svg and delete the pdf.
>> However, I don't know why it won't remove the .ps file, or why it is created
>> in the first place. Is there a way to prevent Lilypond from creating the .ps
>> file?
>>
>>
> Since LilyPond doesn’t have a proper PDF backend, first a .ps file is
> created, which is converted to .pdf afterwards. There is a program option to
> have the intermediate files deleted automatically:
> -ddelete-intermediate-files.
>
> HTH, Simon
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
