Re: my favorite bug :-)

2015-05-01 Thread Urs Liska
Am 01.05.2015 um 13:53 schrieb Masamichi HOSODA: The bug would be fixed if lilypond would make ghostscript use a complete path to the intermediate lines.ps file for the ps to pdf conversion. Does anyone know how to convert from any path (relative and absolute path) to absolute path in scheme

Incorrect interaction of stemLeft/RightBeamCount and Score.skipTypesetting

2015-05-01 Thread Rob Tuley
I'm not top posting. Wrong output: the \set stemRightBeamCount and \set stemLeftBeamCount are incorrectly applied to the first note AFTER \set Score.skipTypesetting = ##f. \version 2.18.2 { $\set Score.skipTypesetting = ##t c'16 \set stemRightBeamCount = #1 c' \set stemLeftBeamCount = #1 c'

Re: my favorite bug :-)

2015-05-01 Thread Masamichi HOSODA
The bug would be fixed if lilypond would make ghostscript use a complete path to the intermediate lines.ps file for the ps to pdf conversion. Does anyone know how to convert from any path (relative and absolute path) to absolute path in scheme (guile) ? Maybe the functions in this file

Re: my favorite bug :-)

2015-05-01 Thread Masamichi HOSODA
The bug would be fixed if lilypond would make ghostscript use a complete path to the intermediate lines.ps file for the ps to pdf conversion. Does anyone know how to convert from any path (relative and absolute path) to absolute path in scheme (guile) ? When the following command is used,

Re: my favorite bug :-)

2015-05-01 Thread Werner LEMBERG
There is a big difference: If you compile a .c file, the .o files stays by default; the compiler doesn't remove it. Uh, wrong? cd /tmp;echo main(){return 0;} gega.c;gcc -o gega gega.c;ls gega* gega gega.c I've meant using option `-c' of the compiler. BTW, if you specify option `-o',

Re: my favorite bug :-)

2015-05-01 Thread D'Arcy J.M. Cain
On Fri, 1 May 2015 12:48:52 +0200 (CEST) Martin Tarenskeen m.tarensk...@zonnet.nl wrote: In this case, as an intermediate file example.ps is used. This is a problem if a file named example.ps already exists in my working directory. This file is brutally overwritten and deleted when I run

Re: my favorite bug :-)

2015-05-01 Thread David Kastrup
Werner LEMBERG w...@gnu.org writes: There is a big difference: If you compile a .c file, the .o files stays by default; the compiler doesn't remove it. Uh, wrong? cd /tmp;echo main(){return 0;} gega.c;gcc -o gega gega.c;ls gega* gega gega.c I've meant using option `-c' of the

Re: my favorite bug :-)

2015-05-01 Thread Werner LEMBERG
However, I think that the intermediate file should be temporary by mkstemp etc. If lilypond uses mkstemp generated temporary file, this ghostscript problem will not occur. +1 Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: my favorite bug :-)

2015-05-01 Thread Werner LEMBERG
Hello David and Masamichi! I've meant using option `-c' of the compiler. Uh, removing the actual end product of a command would be sort of strange, wouldn't it? Yes. But sometimes there are Makefile rules that remove intermediate files. BTW, if you specify option `-o', does gcc create

Re: my favorite bug :-)

2015-05-01 Thread David Kastrup
Werner LEMBERG w...@gnu.org writes: In this case, as an intermediate file example.ps is used. This is a problem if a file named example.ps already exists in my working directory. This file is brutally overwritten and deleted when I run lilypond without any warning or option to cancel, nor is

Re: my favorite bug :-)

2015-05-01 Thread Masamichi HOSODA
There is a big difference: If you compile a .c file, the .o files stays by default; the compiler doesn't remove it. Uh, wrong? cd /tmp;echo main(){return 0;} gega.c;gcc -o gega gega.c;ls gega* gega gega.c I've meant using option `-c' of the compiler. BTW, if you specify option `-o',

Re: my favorite bug :-)

2015-05-01 Thread David Kastrup
Werner LEMBERG w...@gnu.org writes: Hello David and Masamichi! I've meant using option `-c' of the compiler. Uh, removing the actual end product of a command would be sort of strange, wouldn't it? Yes. But sometimes there are Makefile rules that remove intermediate files. Why bring

Re: my favorite bug :-) (fwd)

2015-05-01 Thread Masamichi HOSODA
Did you know it is not possible/allowed to name a lilypond file align.ly or lines.ly? On my Fedora system I can find all the names that suffer from this bug by typing #ls /usr/share/ghostscript/9.15/lib/*.ps all these filenames (minus .ps) can not be used as lilypond inputfiles (plus

Re: my favorite bug :-)

2015-05-01 Thread Martin Tarenskeen
for example create a file lines.ly with a minimal content \version 2.19.19 {c' d' e' f'} and compile ... I'm trying to narrow down the issue It seems that on some systems (like mine). # gs lines.ps is expanded to something like # gs /usr/share/ghostscript/9.15/lines.ps but # gs

my favorite bug :-) (fwd)

2015-05-01 Thread Martin Tarenskeen
-- Forwarded message -- Date: Fri, 1 May 2015 09:47:25 +0200 (CEST) From: Martin Tarenskeen m.tarensk...@zonnet.nl To: lilypond-user mailinglist lilypond-u...@gnu.org Subject: my favorite bug :-) This issue has been reported in the mailing list some time ago - I think it was

Re: compile failure - parsed object should be dead in 2.19.20

2015-05-01 Thread N. Andrew Walsh
Addendum: this is not a bug with ghostscript, at least for me, but rather with a part of ghostscript failing against recent versions of fontconfig (on my gentoo system, fontconfig-2.11.93 fails to compile .ly files with the errors above, but downgrading to 2.11.1 allows files to compile). Can

Re: my favorite bug :-)

2015-05-01 Thread Martin Tarenskeen
On Fri, 1 May 2015, Martin Tarenskeen wrote: The bug would be fixed if lilypond would make ghostscript use a complete path to the intermediate lines.ps file for the ps to pdf conversion. The issue has brought me to another problem: LilyPond by default takes *.ly file as input and produces

Re: my favorite bug :-)

2015-05-01 Thread Werner LEMBERG
In this case, as an intermediate file example.ps is used. This is a problem if a file named example.ps already exists in my working directory. This file is brutally overwritten and deleted when I run lilypond without any warning or option to cancel, nor is a backup copy of the old file

Re: Completion_heads_engraver and dotted breve

2015-05-01 Thread Ralph Palmer
On Mon, Apr 27, 2015 at 4:05 AM, Simon Albrecht simon.albre...@mail.de wrote: Hello, Completion_heads_engraver doesn’t use dotted breve notes for its output, where smaller note values work as expected. Thanks, Simon Thanks, Simon. Submitted as Issue 4362 :

Re: my favorite bug :-)

2015-05-01 Thread Werner LEMBERG
If the intermediate file would be given a unique, not already existing, temporary filename, not only this issue would be solved but also the original lines.ly - lines.ps - lines.pdf issue that started this thread would not be a problem anymore. I'm not a (LilyPond) developer but does it

Re: my favorite bug :-)

2015-05-01 Thread Masamichi HOSODA
The bug would be fixed if lilypond would make ghostscript use a complete path to the intermediate lines.ps file for the ps to pdf conversion. Does anyone know how to convert from any path (relative and absolute path) to absolute path in scheme (guile) ?

Re: figured bass on grace note

2015-05-01 Thread Ralph Palmer
On Tue, Apr 28, 2015 at 10:58 PM, Yuan Ye yuanyel...@openmailbox.org wrote: I believe there is a bug when writing figured bass on grace note. The figure before the grace note is repeated on the grace note. Here is a tiny example: The second figure should be 5 but turns out 6 5. Thanks,