Re: temporary files won't delete -- and block system
Le dimanche 14 mai 2023 à 21:54 +0200, Sam Carmalt a écrit : > Not sure if this is a LilyPond or Frecobaldi problem, but it is frustrating. > > I can see a change made to a score by Cntl-M. But any subsequent change > cannot be seen. Attempting to delete the .pdf file gives an error "cannot > delete the file because it is open in > Frescobaldi". Only fix seems to be to exit Frescobaldi, delete temporary > files, especially .pdf files, and then re-start. > > This obviously slows down the bug-fix problems. > > Help on how to have Frescobaldi simply overwrite files when Cntl-M or > Cntl-Shift-P is pressed would be greatly appreciated. Your problem is not very clear to me. You obviously have the PDF files open in Frescobaldi, but what is the other application you open them in? If you are reopening them each time in a PDF viewer like Adobe Acrobat or such, then perhaps the problem is that you did not save the LilyPond file in Frescobaldi? If you don't save it, Frescobaldi creates a temporary file in an invisible place, compiles that and displays the result PDF, without affecting the PDF that is next to the (out of date) .ly file. I guess you are working on Windows, since the inability to delete a file while it is open in an application is a limitation of Windows. Nothing we can do about that. signature.asc Description: This is a digitally signed message part
temporary files won't delete -- and block system
Not sure if this is a LilyPond or Frecobaldi problem, but it is frustrating. I can see a change made to a score by Cntl-M. But any subsequent change cannot be seen. Attempting to delete the .pdf file gives an error "cannot delete the file because it is open in Frescobaldi". Only fix seems to be to exit Frescobaldi, delete temporary files, especially .pdf files, and then re-start. This obviously slows down the bug-fix problems. Help on how to have Frescobaldi simply overwrite files when Cntl-M or Cntl-Shift-P is pressed would be greatly appreciated. Regards, S. Carmalt -- Sam Carmalt Tel: +41 79 232 25 53
Re: Simple instructions for installing Lilypond
Le dimanche 14 mai 2023 à 13:17 -0400, Hwaen Ch'uqi a écrit : > Does this then mean that the terminal command is now as straightforward as > "sudo apt install lilypond"? Yes. At least under Ubuntu Lunar (23.04), it will install version 2.24.1. > Will that automatically install the texinfo files as well? Yes. signature.asc Description: This is a digitally signed message part
Re: Simple instructions for installing Lilypond
Greetings, David, First, I thank you for venting, for your vent was/is mine as well and is the reason why I am still using V-22.2. Does this then mean that the terminal command is now as straightforward as "sudo apt install lilypond"? Will that automatically install the texinfo files as well? Hwaen Ch'uqi On 5/14/23, David Sumbler wrote: > On Sun, 2023-05-14 at 13:31 +0200, Jean Abou Samra wrote: >> Le dimanche 14 mai 2023 à 12:15 +0100, David Sumbler a écrit : >> > It's a while since I used Lilypond. I have a bit of tweaking I >> > want to do to some scores, so thought I should download the latest >> > version. In the end, I decided to use v2.24.1, rather than 2.25.4, >> > although I have mostly used the "unstable" versions in the past. >> > >> > Lilypond used to use a global install, and it was the work of a few >> > minutes to download and install this on my Linux machines, >> > including all the documentation too if one added the -d flag. >> > >> > I have managed to install Lilypond, and even the docs, a couple of >> > times since it changed to a sort of flatpack design. Each time it >> > has taken me a long time to get it all working. Today I have spent >> > well over an hour messing about, and I have now managed to get >> > lilypond installed and also the documentation. >> > >> > But convert-ly doesn't work: I get a >> > "/home/david/lilypond/usr/bin/python3: not found" error. This is >> > probably because the convert-ly script I have in my ~/bin/ folder >> > needs amending, but I can see myself having to spend another hour >> > or two trying to sort out what is going wrong and how to change it. >> > >> > What seems to be missing is a simple to find and to follow set of >> > instructions on how to install Lilypond. I was surprised to see >> > that the Learning Manual now encourages users to use a package from >> > their distro. This seems to be a change of policy: previously, the >> > website discouraged users from doing this, because the repositories >> > usually have out of date versions. But perhaps this is the path I >> > should go down, simply to save time. >> > >> > Sorry, this is just a grumble about having to mess about so much to >> > get Lilypond functioning. But surely there ought to be some sort >> > of instructions on the download site about how to get everything >> > installed and working. >> >> >> What does “install” mean to you? >> >> This is a serious question, not hair splitting. Depending on what you >> actually want to do with LilyPond, the way to “install” it can be >> vastly different. >> >> If you just want to run it from the command line, then you don't need >> to install it in any way, you can just run >> "~/where/you/unpacked/the/archive/bin/lilypond". >> >> If you want to use it *regularly* from the terminal, or if you want >> some tool (e.g., Emacs) to find it as just "lilypond", you can just >> prepend the right directory to your PATH by adding this to your shell >> startup file (e.g., ~/.bashrc): >> >> export PATH=/where/you/unpacked/the/archive/bin:$PATH >> >> and this will make it callable as "lilypond". >> >> If you want to use it with Frescobaldi, that's in the learning >> manual, but I suppose you saw that. >> >> For the documentation there is no real "installation" process in any >> case (OK, except maybe if you want the Info documentation). >> >> To me, the problem with “there should be a simple way to install >> LilyPond” is that “install LilyPond” is not something well-defined at >> all. There is also a purely psychological issue that some people >> think it's a must to “install” something in some way before being >> able to use it. >> >> There are good reasons why the script that used to be shipped isn't >> shipped anymore (for example: it would not work well with having >> several versions in parallel). > > OK - point taken! > > After writing my previous moaning message, I decided to see what > version of Lilypond I would get if I installed my Linux distro's > version (I'm using Ubuntu-Unity 23.04). Rather to my surprise I found > that it is v.2.24.1, the latest "stable" version, and the same as I > downloaded earlier from the Lilypond download site. I also downloaded > the docs. > > And magically it all seems to work. convert-ly worked straight away, > and all is well. No doubt this is why new users are now encouraged to > use their distro's version, the opposite advice to what used to be > given. So in future I'll probably stick with this policy. Since I > tend to install new versions of Ubuntu fairly frequently, my Lilypond > versions shouldn't be too out of date. > > David > >
Re: Simple instructions for installing Lilypond
Le dimanche 14 mai 2023 à 17:52 +0100, David Sumbler a écrit : > After writing my previous moaning message, I decided to see what version of > Lilypond I would get if I installed my Linux distro's version (I'm using > Ubuntu-Unity 23.04). Rather to my surprise I > found that it is v.2.24.1, the latest "stable" version, and the same as I > downloaded earlier from the Lilypond download site. I also downloaded the > docs. Yes, these days, most distros have up-to-date LilyPond versions in their repositories, which is why the advice against distro packages was removed. signature.asc Description: This is a digitally signed message part
Re: Simple instructions for installing Lilypond
On Sun, 2023-05-14 at 13:31 +0200, Jean Abou Samra wrote: > Le dimanche 14 mai 2023 à 12:15 +0100, David Sumbler a écrit : > > It's a while since I used Lilypond. I have a bit of tweaking I > > want to do to some scores, so thought I should download the latest > > version. In the end, I decided to use v2.24.1, rather than 2.25.4, > > although I have mostly used the "unstable" versions in the past. > > > > Lilypond used to use a global install, and it was the work of a few > > minutes to download and install this on my Linux machines, > > including all the documentation too if one added the -d flag. > > > > I have managed to install Lilypond, and even the docs, a couple of > > times since it changed to a sort of flatpack design. Each time it > > has taken me a long time to get it all working. Today I have spent > > well over an hour messing about, and I have now managed to get > > lilypond installed and also the documentation. > > > > But convert-ly doesn't work: I get a > > "/home/david/lilypond/usr/bin/python3: not found" error. This is > > probably because the convert-ly script I have in my ~/bin/ folder > > needs amending, but I can see myself having to spend another hour > > or two trying to sort out what is going wrong and how to change it. > > > > What seems to be missing is a simple to find and to follow set of > > instructions on how to install Lilypond. I was surprised to see > > that the Learning Manual now encourages users to use a package from > > their distro. This seems to be a change of policy: previously, the > > website discouraged users from doing this, because the repositories > > usually have out of date versions. But perhaps this is the path I > > should go down, simply to save time. > > > > Sorry, this is just a grumble about having to mess about so much to > > get Lilypond functioning. But surely there ought to be some sort > > of instructions on the download site about how to get everything > > installed and working. > > > What does “install” mean to you? > > This is a serious question, not hair splitting. Depending on what you > actually want to do with LilyPond, the way to “install” it can be > vastly different. > > If you just want to run it from the command line, then you don't need > to install it in any way, you can just run > "~/where/you/unpacked/the/archive/bin/lilypond". > > If you want to use it *regularly* from the terminal, or if you want > some tool (e.g., Emacs) to find it as just "lilypond", you can just > prepend the right directory to your PATH by adding this to your shell > startup file (e.g., ~/.bashrc): > > export PATH=/where/you/unpacked/the/archive/bin:$PATH > > and this will make it callable as "lilypond". > > If you want to use it with Frescobaldi, that's in the learning > manual, but I suppose you saw that. > > For the documentation there is no real "installation" process in any > case (OK, except maybe if you want the Info documentation). > > To me, the problem with “there should be a simple way to install > LilyPond” is that “install LilyPond” is not something well-defined at > all. There is also a purely psychological issue that some people > think it's a must to “install” something in some way before being > able to use it. > > There are good reasons why the script that used to be shipped isn't > shipped anymore (for example: it would not work well with having > several versions in parallel). OK - point taken! After writing my previous moaning message, I decided to see what version of Lilypond I would get if I installed my Linux distro's version (I'm using Ubuntu-Unity 23.04). Rather to my surprise I found that it is v.2.24.1, the latest "stable" version, and the same as I downloaded earlier from the Lilypond download site. I also downloaded the docs. And magically it all seems to work. convert-ly worked straight away, and all is well. No doubt this is why new users are now encouraged to use their distro's version, the opposite advice to what used to be given. So in future I'll probably stick with this policy. Since I tend to install new versions of Ubuntu fairly frequently, my Lilypond versions shouldn't be too out of date. David
Re: Seeking something that looks like a dotted tie...
Le dimanche 14 mai 2023 à 17:24 +0100, Graham King a écrit :
> I'm setting a song with multiple verses, one of which starts with a syllable
> spanning two notes. I'd like a dotted tie in the score, but how best to
> achieve that?
Temporarily unset melismaBusyProperties like:
```
\version "2.25.4"
notes = \repeat volta 2 {
\once \tieDotted
\set melismaBusyProperties = #'()
d'2~ d'2
\unset melismaBusyProperties
e'2. 4
}
words = \lyricmode {
<< { Lo -- rem ip -- sum }
\new Lyrics {
\set associatedVoice = "notes"
do _ -- lo -- rit
}
>>
}
\score { <<
\new Voice="sungNotes" \notes
\new Lyrics \lyricsto sungNotes { \words }
>> }
```
See
https://lilypond.org/doc/v2.25/Documentation/notation/multiple-notes-to-one-syllable
signature.asc
Description: This is a digitally signed message part
Seeking something that looks like a dotted tie...
I'm setting a song with multiple verses, one of which starts with a syllable
spanning two notes. I'd like a dotted tie in the score, but how best to
achieve that?
\version "2.25.0"
notes = \repeat volta 2 { d'2 d'2 e'2. 4 }
words = \lyricmode {
<< { Lo -- rem ip -- sum }
\new Lyrics {
\set associatedVoice = "notes"
do _ -- lo -- rit
}
>>
}
\score { <<
\new Voice="sungNotes" \notes
\new Lyrics \lyricsto sungNotes { \words }
>> }
~~~
1. If I use a tie, the alignment of the words for the other verses gets messed
up:
notes = \repeat volta 2 { \tieDotted d'2 ~ d'2 e'2. 4 }
2. If I use a tie + explicit durations in the lyrics, I have to continue
entering them for the entire piece. I can't just do:
Lo2 -- rem2 ip -- sum
and leave lilypond to work out the rest of the durations for the lyrics.
3. If I try to fake it with a dotted phrasing slur, it works but looks ugly
(and is semantically questionable):
notes = \repeat volta 2 { \phrasingSlurDotted d'2\( d'2\) e'2. 4 }
So, what have I missed? Suggestions gratefully received!
-- Graham
Re: Simple instructions for installing Lilypond
Le dimanche 14 mai 2023 à 14:48 +0200, Jean Abou Samra a écrit : > you did not remove these symlinks. Brain fart: symlinks → wrapper scripts signature.asc Description: This is a digitally signed message part
Re: Simple instructions for installing Lilypond
By the way: this: Le dimanche 14 mai 2023 à 12:15 +0100, David Sumbler a écrit : > > But convert-ly doesn't work: I get a "/home/david/lilypond/usr/bin/python3: > not found" error. This is probably because the convert-ly script I have in > my ~/bin/ folder needs amending, but I can > see myself having to spend another hour or two trying to sort out what is > going wrong and how to change it. sounds like the ~/bin/convert-ly script was created by the older installer script, and you removed the old installation but you did not remove these symlinks. See why that was problematic? signature.asc Description: This is a digitally signed message part
Re: Simple instructions for installing Lilypond
Le dimanche 14 mai 2023 à 12:15 +0100, David Sumbler a écrit : > It's a while since I used Lilypond. I have a bit of tweaking I want to do to > some scores, so thought I should download the latest version. In the end, I > decided to use v2.24.1, rather than 2.25.4, > although I have mostly used the "unstable" versions in the past. > > Lilypond used to use a global install, and it was the work of a few minutes > to download and install this on my Linux machines, including all the > documentation too if one added the -d flag. > > I have managed to install Lilypond, and even the docs, a couple of times > since it changed to a sort of flatpack design. Each time it has taken me a > long time to get it all working. Today I have > spent well over an hour messing about, and I have now managed to get lilypond > installed and also the documentation. > > But convert-ly doesn't work: I get a "/home/david/lilypond/usr/bin/python3: > not found" error. This is probably because the convert-ly script I have in > my ~/bin/ folder needs amending, but I can > see myself having to spend another hour or two trying to sort out what is > going wrong and how to change it. > > What seems to be missing is a simple to find and to follow set of > instructions on how to install Lilypond. I was surprised to see that the > Learning Manual now encourages users to use a package from > their distro. This seems to be a change of policy: previously, the website > discouraged users from doing this, because the repositories usually have out > of date versions. But perhaps this is the > path I should go down, simply to save time. > > Sorry, this is just a grumble about having to mess about so much to get > Lilypond functioning. But surely there ought to be some sort of instructions > on the download site about how to get everything > installed and working. What does “install” mean to you? This is a serious question, not hair splitting. Depending on what you actually want to do with LilyPond, the way to “install” it can be vastly different. If you just want to run it from the command line, then you don't need to install it in any way, you can just run "~/where/you/unpacked/the/archive/bin/lilypond". If you want to use it *regularly* from the terminal, or if you want some tool (e.g., Emacs) to find it as just "lilypond", you can just prepend the right directory to your PATH by adding this to your shell startup file (e.g., ~/.bashrc): export PATH=/where/you/unpacked/the/archive/bin:$PATH and this will make it callable as "lilypond". If you want to use it with Frescobaldi, that's in the learning manual, but I suppose you saw that. For the documentation there is no real "installation" process in any case (OK, except maybe if you want the Info documentation). To me, the problem with “there should be a simple way to install LilyPond” is that “install LilyPond” is not something well-defined at all. There is also a purely psychological issue that some people think it's a must to “install” something in some way before being able to use it. There are good reasons why the script that used to be shipped isn't shipped anymore (for example: it would not work well with having several versions in parallel). signature.asc Description: This is a digitally signed message part
Simple instructions for installing Lilypond
It's a while since I used Lilypond. I have a bit of tweaking I want to do to some scores, so thought I should download the latest version. In the end, I decided to use v2.24.1, rather than 2.25.4, although I have mostly used the "unstable" versions in the past. Lilypond used to use a global install, and it was the work of a few minutes to download and install this on my Linux machines, including all the documentation too if one added the -d flag. I have managed to install Lilypond, and even the docs, a couple of times since it changed to a sort of flatpack design. Each time it has taken me a long time to get it all working. Today I have spent well over an hour messing about, and I have now managed to get lilypond installed and also the documentation. But convert-ly doesn't work: I get a "/home/david/lilypond/usr/bin/python3: not found" error. This is probably because the convert-ly script I have in my ~/bin/ folder needs amending, but I can see myself having to spend another hour or two trying to sort out what is going wrong and how to change it. What seems to be missing is a simple to find and to follow set of instructions on how to install Lilypond. I was surprised to see that the Learning Manual now encourages users to use a package from their distro. This seems to be a change of policy: previously, the website discouraged users from doing this, because the repositories usually have out of date versions. But perhaps this is the path I should go down, simply to save time. Sorry, this is just a grumble about having to mess about so much to get Lilypond functioning. But surely there ought to be some sort of instructions on the download site about how to get everything installed and working. David
Re: lilypond-user Digest, Vol 246, Issue 40
Le samedi 13 mai 2023 à 21:23 -0600, Jeff Olson a écrit : > > > > > Excellent! How would you similarly circle a rest (both r and f''\rest)? > For technical reasons, you would have to use the form with \balloonGrobText as in the message I later corrected, not with \balloonText. signature.asc Description: This is a digitally signed message part
Re: Missing barline
Hi Rip_Mus,
Try:
\relative c' {
c1 \bar ".|:-|" \break
c1
}
Cheers,
Pierre
Le dim. 14 mai 2023 à 11:17, Rip _Mus a
écrit :
> Hello,
> in the following minimal example, at the end of the first line, the
> barline is missing:
>
> ```
> \version "2.24.0"
> \relative c' {
> c1 \bar ".|:" \break
> c1
> }
> ```
>
> Is it possible to find a simple solution to implement?
>
> Thank you!
>
> Rip_mus
>
Missing barline
Hello,
in the following minimal example, at the end of the first line, the barline
is missing:
```
\version "2.24.0"
\relative c' {
c1 \bar ".|:" \break
c1
}
```
Is it possible to find a simple solution to implement?
Thank you!
Rip_mus
Re: Cannot identify a missing font for desired Lilypond output
Le dimanche 14 mai 2023 à 10:59 +0200, Volodymyr Prokopyuk a écrit : > * The missing gsfonts package was the root cause of the issue Oops, gsfonts indeed and not ghostscript, sorry for the confusion. (These fonts are part of Ghostscript, but distributions can package them separately.) > By the way, what font from the gsfonts package does Lilypond use as a default > font? The cryptic names of the pdffonts do not help with finding out the name > of the default font. They are documented here: https://lilypond.org/doc/v2.25/Documentation/contributor/requirements-for-running-lilypond Namely, C059, Nimbus Sans and Nimbus Mono PS. Best, Jean signature.asc Description: This is a digitally signed message part
Re: Cannot identify a missing font for desired Lilypond output
Hi Jean, I finally managed to find the root cause (the missing gsfonts package) and fixed the problem! I provide my current working setup for others if they face similar issues - I'm using EndeavourOS with i3wm - I successfully build Lilypond v2.25.4 from source with the following commands - From the lilypond2.25.4/build directory I execute - ../autogen.sh --noconfigure - ../configure --prefix=$HOME/.lilypond --disable-documentation \ GUILE_FLAVOR=guile-3.0 - The explicitly installed minimal dependencies are yay -S ghostscript gsfonts fontforge t1utils texlive-langcyrillic - The missing gsfonts package was the root cause of the issue By the way, what font from the gsfonts package does Lilypond use as a default font? The cryptic names of the pdffonts do not help with finding out the name of the default font. Thank you, Jean, and have a great day! Vlad On Sun, May 14, 2023 at 12:43 AM Jean Abou Samra wrote: > Le samedi 13 mai 2023 à 23:56 +0200, Volodymyr Prokopyuk a écrit : > > Hi Jean, > > I think you have found the solution! You mentioned that Ghostscript > provides the default font. Ghostscript is not installed in my new system as > I thought that it is not necessary as I use the Cairo backend. I did see > the warning in the configure script about the recommendation of installing > the Ghostscript, but I ignored it. Maybe it makes sense to set Ghostscript > as a required dependency. > > Tomorrow I'll install Ghostscript, rebuild Lilypond and let you know the > outcome. > > Thank you very much for your tireless and very professional support. I > sincerely appreciate it! > > > > Ah, if you build LilyPond from source, that indeed makes sense. > > I'm not sure the configure script should really check for the fonts to be > installed. In the past, it used to do that plus copy them into internal > directories, but it was removed for good reasons; see commit > 5689c2721530c6ded22b6291ebb06d10adb5bc28. The reasons given in th commit > message mostly apply to the "installing part", but build system complexity > does apply to looking for them. Plus, not checking for them is conceptually > correct because LilyPond doesn't need them at build time. If you are a > distro packager for example, you can very well build LilyPond into an > environment without the fonts. They only need to be present at runtime. > > By the way, no need to recompile LilyPond after installing Ghostscript. > > Best, > > Jean > >
