).
ArnoldTheresius
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/my-favorite-bug-tp175778p176106.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman
.
ArnoldTheresius
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/my-favorite-bug-tp175778p176024.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org
On 5/4/15 1:35 AM, ArnoldTheresius arnold.we...@siemens.com wrote:
2. the PS file, because it's used for another postprocessing: I generate a
booklet layout PDF from it (this PDF uses the double sheet size, e.g. A3)
How do you do this? This is something I'm very interested in, but I've
been
On 2015-05-04 15:40, Carl Sorensen wrote:
On 5/4/15 1:35 AM, ArnoldTheresius arnold.we...@siemens.com wrote:
2. the PS file, because it's used for another postprocessing: I generate a
booklet layout PDF from it (this PDF uses the double sheet size, e.g. A3)
How do you do this? This is
On Mon, 4 May 2015 01:35:13 -0700 (MST)
ArnoldTheresius arnold.we...@siemens.com wrote:
2. the PS file, because it's used for another postprocessing: I generate a
booklet layout PDF from it (this PDF uses the double sheet size, e.g. A3)
You can do this from the PDF as well.
-- Johan
Hi,
this little (simplified) shell script (I have called it ly2pdf)
#!/bin/sh
INFILE=$1
OUTFILE=${INFILE%.ly}.pdf
lilypond --ps -o $$ $INFILE
ps2pdf $$.ps $OUTFILE
rm -f $$.ps
demonstrates the kind of mechanism that LilyPond needs. (But without
needing such a script). It fixes the lines.ly
Observing all the energy devoted to this critical issue, I have to wonder
how many extraordinary symphonies, operas, and cantatas will NOT be written
because some folks are too easily distracted by minutia
I could live 5 lifetimes, and this issue would never get more than 5
seconds of my
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,
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
___
lilypond-user mailing list
lilypond-user@gnu.org
On Fri, 1 May 2015, N. Andrew Walsh wrote:
Is this a similar bug to that I posted to the bug-list already? Namely, that
ghostscript fails entirely (and thus lilypond
fails to compile entirely) on recent versions of lilypond? As I said there, I'm
using gs 3.19, on a self-compiled version
of
see my other post in the thread about Fedora: that bug is apparently
related to a problem with recent fontconfig (which had wide-ranging
consequences and breakages on my gentoo system).
Cheers,
A
On Fri, May 1, 2015 at 7:08 PM, Martin Tarenskeen m.tarensk...@gmail.com
wrote:
On Fri, 1 May
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) ?
This issue has been reported in the mailing list some time ago - I think
it was David Kastrup who discovered it - but I can't find it anywhere in
the buglist or in the docs.
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
On Fri, 1 May 2015, Michael Hendry wrote:
On 1 May 2015, at 08:54, Werner LEMBERG w...@gnu.org wrote:
for example create a file lines.ly with a minimal content
\version 2.19.19
{c' d' e' f'}
and compile ...
Nice! I wasn't aware that lilypond can put *that* much information
into four
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
for example create a file lines.ly with a minimal content
\version 2.19.19
{c' d' e' f'}
and compile ...
Nice! I wasn't aware that lilypond can put *that* much information
into four note symbols :-)
Please submit a bug report.
Werner
On 1 May 2015, at 09:41, Martin Tarenskeen m.tarensk...@zonnet.nl wrote:
On Fri, 1 May 2015, Michael Hendry wrote:
On 1 May 2015, at 08:54, Werner LEMBERG w...@gnu.org wrote:
for example create a file lines.ly with a minimal content
\version 2.19.19
{c' d' e' f'}
and
On 1 May 2015, at 08:54, Werner LEMBERG w...@gnu.org wrote:
for example create a file lines.ly with a minimal content
\version 2.19.19
{c' d' e' f'}
and compile ...
Nice! I wasn't aware that lilypond can put *that* much information
into four note symbols :-)
Please submit a bug
Hi All,
2015-05-01 10:41 GMT+02:00 Martin Tarenskeen m.tarensk...@zonnet.nl:
On Fri, 1 May 2015, Michael Hendry wrote:
On 1 May 2015, at 08:54, Werner LEMBERG w...@gnu.org wrote:
for example create a file lines.ly with a minimal content
\version 2.19.19
{c' d' e' f'}
and compile
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
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
On 01.05.2015 (14:16), Werner LEMBERG wrote:
For the curious people, here's `lines.pdf' if ghostscript erronously
processes its own `lines.ps' demo file.
Pretty! Have you tried to play it?
e
--
To be a kind of moral Unix, he touched the hem of Nature's shift.
-- Shelley
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
On Fri, 1 May 2015 08:28:17 -0400
D'Arcy J.M. Cain da...@druid.net wrote:
If the intermediate file would be given a unique, not already
existing, temporary filename, not only this issue would be solved but
Solved for some, problem for others. I don't want to have to guess
what my final
On Fri, 1 May 2015 11:36:23 +0200
Pierre Perol-Schneider pierre.schneider.pa...@gmail.com wrote:
So am I : four notes on Ubuntu 14 and W7
It depends on whether your GhostScript looks in the current directory first.
Lily should do PDF. Period.
-- Johan
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
On Fri, 1 May 2015 09:47:25 +0200 (CEST)
Martin Tarenskeen m.tarensk...@zonnet.nl wrote:
Did you know it is not possible/allowed to name a lilypond file
align.ly or lines.ly?
Yes.
It is one of the reasons I keep saying that LilyPond should eliminate
PostScript (and hence GhostScript) and
Lily should do PDF. Period.
Right. However, noone is going to implement this right now, so we
have to follow the second-best route, this is, making the creation of
the intermediate PS file work correctly.
Werner
___
lilypond-user mailing list
Nice! I wasn't aware that lilypond can put *that* much information
into four note symbols :-)
I’m feeling left out here, on my Mac!
All I get is the first four notes of a C major scale!!
For the curious people, here's `lines.pdf' if ghostscript erronously
processes its own `lines.ps' demo
Is this a similar bug to that I posted to the bug-list already? Namely,
that ghostscript fails entirely (and thus lilypond fails to compile
entirely) on recent versions of lilypond? As I said there, I'm using gs
3.19, on a self-compiled version of lilypond-3.19.20. I cannot compile even
a simple
On Fri, 1 May 2015 15:20:19 +0200
N. Andrew Walsh n.andrew.wa...@gmail.com wrote:
Is this a similar bug to that I posted to the bug-list already? Namely,
that ghostscript fails entirely (and thus lilypond fails to compile
entirely) on recent versions of lilypond? As I said there, I'm using gs
31 matches
Mail list logo
