On Thu, 10 Apr 2025 at 02:34, Mike Stay wrote:
>
> For some reason I can't fathom, every capital N in my lyrics is being
> replaced with U+1ECA (Latin Capital Letter I with Dot Below). I'm on
> macos Sonoma 14.6 running Frescobaldi 3.3.0, which calls out to
> lilypond 2.24.4. What could possibly b
My version 2.25.25 correctly renders the lyrics as "Na Na".
That certainly does. It's an Apple problem, not a lilypond problem. Thanks!
On Wed, Apr 9, 2025 at 7:09 PM David Wright wrote:
>
> On Wed 09 Apr 2025 at 16:00:48 (-0600), Mike Stay wrote:
> > For some reason I can't fathom, every capital N in my lyrics is being
> > replaced with U+1ECA (Latin C
On Wed, 09 Apr 2025 18:20:06 +0800 Timothy Lanfear
wrote ---
> \score {
> <<
> \new Staff \with { \consists Text_mark_engraver } { \mark
> \default c''1 \textMark "molto" c'' }
> \new Staff { \mark \default c'1 \textMark "molto" c' }
On Wed 09 Apr 2025 at 16:00:48 (-0600), Mike Stay wrote:
> For some reason I can't fathom, every capital N in my lyrics is being
> replaced with U+1ECA (Latin Capital Letter I with Dot Below). I'm on
> macos Sonoma 14.6 running Frescobaldi 3.3.0, which calls out to
> lilypond 2.24.4. What could pos
For some reason I can't fathom, every capital N in my lyrics is being
replaced with U+1ECA (Latin Capital Letter I with Dot Below). I'm on
macos Sonoma 14.6 running Frescobaldi 3.3.0, which calls out to
lilypond 2.24.4. What could possibly be causing this?
Here's the source:
```
\version "2.18.2"
Il giorno mer 9 apr 2025 alle 19:32:49 +02:00:00, Simon Albrecht
ha scritto:
On 09.04.25 16:34, Federico Bruni wrote:
It seems that you are running it from source, even if you call
`frescobaldi` and not `python -m frescobaldi` (in the git dir).
Maybe you have more than one frescobaldi in
> On 23 Mar 2025, at 15:59, Hans Aikema wrote:
>
>
>
>> On 21 Mar 2025, at 17:00, Valentin Petzel wrote:
>>
>> Hello Ad,
>>
>> what you want is
>>
>> \paper {
>> ragged-right = ##t
>> }
>>
>> the issue with this is that it will shorten the staff. So use
>>
>> \layout {
>> \context {
>
On 09.04.25 16:34, Federico Bruni wrote:
It seems that you are running it from source, even if you call
`frescobaldi` and not `python -m frescobaldi` (in the git dir).
Maybe you have more than one frescobaldi in your PATH?
I do. Here’s their respective outputs:
~$ bin/frescobaldi
Traceback (m
Thanks, Hans. Your explanation clarifies the situation nicely.
Best,
David
> On 04/09/2025 5:39 AM EDT Hans Aikema wrote:
>
>
>
>
> > On 9 Apr 2025, at 10:08, David House wrote:
> > So, going through the tutorial. I am confused about the ' designating
> > middle C.
> >
> > This
Il giorno mer 9 apr 2025 alle 16:14:08 +02:00:00, Simon Albrecht
ha scritto:
Tremendous news, wonderful to hear!
Being clueless however how to deal with any python issues on
updating…
I had a working install, on Linux Mint, and after git pull-ing both
the main app and python-ly, I get thi
Tremendous news, wonderful to hear!
Being clueless however how to deal with any python issues on updating…
I had a working install, on Linux Mint, and after git pull-ing both the
main app and python-ly, I get this on the console:
~$ frescobaldi
Traceback (most recent call last):
File "/usr/l
You could set the orientation with a Guile variable that's useful, thanks
On 09/04/2025 12:14, damianlegassick wrote:
Hi all
If I wanted do something equivalent to this (which I know does not
work) - what's the best way to go about it?
\tag #'landscape #(set-default-paper-size "a4" 'landscape)
\tag #'portrait #(set-default-paper-size "a4" )
You could set the ori
On 9 Apr 2025, at 13:25, Lucas Cavalcanti wrote: I think
that I may have misunderstood your question... if you want the possibility of two
different outputs (hence the use of tags) you'll need to use different book blocks.
Paper instructions must be made on the top of the file or on a paper bl
I think that I may have misunderstood your question... if you want the
possibility of two different outputs (hence the use of tags) you'll need to
use different book blocks. Paper instructions must be made on the top of
the file or on a paper block (on top of a file or at first in the paper
block).
Tags don't need to always reference musical expressions; you can use tags
on \set commands too (like "tag #'tablature { \set TabStaff.minimumFret =
#2 }").
But in this case you have presented, it would be wiser to use the \bookpart
block to each section that needs the paper rotated (using the
set-p
On 07/04/2025 03:07, James Harkins wrote:
OK, now a real question (after -- I think -- RTFMing this time).
I was looking for a way to have a text mark, e.g. '15-20" electronics' --
appear only once at the top of a score system, while also appearing in each of the
parts (in the way that a re
Hi all If I wanted do something equivalent to this (which I know does not work) - what's the best
way to go about it? \tag #'landscape #(set-default-paper-size "a4" 'landscape) \tag
#'portrait #(set-default-paper-size "a4" ) thanks Damian
On 07/04/2025 03:07, James Harkins wrote:
OK, now a real question (after -- I think -- RTFMing this time).
I was looking for a way to have a text mark, e.g. '15-20" electronics' --
appear only once at the top of a score system, while also appearing in each of the
parts (in the way that a rehea
> On 9 Apr 2025, at 09:02, Helge Kruse wrote:
>
> I am sometimes not happy with the order of accidentals that Lilypond
> places. In the following example I would like to have the sharp right of
> the flat accidential, i.e. more narrower to the fis notehead:
>
> \version "2.24.4"
> \relative c
> On 9 Apr 2025, at 10:08, David House wrote:
>
> So, going through the tutorial. I am confused about the ' designating middle
> C.
>
> This is the coding in the example of page 15 of the tutorial manual which
> places c' in within the bass clef staff:
>
> \relative {
> \clef bass
> \tim
So, going through the tutorial. I am confused about the ' designating middle C.
This is the coding in the example of page 15 of the tutorial manual which
places c' in within the bass clef staff:
\relative {
\clef bass
\time 3/4
\tempo "Andante" 4 = 120
c,2 e8 c'
g'2.
f4 e d
I am sometimes not happy with the order of accidentals that Lilypond
places. In the following example I would like to have the sharp right of
the flat accidential, i.e. more narrower to the fis notehead:
\version "2.24.4"
\relative c {
\key d \minor
\clef bass
}
How can I tweak the accide
24 matches
Mail list logo
