Re: Can't compile Lilypond files

2024-03-25 Thread Valentin Petzel
Hello David,

great that things worked out. Instead of putting a script at /usr/bin/lilypond 
which calls ~/bin/lilypond you could also create a symlink. Also modern Linux 
setups should have ~/.local/bin in PATH by default, so if the reason is only 
to be able to call `lilypond` without path adding a symlink or script there 
should be enough.

Cheers,
Valentin

signature.asc
Description: This is a digitally signed message part.


Re: Can't compile Lilypond files

2024-03-25 Thread Raphael Mankin




On 24/03/2024 21:26, David Sumbler wrote:

On Sun, 2024-03-24 at 21:55 +0100, Lukas-Fabian Moser wrote:

[snip]


What I don't understand is why or how it always used to work, but I 
suppose there's no point in worrying about that.


I have lost count of the number of projects over the past several 
decades in which I have asked that same question.



Anyway, thanks for finding the solution!

David


--
https://saturday-october-seven.com/



Re: Can't compile Lilypond files

2024-03-24 Thread David Sumbler
On Sun, 2024-03-24 at 21:55 +0100, Lukas-Fabian Moser wrote:
> Hi David,
> 
> David Sumbler  schrieb am So., 24. März 2024,
> 21:29:
> > I am running xubuntu  22.04.  When I last used Lilypond (November
> > 2023) I was probably running a recent version of Ubuntu Unity.  But
> > my /home folder has not changed significantly, and Lilypond 2.24.1,
> > downloaded from lilypond.org, is installed there.
> > 
> > I don't quite understand the question about PATH.  The command
> > lilypond is set up to invoke bin/lilypond in my home folder; this
> > is a short script to call my latest version of lilypond in its
> > folder which is a subfolder of my home folder.  And clearly it is
> > doing this.
> > 
> > What do I get as an error message?  I as sorry if I was not clear,
> > but I do not get any error message at all.  No error reported, no
> > warnings, no compilation; merely the same output I would get if I
> > simply typed the command 'lilypond'.
> 
> But this sounds as if your script in bin does not pass command line
> arguments to lilypond, doesn't it?
> 
> So, is this script self-written? And what does its source code look
> like?
> 
> Lukas

You've found the answer!  No, my script wasn't passing command line
arguments, and Ctrl-C Ctrl_L in Emacs lilypond-mode was naturally also
using my one-line script.  Having corrected the script, it now works as
expected.

What I don't understand is why or how it always used to work, but I
suppose there's no point in worrying about that.

Anyway, thanks for finding the solution!

David


Re: Can't compile Lilypond files

2024-03-24 Thread Lukas-Fabian Moser
Hi David,

David Sumbler  schrieb am So., 24. März 2024, 21:29:

> I am running xubuntu  22.04.  When I last used Lilypond (November 2023) I
> was probably running a recent version of Ubuntu Unity.  But my /home folder
> has not changed significantly, and Lilypond 2.24.1, downloaded from
> lilypond.org, is installed there.
>
> I don't quite understand the question about PATH.  The command lilypond is
> set up to invoke bin/lilypond in my home folder; this is a short script to
> call my latest version of lilypond in its folder which is a subfolder of my
> home folder.  And clearly it is doing this.
>
> What do I get as an error message?  I as sorry if I was not clear, but I
> do not get any error message at all.  No error reported, no warnings, no
> compilation; merely the same output I would get if I simply typed the
> command 'lilypond'.
>

But this sounds as if your script in bin does not pass command line
arguments to lilypond, doesn't it?

So, is this script self-written? And what does its source code look like?

Lukas


Re: Can't compile Lilypond files

2024-03-24 Thread David Sumbler
I am running xubuntu  22.04.  When I last used Lilypond (November 2023)
I was probably running a recent version of Ubuntu Unity.  But my /home
folder has not changed significantly, and Lilypond 2.24.1, downloaded
from lilypond.org, is installed there.

I don't quite understand the question about PATH.  The command lilypond
is set up to invoke bin/lilypond in my home folder; this is a short
script to call my latest version of lilypond in its folder which is a
subfolder of my home folder.  And clearly it is doing this.

What do I get as an error message?  I as sorry if I was not clear, but
I do not get any error message at all.  No error reported, no warnings,
no compilation; merely the same output I would get if I simply typed
the command 'lilypond'.

David

On Sun, 2024-03-24 at 20:39 +0100, Valentin Petzel wrote:
> Hello David,
> 
> it apears your Lilypond installation has some issue. What OS are you
> currently 
> on? How did you install Lilypond? If you are using some Linux
> distribution 
> there might be a version mismatch between the libraries the binaries
> have been 
> compiled against and the ones installed on your system. If so this
> should be a 
> dependency / packaging issue of your distribution. Have you tried
> using the 
> statically linked binaries from lilypond.org?
> 
> Cheers,
> Valentin

On Sun, 2024-03-24 at 20:42 +0100, Xavier Scheuer wrote:
> Hello,
> 
> How have you installed LilyPond? From the official binaries or from a
> package from your Linux distribution (I guess, since you mention
> Emacs, that you are under Linux)?
> Do you know that the last versions of LilyPond do not update your
> PATH? So are you invoking lilypond with the path where you extracted
> the binaries?
> And when you say you can't compile, what do you get as error message?
> It is not clear at all.
> 
> Kind regards,
> Xavier

> Am Sonntag, 24. März 2024, 17:13:03 CET schrieb David Sumbler:
> > I haven't used Lilypond for a while, but I have currently got
> > v.2.24.1
> > 
> > I started a new, very small, project today, but I can't compile
> > anything.  Thinking I must have forgotten even the basics of
> > writing
> > Lilypond files, I tried a few of my previous project files which I
> > have
> > successfully compiled in the past.  But nothing will compile.
> > 
> > If I use the bash command line, with, for example,  'lilypond -V
> > file.ly' I get no compilation, and the output is identical to what
> > I
> > get if I just enter 'lilypond' with no option and no file.
> > 
> > If I try to compile from Emacs, using Ctrl-C Ctrl-L, I get exactly
> > the
> > same output as above, with "Compilation exited abnormally with code
> > 2
> > at Sun Mar 24 15:54:38" or similar suffixed.
> > 
> > What can possibly be wrong?  Lilypond isn't giving me any clues.
> > 
> > David
> 



Re: Can't compile Lilypond files

2024-03-24 Thread Xavier Scheuer
On Sun, 24 Mar 2024 at 17:14, David Sumbler  wrote:
>
> I haven't used Lilypond for a while, but I have currently got v.2.24.1
>
> I started a new, very small, project today, but I can't compile
anything.  Thinking I must have forgotten even the basics of writing
Lilypond files, I tried a few of my previous project files which I have
successfully compiled in the past.  But nothing will compile.
>
> If I use the bash command line, with, for example,  'lilypond -V file.ly'
I get no compilation, and the output is identical to what I get if I just
enter 'lilypond' with no option and no file.
>
> If I try to compile from Emacs, using Ctrl-C Ctrl-L, I get exactly the
same output as above, with "Compilation exited abnormally with code 2 at
Sun Mar 24 15:54:38" or similar suffixed.
>
> What can possibly be wrong?  Lilypond isn't giving me any clues.

Hello,

How have you installed LilyPond? From the official binaries or from a
package from your Linux distribution (I guess, since you mention Emacs,
that you are under Linux)?
Do you know that the last versions of LilyPond do not update your PATH? So
are you invoking lilypond with the path where you extracted the binaries?
And when you say you can't compile, what do you get as error message? It is
not clear at all.

Kind regards,
Xavier


Re: Can't compile Lilypond files

2024-03-24 Thread Valentin Petzel
Hello David,

it apears your Lilypond installation has some issue. What OS are you currently 
on? How did you install Lilypond? If you are using some Linux distribution 
there might be a version mismatch between the libraries the binaries have been 
compiled against and the ones installed on your system. If so this should be a 
dependency / packaging issue of your distribution. Have you tried using the 
statically linked binaries from lilypond.org?

Cheers,
Valentin

Am Sonntag, 24. März 2024, 17:13:03 CET schrieb David Sumbler:
> I haven't used Lilypond for a while, but I have currently got v.2.24.1
> 
> I started a new, very small, project today, but I can't compile
> anything.  Thinking I must have forgotten even the basics of writing
> Lilypond files, I tried a few of my previous project files which I have
> successfully compiled in the past.  But nothing will compile.
> 
> If I use the bash command line, with, for example,  'lilypond -V
> file.ly' I get no compilation, and the output is identical to what I
> get if I just enter 'lilypond' with no option and no file.
> 
> If I try to compile from Emacs, using Ctrl-C Ctrl-L, I get exactly the
> same output as above, with "Compilation exited abnormally with code 2
> at Sun Mar 24 15:54:38" or similar suffixed.
> 
> What can possibly be wrong?  Lilypond isn't giving me any clues.
> 
> David



signature.asc
Description: This is a digitally signed message part.


Re: Can't compile Lilypond files

2024-03-24 Thread David Sumbler
I include my code below - this is as far as I got before discovering
the problem.  Jakob, I don't seeing the code will help: if there were a
significant problem with it, then normally Lilypond would report
warnings and errors upon compilation.  But as I said, it reports
nothing!

And yes, Hans, I was definitely using a capital 'V', and I also tried
other versions such as 'lilypond -l DEBUG Cloud/LilyPond/file.ly', with
the same result every time: nothing gets compiled, and no anomalies are
reported.

Here is the file so far:

\version "2.24.1"
\language "english"

\score {
 \relative {
 \time 4/4
 \key d \major
 \partial 8
 d'''8 |
 cs d cs d c d c d |
 b d b d bf d bf d |
 a d a d as d b d |
 c d cs a d2 "|."
 }
}

On Sun, 2024-03-24 at 17:54 +0100, Jakob Pedersen wrote:
> Hi David,
> 
> It might be beneficial if you would share your lilypond file, or
> shortened version of it, so that the smart folks here can look at it
> and point you in the right direction.
> 
> Best wishes,
> Jakob

On Sun, 2024-03-24 at 19:21 +0100, Hans Aikema wrote:
> 
> David, are you sure you’re using a capital V? Because if you use a
> lower-case V you end up in the —version mode of Lilypond, which will
> indeed output similar output as the usage info printed when you
> invoke lilypond without any argument (though the latter will include
> usage instructions, where lilypond -v will only print the version
> header)
> 
> Extract from lilypond —help:
> 
> -v, --version                    show version number and exit
> -V, --verbose                    be verbose (equivalent to --
> loglevel=DEBUG)



Re: Can't compile Lilypond files

2024-03-24 Thread Hans Aikema


> On 24 Mar 2024, at 17:13, David Sumbler  wrote:
> 
> I haven't used Lilypond for a while, but I have currently got v.2.24.1
> 
> I started a new, very small, project today, but I can't compile anything.  
> Thinking I must have forgotten even the basics of writing Lilypond files, I 
> tried a few of my previous project files which I have successfully compiled 
> in the past.  But nothing will compile.
> 
> If I use the bash command line, with, for example,  'lilypond -V file.ly' I 
> get no compilation, and the output is identical to what I get if I just enter 
> 'lilypond' with no option and no file.
> 
> If I try to compile from Emacs, using Ctrl-C Ctrl-L, I get exactly the same 
> output as above, with "Compilation exited abnormally with code 2 at Sun Mar 
> 24 15:54:38" or similar suffixed.
> 
> What can possibly be wrong?  Lilypond isn't giving me any clues.
> 
> David

David, are you sure you’re using a capital V? Because if you use a lower-case V 
you end up in the —version mode of Lilypond, which will indeed output similar 
output as the usage info printed when you invoke lilypond without any argument 
(though the latter will include usage instructions, where lilypond -v will only 
print the version header)

Extract from lilypond —help:

-v, --versionshow version number and exit
-V, --verbosebe verbose (equivalent to --loglevel=DEBUG)




Re: Can't compile Lilypond files

2024-03-24 Thread Jakob Pedersen

Hi David,

It might be beneficial if you would share your lilypond file, or 
shortened version of it, so that the smart folks here can look at it and 
point you in the right direction.


Best wishes,
Jakob

On 24.03.2024 17.13, David Sumbler wrote:

I haven't used Lilypond for a while, but I have currently got v.2.24.1

I started a new, very small, project today, but I can't compile 
anything.  Thinking I must have forgotten even the basics of writing 
Lilypond files, I tried a few of my previous project files which I 
have successfully compiled in the past.  But nothing will compile.


If I use the bash command line, with, for example,  'lilypond -V 
file.ly' I get no compilation, and the output is identical to what I 
get if I just enter 'lilypond' with no option and no file.


If I try to compile from Emacs, using Ctrl-C Ctrl-L, I get exactly the 
same output as above, with "Compilation exited abnormally with code 2 
at Sun Mar 24 15:54:38" or similar suffixed.


What can possibly be wrong?  Lilypond isn't giving me any clues.

David




Can't compile Lilypond files

2024-03-24 Thread David Sumbler
I haven't used Lilypond for a while, but I have currently got v.2.24.1

I started a new, very small, project today, but I can't compile
anything.  Thinking I must have forgotten even the basics of writing
Lilypond files, I tried a few of my previous project files which I have
successfully compiled in the past.  But nothing will compile.

If I use the bash command line, with, for example,  'lilypond -V
file.ly' I get no compilation, and the output is identical to what I
get if I just enter 'lilypond' with no option and no file.

If I try to compile from Emacs, using Ctrl-C Ctrl-L, I get exactly the
same output as above, with "Compilation exited abnormally with code 2
at Sun Mar 24 15:54:38" or similar suffixed.

What can possibly be wrong?  Lilypond isn't giving me any clues.

David