Robin: That worked (especially after putting it in each hand in the piano
score. Thanks
Mike Dean
On Sat, Oct 3, 2020 at 1:18 PM Robin Bannister wrote:
> Mike Dean wrote:
> > Now to hide the warning 3/4 before the start of the Trio (I can take
> the \time
> > 3/4
> > out, but that also takes o
Mike Dean wrote:
Now to hide the warning 3/4 before the start of the Trio (I can take the \time
3/4
out, but that also takes out the time sig at the start of the
Trio)looking at the LSR did not give me anything to get a handle on
Check out
https://lists.gnu.org/archive/html/lilypond-user/2
No worries! Since I don’t have your file, I can’t know what warning you get.
On 3. Oct 2020, 19:59 +0200, Mike Dean , wrote:
> Martin: Perfect!!! Thanks
> Now to hide the warning 3/4 before the start of the Trio (I can take the
> \time 3/4
> out, but that also takes out the time sig at the start
Martin: Perfect!!! Thanks
Now to hide the warning 3/4 before the start of the Trio (I can take the \time
3/4
out, but that also takes out the time sig at the start of the
Trio)looking at the LSR did not give me anything to get a handle on
Mike Dean
On Sat, Oct 3, 2020 at 2:08 AM Martín Rincó
Mike, to make the fermata appear at the end of the line and not at the
beginning of the next line try using \once \override Score.RehearsalMark
#'break-visibility =
#begin-of-line-invisible before the \mark.
Cheers,
Martín.
On 3. Oct 2020, 04:34 +0200, antlists , wrote:
>
> the
On 03/10/2020 03:32, Mike Dean wrote:
Not really sure how to get the fermata over the repeat bar line rather
than over the clef on the next line
Isn't this the default behaviour of \uFermata and friends?
Sorry I can't from memory be more specific, but I know my battle with
fermatas was gettin
\version 2.20
{
g'4 e8 c d b |
c4_\markup Fine r \bar ":|." \mark\markup{\musicglyph #"scripts.ufermata"}
}
%End Minuet section
\break
\relative c''{
\time 3/4
\partial 4
\repeat volta 2 {
e8\mp \mark "Trio" }
Not really sure how to get the fermata over the repeat bar line rather than
over the c
On 01/10/2020 19:27, Carl Sorensen wrote:
Variables can only be defined at top level, not inside a score.
https://lilypond.org/doc/v2.20/Documentation/notation/file-structure
I just shove all of this sort of stuff in an include file, and include
it at the top.
I've come across things like sf
Thanks, Carl, for the clarification..
Mark: I was coding (from memory) what was one of the Minuets in Hob.IX:8
("12 Minuets for Clavecin or Pianoforte", as it turned out after a lot of
spade work; I had thought to be a work by Mozart in his Divertimenti).
Having obtained the sheet music, I was fixi
Variables can only be defined at top level, not inside a score.
https://lilypond.org/doc/v2.20/Documentation/notation/file-structure
Carl Sorensen
Hello Mike,
This works :
\version "2.20.0"
rf = #(make-dynamic-script "rf")
{ a \rf }
JM
> Le 1 oct. 2020 à 19:43, Mike Dean a écrit :
>
> Having stumbled across entering in \fz directly, I didn't explore any further
> using #(make-dynamic-script).
> But since you mentioned, looking at exa
Having stumbled across entering in \fz directly, I didn't explore any
further using #(make-dynamic-script).
But since you mentioned, looking at examples in the Notation manual, I
understood that it should go before the relative command.
Precisely, I had this sequence:
\score {
fz = #(make-dynamic
Mike Dean writes:
> Two questions in typesetting a piece by Haydn:
> 1. Does Fz needs to be defined (unlike sfz)?
> 2. where should
> fz = #(make-dynamic-script "fz")
> be placed in order not to generate an error?
>
> C:/Users/Mike
> Dean/AppData/Local/Temp/frescobaldi-lis_ksvl/tmpgdr3w9ef/J-Hayd
Two questions in typesetting a piece by Haydn:
1. Does Fz needs to be defined (unlike sfz)?
2. where should
fz = #(make-dynamic-script "fz")
be placed in order not to generate an error?
C:/Users/Mike
Dean/AppData/Local/Temp/frescobaldi-lis_ksvl/tmpgdr3w9ef/J-Haydn-Minuet in
C-correct.ly:14:1 <0>:
Well, \fz did work without a prior definition (pleasant surprise for me,
since I didn't find a reference to it in the manual nor the LSR)
Mike Dean
On Wed, Sep 30, 2020 at 8:31 PM Mike Dean wrote:
> Two questions in typesetting a piece by Haydn:
> 1. Does Fz needs to be defined (unlike sfz)?
>
Ooops, sorry Claire, forgot to credit you for thanks too!
JM
> Le 26 août 2020 à 18:36, Jacques Menu a écrit :
>
> Hello folks,
>
> Thanks to Samuel and Fernando, I’ve been able to set these two
> Lua*TeX+se.engine files on Mac OS Mojave, taken from
> https://github.com/gregorio-project/greg
m not the one for the job. Again, thanks for your patience.
On 4/13/20 5:48 PM, Daniel Woodfield wrote:
I just realized that Lilypond 2.20 was released (sorry, I'm a little
slow to notice over here on Ubuntu LTS). I'm thinking about moving to
openSUSE when Leap 15.2 is released, b
> On 28 Mar 2020, at 13:14, Moritz Heffter wrote:
>
>> https://stackoverflow.com/questions/18758837/xcode-quit-unexpectedly-for-my-project-not-in-xcode-4-6-3
>
> But I found the following. In my my log files the issue occurs always with
> the same dylib:
> 85 libdyld.dylib 0x7fff6e
> On 28 Mar 2020, at 13:14, Moritz Heffter wrote:
>
>> https://stackoverflow.com/questions/18758837/xcode-quit-unexpectedly-for-my-project-not-in-xcode-4-6-3
>
> But I found the following. In my my log files the issue occurs always with
> the same dylib:
> 85 libdyld.dylib 0x7fff6e
>> On 27 Mar 2020, at 18:53, Moritz Heffter wrote:
>>
>>> Try in Terminal
>>> export PATH=/usr/bin:/bin:/usr/sbin:/sbin
>>>
>>> and then
>>> /opt/lilypond/bin/lilypond
>>
>> Hmm, I have done that, but unfortunately without progress.
>
> In the link below, the issue was solved by fixing the env
> On 27 Mar 2020, at 18:53, Moritz Heffter wrote:
>
>> Try in Terminal
>> export PATH=/usr/bin:/bin:/usr/sbin:/sbin
>>
>> and then
>> /opt/lilypond/bin/lilypond
>
> Hmm, I have done that, but unfortunately without progress.
In the link below, the issue was solved by fixing the environment
>> On 26 Mar 2020, at 19:03, Moritz Heffter wrote:
>>
>> Thanks for the information. I’ve reinstalled the 2.19 package and put
>> /opt/lilypond/bin in the PATH. I can execute lilypond from the Terminal
>> still getting the segmentation fault. But now with a different reason:
>>
>> Termination
> On 26 Mar 2020, at 19:03, Moritz Heffter wrote:
>
> Thanks for the information. I’ve reinstalled the 2.19 package and put
> /opt/lilypond/bin in the PATH. I can execute lilypond from the Terminal still
> getting the segmentation fault. But now with a different reason:
>
> Termination Sign
Thanks for the information. I’ve reinstalled the 2.19 package and put
/opt/lilypond/bin in the PATH. I can execute lilypond from the Terminal still
getting the segmentation fault. But now with a different reason:
Termination Signal:Segmentation fault: 11
Termination Reason:Namespace SIGN
> On 26 Mar 2020, at 12:57, Moritz Heffter wrote:
>
> BTW, /opt is in read-only mode. I’m not able to remove it.
One may have to give the Terminal app permissions, which I did in the past, but
it is not there now, so it may or may not be required.
https://osxdaily.com/2018/10/09/fix-operatio
You are running a brew-installed Lilypond, my dear ;-)
Try the following in a terminal:
$ /Applications/LilyPond.app/Contents/MacOS/LilyPond
Cheers, RalfD
Am Donnerstag, 26. März 2020 10:57 CET, Moritz Heffter
schrieb:
> The error is logged for lilypond-bin when I run lilypond from the Termi
> On 26 Mar 2020, at 12:57, Moritz Heffter wrote:
>
> Well this is bringing me one step further. I think the problem is that some
> libraries are not found. Especially guile.
>
> I’ve now completely removed macports (I’ve installed it only because of
> Lilypond) and reinstalled the Lilypond
Well this is bringing me one step further. I think the problem is that some
libraries are not found. Especially guile.
I’ve now completely removed macports (I’ve installed it only because of
Lilypond) and reinstalled the Lilypond package of version 2.19 from Hans again.
It installs into /opt/li
> On 26 Mar 2020, at 10:57, Moritz Heffter wrote:
>
> The error is logged for lilypond-bin when I run lilypond from the Terminal:
>
> Process: lilypond-bin [8616]
> Path: /opt/lilypond/*/lilypond-bin
> Identifier:lilypond-bin
> Version:
The error is logged for lilypond-bin when I run lilypond from the Terminal:
Process: lilypond-bin [8616]
Path: /opt/lilypond/*/lilypond-bin
Identifier:lilypond-bin
Version: 0
Code Type: X86-64 (Native)
Parent Process:zsh
> On 26 Mar 2020, at 10:36, Moritz Heffter wrote:
>
> Hum, I’ve tried out different settings now and also updated the system to the
> version 10.15.4 but it’s still the same error. I've also deactivated
> FileVault and gave.
>
> The log file says maybe a bit more precisely:
>
> Error Code:
Hum, I’ve tried out different settings now and also updated the system to the
version 10.15.4 but it’s still the same error. I've also deactivated FileVault
and gave.
The log file says maybe a bit more precisely:
Error Code: 0x0004 (no mapping for user data read)
Trap Number: 14
B
[Keep the cc to the list so other can follow the issue.]
> On 24 Mar 2020, at 11:45, Moritz Heffter wrote:
>
> My PATH variable shows the following:
>
> /Users/username/Library/Python/3.7/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin
>
> My
> On 24 Mar 2020, at 10:43, Moritz Heffter wrote:
>
> Hum, that mean some configuration on my machine is the problem? I use another
> package manager (brew). Could it be that there arise some incompatibilities?
It might, if you have stuff that overrides what lilypond expects to use. Check
in
Am Dienstag, den 24.03.2020, 10:43 +0100 schrieb Moritz Heffter:
> Hum, that mean some configuration on my machine is the problem? I use
> another package manager (brew). Could it be that there arise some
> incompatibilities?
>
I'd be intersted to know if there is _any_ correlation to your MkDocs
Hum, that mean some configuration on my machine is the problem? I use another
package manager (brew). Could it be that there arise some incompatibilities?
Best,
Moritz
> Am 24.03.2020 um 10:18 schrieb Hans Åberg :
>
> The MacPorts 2.19.84 installer was made on essentially the same hardware.
>
The MacPorts 2.19.84 installer was made on essentially the same hardware.
> On 24 Mar 2020, at 09:38, Moritz Heffter wrote:
>
> It’s a new MacBook Pro 13‘ (2019) with 16/512 and an i5 (4 cores) 1,4 GHz
>
>> Am 23.03.2020 um 21:44 schrieb Hans Åberg :
>>
>> What computer model is this?
>>
>
It’s a new MacBook Pro 13‘ (2019) with 16/512 and an i5 (4 cores) 1,4 GHz
> Am 23.03.2020 um 21:44 schrieb Hans Åberg :
>
> What computer model is this?
>
>
>> On 23 Mar 2020, at 20:25, Moritz Heffter wrote:
>>
>> Thanks for this hint. I’m trying to install 2.20 on macOS Catalina (10.15.3)
What computer model is this?
> On 23 Mar 2020, at 20:25, Moritz Heffter wrote:
>
> Thanks for this hint. I’m trying to install 2.20 on macOS Catalina (10.15.3)
> and get a segmentation fault.
>
> I get this also with the version 2.19.84 mentioned below which might be
> pointing to a problem
Dear all,
Thanks for this hint. I’m trying to install 2.20 on macOS Catalina (10.15.3)
and get a segmentation fault.
I get this also with the version 2.19.84 mentioned below which might be
pointing to a problem on my machine. Does anyone have suggestions what I can
try?
Best,
Moritz
> Am 23
[Please keep the cc to the list so that others can follow the issue.]
With some programs, one may have to OK it in System Preferences > Security &
Privacy. But I think it is not needed for the MacPorts installer version.
> On 22 Mar 2020, at 23:17, Eric wrote:
>
> Actually, when this came up
> On 3 Mar 2020, at 05:14, Eric wrote:
>
> Actually, both the latest version and 2.19.84 seem not to launch at all on my
> iMac (late 2015, dual core, etc running os 10.15.3...) (2.19.84 did but it
> doesn’t.)
What binary are you using?
Actually, both the latest version and 2.19.84 seem not to launch at all on
my iMac (late 2015, dual core, etc running os 10.15.3...) (2.19.84 did but
it doesn’t.)
Thomas Morley writes:
> well, I've multiple guile-versions on my machine, though one of it is
> the distributed guile-1.8.
> If available it's the most easy way to get this one.
>
> Ofcourse the discussion is a little bit academic as you said...
> Nevertheless:
> (1)
> ~$ uname -a
> Linux kasten
On 18.07.19 14:37, Ralph Palmer wrote:
Has any progress been made in making a process available to install LilyPond 2.20 or 2.21 on Ubuntu 18.04? Back in March of this year (2019), there was a brief discussion about installing Guile 1.8 on Ubuntu 18.04, so that ly 2.20 could run. I tried to
scobaldi 3.0.0 under Ubuntu
> >> 18.04.2.
> >>
> >> Has any progress been made in making a process available to install
> >> LilyPond 2.20 or 2.21 on Ubuntu 18.04? Back in March of this year
> >> (2019), there was a brief discussion about installing Gu
On 2019-07-18 6:13 am, Thomas Morley wrote:
Am Do., 18. Juli 2019 um 14:37 Uhr schrieb Ralph Palmer
:
Greetings -
I'm running LilyPond 2.19.81 with Frescobaldi 3.0.0 under Ubuntu
18.04.2.
Has any progress been made in making a process available to install
LilyPond 2.20 or 2.21 on U
Am Do., 18. Juli 2019 um 14:37 Uhr schrieb Ralph Palmer
:
>
> Greetings -
>
> I'm running LilyPond 2.19.81 with Frescobaldi 3.0.0 under Ubuntu 18.04.2.
>
> Has any progress been made in making a process available to install LilyPond
> 2.20 or 2.21 on Ubuntu 18.04? Back i
Hi Ralph,
I'm running LilyPond 2.19.81 with Frescobaldi 3.0.0 under Ubuntu 18.04.2.
Has any progress been made in making a process available to install
LilyPond 2.20 or 2.21 on Ubuntu 18.04? Back in March of this year
(2019), there was a brief discussion about installing Guile 1
Il giorno gio 18 lug 2019 alle 14:37, Ralph Palmer
ha scritto:
Back in March of this year (2019), there was a brief discussion about
installing Guile 1.8 on Ubuntu 18.04, so that ly 2.20 could run. I
tried to follow the suggestions, but was unsuccessful.
Can you link to the instructions which
Ralph Palmer writes:
> Greetings -
>
> I'm running LilyPond 2.19.81 with Frescobaldi 3.0.0 under Ubuntu 18.04.2.
>
> Has any progress been made in making a process available to install
> LilyPond 2.20 or 2.21 on Ubuntu 18.04? Back in March of this year (2019),
> th
Greetings -
I'm running LilyPond 2.19.81 with Frescobaldi 3.0.0 under Ubuntu 18.04.2.
Has any progress been made in making a process available to install
LilyPond 2.20 or 2.21 on Ubuntu 18.04? Back in March of this year (2019),
there was a brief discussion about installing Guile 1.8 on U
On 03/30, Urs Liska wrote:
> >I'm not aware of any reason it wouldn't work on
> >18.04.
>
> except for the "small" issue of 18.04 not having Guile 1.8 anymore...
I hadn't been aware of this. It does complicate things a bit.
Since Guile 1.8 is also needed for Lilypond 2.18.2, I figured Ubuntu
18
Am 30. März 2019 20:06:50 MEZ schrieb Valentin Villenave
:
>On 3/30/19, Ralph Palmer wrote:
>> I think I missed something. Can I install 2.20 and/or 2.21 on Linux?
>I'm
>> not an expert, though I've used command line some. Will it be
>difficult
>> and/or dangerous?
>
>Hi Ralph,
>if you don’t wa
Am 30. März 2019 18:11:54 MEZ schrieb Mason Hock :
>On 03/30, Ralph Palmer wrote:
>> I think I missed something. Can I install 2.20 and/or 2.21 on Linux?
>> not an expert, though I've used command line some.
>
>I don't think that 2.20 has been released, but since you're comfortable
>with the comm
On 3/30/19, Ralph Palmer wrote:
> I think I missed something. Can I install 2.20 and/or 2.21 on Linux? I'm
> not an expert, though I've used command line some. Will it be difficult
> and/or dangerous?
Hi Ralph,
if you don’t want to bother with dependencies and compilation, you may
want to have a
On 03/30, Ralph Palmer wrote:
> I think I missed something. Can I install 2.20 and/or 2.21 on Linux?
> not an expert, though I've used command line some.
I don't think that 2.20 has been released, but since you're comfortable
with the command line you can build 2.21.
> Also, I'm running Ubuntu 18
Am 30. März 2019 15:50:05 MEZ schrieb Ralph Palmer :
>Greetings -
>
>I think I missed something. Can I install 2.20 and/or 2.21 on Linux?
You can *build* these on Linux. But if you don't have any specific reason I
wouldn't say it is worth the effort (although that effort might be a value in
it
Greetings -
I think I missed something. Can I install 2.20 and/or 2.21 on Linux? I'm
not an expert, though I've used command line some. Will it be difficult
and/or dangerous?
Also, I'm running Ubuntu 18.04.2 and Frescobaldi 3.0.0. Are there any known
conflicts?
All the best,
Ralph
Ralph Palme
hi everybody,
when will lilypond 2.20 be released? iiuc the last prerelease was 8 months ago
and i'm wondering whether development has stopped... i would like to use all
the new features but my university won't let me install unstable software.
thanks to all developers for making s
- Original Message -
From: "Thomas Spuhler"
To:
Sent: Saturday, February 07, 2015 11:53 PM
Subject: lilypond-2.20
I am the packager of Lilypond for Mageia. I haven't seen any development
releases since September
2014 which is really very unusual. Are there any expla
I am the packager of Lilypond for Mageia. I haven't seen any development
releases since September
2014 which is really very unusual. Are there any explanation for this.
We are pretty close to a new OS release and I would like to incorporate 2.20.0
--
Best regards
Thomas Spuhler
All of my e-ma
I am the packager of Lilypond for Mageia. I haven't seen any development
releases since September
2014 which is really very unusual. Are there any explanation for this.
We are pretty close to a new OS release and I would like to incorporate 2.20.0
--
Best regards
Thomas Spuhler
All of my e-ma
63 matches
Mail list logo
