[Re-sending after changing my SMTP settings since I discovered lots of
my e-mails got blocked by spam filters.]
Folks,
the following is triggered mainly (but not solely) by my short exchange
with Dan
(https://gitlab.com/lilypond/lilypond/-/merge_requests/1617#note_1735195563):
We have some
Folks,
the following is triggered mainly (but not solely) by my short exchange
with Dan
(https://gitlab.com/lilypond/lilypond/-/merge_requests/1617#note_1735195563):
We have some context properties that are persistent (e.g.
figuredBassPlusDirection), whereas others are effective once and
I have sometimes needed to reprint a time signature even if it wasn't
different.
+1
Of course it would be nice to have a consistent behaviour for clef, time
signature, key signature. But note that those three entities are
conceptually different in that clef / key signature are per-staff
Well, if you didn’t recall the previous discussion but nevertheless proposed a
similar idea, that is an indication that there is some real need.
I actually lean towards adding \* and calling it a day.
+1 (not surprising given my opinion given in the 2021 thread).
I'd volunteer to do this (in
Am 20.01.23 um 07:38 schrieb Aaron Hill:
On 2023-01-19 8:54 pm, David Zelinsky wrote:
Am I misunderstanding something? Or is what it says in 3.2 a mistake?
If GitLab works similar to GitHub (which I have more experience with),
any new commits to your branch should automatically be picked
Hi David,
Am 17.01.23 um 06:18 schrieb David Zelinsky:
Thanks. As I understand it I will need to first request and be granted
commit access. Or is there another way, given that I am new and
untested?
Welcome - it's great you want to contribute!
What's being "tested" is mainly your merge
Am 15.01.23 um 20:20 schrieb Jean Abou Samra:
Le 15/01/2023 à 20:11, Lukas-Fabian Moser a écrit :
So the setting seems to be used on a per-page basis,
The problem here is that during page breaking, the score-local layouts
are being taken into account, but not during page spacing.
Do you
Sorry for piping up:
Personally I don't see any problem with Jean's poll: It clearly was not
intended as a way to reach a democratic decision, but as a means of
obtaining a data point.
(which is surprising and my interpretation is that the question was
phrased wrongly: Currently, the only
I don't see that. layout/midi are different output media. paper has
some overarching information (like base file names). It also contains
some information pertinent to typesetting a whole document as opposed to
single scores, like paper dimensions. Things like staff sizes are a
whole lot
Hello Hassan,
Hello
I am hassan EL FATIHI author of hel-arabic.ly,
if you have questions or changes to propose I am at your disposal.
I have been practicing Arabic music for more than thirty years,
in addition I am a computer scientist which pushed me to program hel-arabic.ly
What's most
A logo will occupy a small fraction of the page. Do you really need
to have it in such high resolution that the file size becomes a
problem?
In practice, probably. (Although there are also things like
page-sized watermarks.)
Given "but" below, did you miss a "not" in this sentence?
Yes,
Am 30.12.22 um 17:34 schrieb Jean Abou Samra:
Le 30/12/2022 à 17:20, Lukas-Fabian Moser a écrit :
I agree with Jonas that it would be a considerable loss not to be
able to import vector graphics. I don't concur with Jean's argument
that one can replace them by using markup commands: One
Ok, in that case we can properly deprecate this once we have an
alternative (see above). I still think losing the ability to include
(external) vector graphics is a loss, though.
What are the chances of having a conversion tool that produces
LilyPond markup commands for the vectors in formats
Am 12.12.22 um 23:17 schrieb Jean Abou Samra:
Ha:
[... ... ...]
(utf-8-string "emmentaler-11 3.9453125" "6" (translate-stencil (0.0 .
0.0) (glyph-string
# "Emmentaler-11" 3.9443359375 #f
((0.785296062992126 (0.0 . 1.1225612496924213)
0.0 0.0 "six"))
Again, thanks for "holding my hands" while searching for the cause; I
try to follow your suggestions precisely, but am not able to "start
thinking for myself" at the moment:
Am 12.12.22 um 22:57 schrieb Jean Abou Samra:
Yet another question.
Can you try this:
\markup \override
Am 12.12.22 um 22:46 schrieb Jean Abou Samra:
Ah, another question, Lukas: what does the "locale" command give you?
Call me paranoid, but the accidental characters are obviously
non-ASCII, so the Unicode handling might go wrong somewhere.
lukas@Aquarium:~$ locale
LANG=de_DE.UTF-8
Hi,
OK. What do you get with
\version "2.23.82"
\new FiguredBass \figuremode {
\override BassFigure.stencil =
#(grob-transformer
'stencil
(lambda (grob orig)
(pretty-print (ly:stencil-expr orig) (current-error-port))
orig))
<6> <_+> <_-> <_!>
}
?
Thanks
I would very strongly suspect 2.23.10 with
https://gitlab.com/lilypond/lilypond/-/merge_requests/1409
New data: The problem starts with 2.23.8, incidentally the same
release that contain's Werner's modifications to bass figure glyph sizes.
I'm sorry, stupid mistake: Make that 2.23.10. (I'm
Am 12.12.22 um 01:36 schrieb Jean Abou Samra:
Le 12/12/2022 à 01:20, Jean Abou Samra a écrit :
Werner will know about this better than me, but I am still curious.
What does this give you?
\version "2.23.82"
#(ly:message "~s" (ly:font-config-get-font-file "emmentaler-20"))
\markup "♯"
Am 12.12.22 um 22:26 schrieb Jean Abou Samra:
Le 12/12/2022 à 22:11, Lukas-Fabian Moser a écrit :
I'm sorry not to have been more prompt in my replies, as I'm still
quite swamped.
To my knowledge, I have no globally installed lilypond. I don't
remember installing one
Hi all,
Anyway, this doesn't explain Lukas' original problem on Mint.
My conjecture was that Lukas has 2.22 installed globally like I have
2.23, and this would lead to characters not being found because the
2.22 Emmentaler doesn't have those new characters. Of course, we
need Lukas to tell
Hi Werner,
In any case, here are images again as attachments. They don't look
like Werner's.
Assuming that you run under GNU/Linux: Try to recreate all FontConfig
files with `fc-cache --really-force` (probably as a superuser, too).
I sometimes got issues with that.
Yes, I'm under Mint 20.3.
For your information, your email doesn't contain the images. I see in
the raw email content that you are using Thunderbird and your email is
sent in plain text. A plain text email can't contain images inline,
but as I have experienced myself, Thunderbird won't warn you in any
way if you add
Hi Jean,
How is it supposed to be? While I am ignorant about figured bass, I
don't see anything egregious.
For your information, your email doesn't contain the images. I see in
the raw email content that you are using Thunderbird and your email is
sent in plain text. A plain text email can't
Hi all,
if I do
\version "2.23.82"
\new FiguredBass \figuremode {
<6> <_+> <_-> <_!>
}
I get:
As soon as I do
\version "2.23.82"
\new FiguredBass \figuremode {
<6> <_+> <_-> <_!> <6!>
}
this becomes
I'm pretty sure this is not how it's supposed to be? (I'm very sorry to
bring this
Am 26.11.22 um 18:35 schrieb Lukas-Fabian Moser:
Am 26.11.22 um 18:11 schrieb David Kastrup:
\override NoteHead.color = red
actually lowers the barrier immensely compared with
\override NoteHead #'color = #red
red and #red are completely different Scheme entities.
Yes indeed (I suspect
lukas@Aquarium:~/git/lilypond/scm(master)$ git grep darkred
color.scm: (darkred 0.54509803921568623 0 0)
output-lib.scm:(define-public darkred '(0.5 0.0 0.0))
lukas@Aquarium:~/git/lilypond/scm(master)$ git grep darkgreen
color.scm: (darkgreen 0 0.39215686274509803 0)
Am 26.11.22 um 18:11 schrieb David Kastrup:
\override NoteHead.color = red
actually lowers the barrier immensely compared with
\override NoteHead #'color = #red
red and #red are completely different Scheme entities.
Yes indeed (I suspect red gets parsed to #'red, no?). I never took the
Hi Jean,
FWIW, the last one
a4_boringly
is something I wouldn't do, since
a_boringly
does not work
Yes, d'accord.
Personally, I tend to leave out # when possible for numbers,
and also leave out #' for symbols when possible because it
is not only shorter, but allows the syntax
Hi Werner,
In the NR, most such functions have its argument starting with `#`,
for example
```
\ottava #-2
```
Are there still cases where `#` is mandatory for numbers? Otherwise
the documentation could be updated to remove all `#`.
Yes, there are: In markup, for example.
\markup
Hi Jean-Julien,
It's seems to be a very «franco-french» notation but denoting a pretty
important chord in tonal harmony: the dominant seventh.
You can see it on the french wikipedia page (cf
Hi Jean,
With your changes to figured bass in 2.23.12, this snippet
no longer has the '+' centered below '7':
\version "2.23.11"
\new FiguredBass {
\figuremode {
<7 _\+>
}
}
Do you consider this a problem?
(I am ignorant about figured bass, there is just a user
on lilypond-user-fr,
quot;,
scm_string_to_symbol (s));
BTW, no space between dash and %s?
That was me :-).
commit 61cd3bc1f3254b430bf04acd587c4082253602d4
Author: Lukas-Fabian Moser
Date: Mon Dec 27 01:25:43 2021 +0100
Make articulation-type a symbol? instead of a string?
This was an ancient TODO (see
Honestly, I think that your criteria for creating pre-release of 2.24
are too rigid. As far as I can see, doing a 2.23.80 release *right
now* is the way to go.
Fine, if you disagree with the plan laid out in August, I invite you to
volunteer taking care of the releases and the related
Hi Andrew,
Am 07.09.22 um 10:19 schrieb Andrew Bernard:
I cant find out what tlasm is. It's a missing dependency for the
build. Google's indexing of billions of pages produces nothing, unless
I am dreaming. Could somebody help me understand what this program is
and where to find it?
Hi Andrew,
Andrew Bernard schrieb am Mo., 5. Sept. 2022,
11:51:
> In 2.23.12 at least, there is an error for gvim (missing comma in list)
> in the lilypond-invoke-editor script, and the column number for geany is
> wrong as it numbers columns from zero not one.
>
> While here, should we drop
Jean Abou Samra schrieb am Mi., 24. Aug. 2022, 14:18:
> Le 24/08/2022 à 10:28, Lukas-Fabian Moser a écrit :
> > This has the drawback, of course, of needing c:4 instead of c4, but
> > personally, I wouldn't be bothered very much by this. But of course
> > it's very likeliy
Am 22.08.22 um 20:59 schrieb Jean Abou Samra:
And what do you think about
f1*2:maj7 g:M7 g1:m7 ges1:M7 f1:maj7 ges1:M7
I’m not sure if native English speakers will find it weird to require “M” for a
plain major chord (in France I have mostly seen “Do M” and not “Do” when it was
meant as a
Am 22.08.22 um 21:34 schrieb Aaron Hill:
On 2022-08-22 6:12 am, Lukas-Fabian Moser wrote:
I think it would be a considerable gain in heavy-handedness if I would
have to do
1*2 1 1
instead of
f1*2:maj7 g:7 g1:m7 ges1:7 f1:maj7 ges1:7
Not to sound contrarian, but I would very much welcome
Am 13.08.22 um 22:04 schrieb David Kastrup:
We had this discussion a longer time ago, with chords and notes
conflicting in that : is used for tremolo notation, too.
For context:
https://mail.gnu.org/archive/html/lilypond-devel/2012-09/msg00160.html
[GLISS] Unifying \chordmode and \notemode
Am 01.08.22 um 09:05 schrieb Werner LEMBERG:
GregorianTranscriptionStaff currently shows a time signature. Is
that desirable?
As discussed in
https://gitlab.com/lilypond/lilypond/-/merge_requests/1515#note_1045453533
I think it makes sense to have time signatures if you transcribe
Well, you should at least add examples in the form of regtests, and in
case of something like Bezier::solve_point it would make sense to take
stock of what there is on the C++ side and see whether
Bezier::solve_point would make sense as an integral part of a larger
whole that gives a
Folks,
is it acceptable to submit a MR that adds a scheme interface to some C++
routine without using that new interface in LilyPond proper?
In my case, I made Bezier::solve_point Scheme-visible for some work
project of mine that is too spezialized to submit as a MR (at least for
the time
Is there any way to get this repeat structure with the recent
repeat additions? This is from a question on the user list.
||: A:|| B||
Fine D.C. Al Fine
-> A A B A
How cruel it would have been not to support sonata form!
... that would be some tonally renegade
Hi Jean & everybody,
Am 23.05.22 um 19:33 schrieb Jean Abou Samra:
If you have a core dump, that normally means you encountered a
bug in LilyPond. Having such a crash is quite rare, so it seems
like bad luck if you hit one as a new user
That's what I told Andrea when she asked me (we're at
I don't see one either, but there appear to be scores in the wild that
use them (I saw an example on the user list, which is what triggered
the original post). The question is whether we consider it fine to
start giving an error on them (it's not a fatal error, doesn't prevent
compilation of
But as you say "most applications". Partial or incomplete measures
are not always anacruses. Hymns nearly always cut the final measure
short so it logically joins with the partial measure at the start of
the tune. You might also find incomplete measures in volta sections
when the
What about providing a new command `\upbeat` and moving `\partial`
into oblivion? Compare this to `\tuplet` vs. `\times`.
Werner
... Or you could use the brand new command \upbeat when music follows,
keep \partial, and you don't have to worry about backwards
compatibility.
This
Folks,
Am 17.02.22 um 11:48 schrieb Xavier Scheuer:
> If I have a book that is structured something like below, then LP
> produces two midi files: foo.midi and foo-1.midi.
>
> Is there a way I can coerce the names into "bar.midi" and "baz.midi"
> within LP? Or is this something best down
Hi Colin,
forgive me for butting in as someone who has made very few contributions
(but followed some of the discussions quite closely over the last few
years):
All the above can be overridden by any developer with access, where
judgement calls for expediting an MR, or it is clearly
Hi Jean,
Both of these cases seem to work the same as in
current versions if I do
[...]
SCM
assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL)
{
- for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p))
+ for (SCM p = alist; scm_is_pair (p) && scm_is_pair (scm_car (p)) &&
Hi David,
I've been using Lilypond for a few years, and only yesterday learned
about the point-and-click feature in pdf output. In particular, I had
no idea that by default Lilypond includes absolute pathnames to local
source files on my system as metadata in the pdf output files. So when
I
\version "2.23.6"
myScripts = \default-script-alist
myScripts.tenuto.padding = 5
\layout {
\context {
\Score
scriptDefinitions = #myScripts
}
}
{
a--
}
(One might also skip defining a new variable and instead change
default-script-alist directly, but it has to be re-read
Hi Jean, (CCing devel because of the stuff below the asterisks)
Although this approach manipulates internal data structures of
LilyPond, it has the advantage of dealing with your issue at the root
and not causing side effects for other scripts. Unfortunately, this
approach does not work
Yes. This overrides the default after-line-breaking
callback, which causes trouble if that callback was
supposed to do something important. Harm's code was
written at a time where the grob-transformer was
not available. It's now possible to write this code
in a way that works for grobs with an
Hi Dan & Werner,
Am 22.12.21 um 15:41 schrieb Dan Eble:
```
{
\override DoublePercentRepeat.slope = #.3
\repeat percent 2 { e'2 e' e' e' }
\revert DoublePercentRepeat.slope
}
```
I'd recommend using \temporary\override in to mimic \once behaviour more
closely:
\version "2.23.5"
\new Score \with {
\consists "Balloon_engraver"
}
Ah, sorry, I forgot one:
\new Score \with {
\consists Balloon_engraver
}
Lukas
Hi Werner,
Am 21.12.21 um 23:07 schrieb Werner LEMBERG:
Please have a look at the following example.
```
\new Score \with {
\consists "Balloon_engraver"
} \new Staff {
\repeat "percent" 2 {
e'4 e' e' e' |
\balloonGrobText #'PercentRepeat #'(0 . 1) \markup "Repeat"
}
Hi Jean,
Feedback is appreciated.
For what it's worth: I like that design (only having looked at the
style-test.zip file) a lot. It's unobtrusive, yet makes it easier to
parse the structure of a code sample at first glance.
Of course, that doesn't help at all with the issues raised by
For a data point, about 1 Windows machine in 8
is running Windows these days.
... while the remaining 7 are not running.
(Sorry, not sure if the German pun works in English.)
So can we please try to avoid sarcasm and try to assume best intent on
the respective other's side? Having met both of you, I am sure this
assumption is actually quite reasonable.
Sorry for hitting the limits of my English language skills: I wanted to
say that I'm sure that the assumption of
It's great that you show so much patience with rank beginners in
LilyPond.
Gentlemen, please.
It's obvious and well-known that few people know LilyPond's design and
inner workings as well as David, so if he raises concerns about a design
question, it's a pretty safe bet that there's a
When Thomas Adès switches from 4/4 to 4/5, there is no way of knowing
which "graphical" note length (combination of notehead style and flag
count) is supposed to be used for the basic unit (of which 4 make up a
bar, and of which five equal the duration of a semibreve).
Example:
\version
Hi Kieren,
Am 14.11.21 um 15:00 schrieb Kieren MacMillan:
There just is no uniquely identified print form using a note in the
denominator for that time signature representation.
As I’ve explained several times, there is.
I don't think you're right.
It's well possible that I'm missing the
Yes. The numerical representation of traditional time signatures is a pair of integers. But the
"numerator" can be any integer. While the "denominator" can also be any
integer, it doesn't really represent an integer. It represents a duration; a fraction of a whole
note.
To make
Hi Carl,
Although the time signature looks like a fraction, it is not. A fraction has numbers in the
denominator and the numerator (and strictly speaking, a fraction properly has integers in the
numerator and denominator -- if they are not integers, it's a quotient, not a fraction, IIUC).
Hi Kieren,
Am 13.11.21 um 16:19 schrieb Kieren MacMillan:
1. Is there any objection to me adding a TimeSignature style which would
immediately apply to all already-accepted time signatures?
2. If not, does anyone have opinions on what that style name should be? (Ones
that seem like obvious
Hi Kieren,
See my “stylesheet” comment earlier in the thread: in a perfect world, a user
should be able to take any existing score and simply add
\override Score.TimeSignature.style = #'note-denom
and the output would be “as expected” — with a new function, a
search-and-replace (with
Wouldn't it be easier to define an independent \kierenTime function
that expects an integer (index?) numerator and a music (ly:music?)
denominator? Then we could just write
\version "2.22"
kierenTime =
#(define-void-function (num den) (index? ly:music?)
(format #t "~a\n" num)
Hi Kieren,
You’re not extrapolating the concept, as I have been asking people to, so I’ll
once again make it more explicit for you:
I want the user to be able to say
\tweak style #'note-denom \time 3/4.
or
\tweak style #'note-denom \time #'(3 . "4.")
or
\tweak style
Hi Elaine,
The first is, how is the usage of \time different in lyrics than anywhere
else?
Frankly, I was not aware that using \time inside lyrics was a thing.
What is the reason to use \time inside lyrics?
It is a suggested practice, is it the only way of doing certain things?
I'm not
Hi,
BTW, Gould gives the following example in her book (also noting that
it would be better to use 15/16 together with a '2+3 sempre' remark
instead).
3
--
8 ~ 8.
(the tilde denotes a tie).
Sorry if I miss the point completely (I only skimmed part of the e-mail
thread).
Hi Kieren,
A blatant counter-example is in the person of Harm.
So C++ and Scheme *are* [as I first suggested] separable?
There's lots of stuff one can do in Scheme alone. But it seems to me to
be a non-trivial task in general to decide a priori whether, given a
feature request or bug
Am 01.11.21 um 21:40 schrieb Jean Abou Samra:
In short: useless but not problematic.
Am 01.11.21 um 21:08 schrieb David Kastrup:
It's redundant. Not incorrect, at worst slightly inconsistent/ugly.
Thanks much to both of you (and also for the very enlightening code
snippets that make the
Folks,
while trying to tidy up ly/engraver-init.ly a bit (which seems to have
experienced some rank growth over the years) I stumbled upon:
\context {
\Staff
\type "Engraver_group"
\name "DrumStaff"
\alias "Staff"
% (etc.)
}
That's the only instance of a context definition that
this would have the advantage to be inline with the doc-string and
solve the issue at hand.
Should I prepare a MR?
Though, speaking of refactoring rounded-box-stencil.
It always bugs me to see some stencil overlaying to get a simple line.
Yes, that's an obvious and unpleasant limitation:
So in my impression, rounded-box-stencil might deserve a refactoring
anyway?
I would propose:
lukas@Aquarium:~/git/lilypond/scm(dev/lfm/rounded-box)$ git diff master
diff --git a/scm/define-markup-commands.scm b/scm/define-markup-commands.scm
index cb99a960fe..8b54fd048a 100644
---
Hi Harm,
I noticed a bug with recent master:
\markup \rounded-box "foo"
prints completely black.
First bad commit is:
commit 0772e38398972d6c2b4ba9e6f42e7725d973e08b
Author: Han-Wen Nienhuys
Date: Sun Aug 1 11:15:02 2021 +0200
Stop passing color names to output backends
Well,
No, that was the only required step after writing to the mailing list
(as documented in the CG), afterwards somebody with Owner permissions
(currently Han-Wen and me) have to press the button to accept, which I
just did. The complication here is that GitLab doesn't send email
notifications
Don't worry about breaking something! In almost all cases this gets
caught by the CI infrastructure. I think we all agree that it would
be very beneficial if you have commit rights.
Thanks! So I clicked the "Request access" button yesterday. Should I do
anything else?
Lukas
Am 06.10.21 um 21:21 schrieb Jean Abou Samra:
Hi all,
Rebasing and merging Lukas' \after patch this
morning, I had a wonder moment — wait, he still
doesn't have commit access? Seeing his recent patches,
which all required substantial discussion and
refinement as well as documentation and
[Jean]
What kind of next version, next minor of
current stable, i.e. 2.22.2, or next
stable release, 2.24?
Which leads me to ask:
@Jefferson: Would it be conceivable to do Homebrew builds also for
(odd-numbered) development versions of LilyPond? LilyPond tends to have
a conservative policy
Folks,
Am 05.10.21 um 14:39 schrieb Jefferson Felix:
No problem, I was just pointing out the reasons why Guile 1.8.8 was
not approved by the homebrew core. I even believe this will help
advance Guile 2 compatibility, and certainly the Lilypond development
community will pick up on any bugs.
Am 05.10.21 um 01:41 schrieb Dan Eble:
I'd basically be interested in trying to understand the mechanics involved, but
seeing as term started today at our university, I'm sceptical I can spend
serious time on this before Christmas break. (And there's a fair chance it
would be above my head
Does anybody see a better solution that might be good enough for the NR?
Well-invented. I don't see anything better.
Thanks (also for looking at this in the first place).
My feeling is that this should replace the "_something" example in the
NR, but because of its complexity, it should
Folks,
in my quest to maybe get rid of the recommendations of "\skip 1" for
lyrics in the NR I stumbled upon the following example in
http://lilypond.org/doc/v2.23/Documentation/notation/techniques-specific-to-lyrics.html:
% If you wish to show extenders and hyphens into and out
% of
28x { d a b fs | g d g a }
https://gitlab.com/lilypond/lilypond/-/merge_requests/937
That is a clever proposal. I am already fond of it.
Thank you.
This looks so "natural" (in the non-computer science-way of the meaning)
one is surprised it works. :-)
What this means is that if you
I answer somewhat orthogonally to your question: I think that for many
people it's a lot easier to digest the information
"\* creates unfolded repeats; this behaviour may be changed using
\defaultRepeatType percent"
That is one step forward, one step back: one advantage of a fixed
shorthand
Maybe it helps to give some context: The discussion started with the
problem of skipping notes in lyrics (using \addlyrics {} / \lyricsto
{}) in the documentation. In order to skip multiple notes, the
documentation currently suggests ugly things like
\repeat unfold 2 { \skip 1 }
that
a)
Hi Jean,
I think it's a trap to see \repeat unfold as syntactic
sugar for repeating a sequence of characters n times
in the input. For instance,
\relative { \repeat unfold 4 c'1 }
is not the same as
\relative { c'1 c'1 c'1 c'1 }
Yes, of course. But I'd be very surprised if a large
"\*" =
#(define-music-function (n mus) (index? ly:music?)
#{ \repeat $repeat-shorthand $n { #mus } #})
Instead of debating a default repeat type and function, why not provide access
to repetition as a music function with a clear name like
\repeatFunction type n music
And let the
IS unfold the best candidate? Just because the OP makes extensive use
of it, doesn't mean everyone else does. I'd rather it was percent, but
I suspect I genuinely am a minority.
One of the reasons I argue against making \repeat $n \music equivalent
to some \repeat X $n \music.
An
But your special-character argument made me think: Maybe it would be
possible to get rid of the * sign? Maybe I'm missing something, but
isn't \{unsigned int} still "available" so one could do \16 d8 instead
of \*16 d8 ? Of course, probably only David K. can say for sure what
implications that
Just as a counter-point, while I'm a light user / copyist, I don't
think I've EVER used repeat unfold, while repeat percent happens a lot.
I actually quite like the "\x16 d8" idea as a shortcut, but what I'm
saying is don't think it's a good idea, just because YOU do it a lot.
Other people
Hi,
In short, I propose to make the first argument to
\repeat optional, making \repeat n music equivalent to
\repeat unfold n music.
Thanks for working on that!
The issue I have with your idea is that to me, \repeat unfold and
\repeta volta/tremolo have slightly different semantics:
Hi Jonas,
If I'm not wrong, my question is how to force a re-build of
out-www/en/identifiers.tely.
I think you need to delete out{,-www}/en/internals.texi. This will
retrigger the rule to dump the internal documentation, which is partly
included into the Notation Reference.
That did it.
Hi James,
See:
https://lilypond.org/doc/v2.21/Documentation/contributor-big-page.html#building-a-single-document
Did you do the 'touch' command?
Now I did :-) (thanks!), but touch'ing notation.tely doesn't do the trick.
If I'm not wrong, my question is how to force a re-build of
but the kerning of "Av" in
doesn't seem right to me. Is that as it should be? (The image is
from the pdf in the official 2.22/2.23 build.)
... no image...
Sorry, shouldn't use inline images. See attached.
Lukas
Hi,
I'm probably missing something very obvious:
After changing a docstring in ly/music-functions-init.ly, what steps are
necessary to re-build notation.pdf in order to check the result in "A.19
Available music functions"? If I only delete notation.pdf and re-build
it using
make -C
Just from comparing those statements: Would it be reasonable (and maybe
generally useful) to make global_path.find (used in gulp_file_to_string,
lily-guile.cc) available at scheme level?
see ly:find-file.
Aah, thanks much (sorry I didn't see it).
So then, Valentin, want you asked for seems
1 - 100 of 153 matches
Mail list logo
