On 2024-05-14 10:49, 周 卫星 wrote:
[HIGH] The LilyDev3 docker build is **MISSING SOME PACKAGES** and not
available for work out-of-box! To me it looks like a critical issue - why all
the bother with Docker when I need to search and install the missing packages
manually?
I believe that
On 2024-04-29 17:39, Steph Phillips wrote:
Hi there!
I'm an experienced Python developer with some additional background in
C# and C++ and would be really excited to contribute to LilyPond.
It's definitely hard to decide where to begin though, so I'm hoping you
can point me at the starting
On 2024-04-28 03:34, Werner LEMBERG wrote:
>
Independent of improving the metrics, maybe we could improve the
review workflow by adding dynamic control to the diff web page to
expand or collapse the entries based on a variable threshold.
Yes, this would be a nice feature – please submit an
On 2024-04-27 00:24, Werner LEMBERG wrote:
I'm working on a modification of `musicxml2ly` that will cause a
change in the result as shown by the attached images. However, our
regtest classifies this as 'below threshold' and doesn't display it.
Does anybody have an idea how to improve this?
?
When I test that assumption by removing the listener for articulations
from the Voice context listeners, the list of articulations is still empty.
cheers
Maurits
Op 16-04-2024 om 13:14 schreef Dan Eble:
On 2024-04-15 04:20, Maurits Lamers via Discussions on LilyPond
development wrote:
Hey
On 2024-03-13 20:09, Thomas Morley wrote:
I don't understand what you propose.
My advice was general software-design advice based on a hasty
consideration of your post, so I'm not really surprised.
To give a different example, let's look at make-dotted-bar-line (afaik
it's your code).
On 2024-03-13 17:35, Thomas Morley wrote:
currently I'm attempting to improve dashed/dotted bar lines wrt to
changed staff-space and span bars.
We use both definitions for BarLine _and_ SpanBar, but then SpanBar is
frequently a little off.
It would be nice to have a possibility to detect
On 2024-03-11 18:27, hassan.elfat...@free.fr wrote:
you delete
(define-safe-public FIVE-HALF-FLAT -5/2)
(define-safe-public SEVEN-HALF-FLAT -7/2)
(define-safe-public FIVE-HALF-SHARP 5/2
you delete (define-safe-public FIVE-HALF-FLAT -5/2)
As I understand it, this change was made after your
On 2024-03-07 09:24, hassan.elfat...@free.fr wrote:
by trying to make hel-arabic.ly dependent on arabic.ly without consulting me,
you screwed up the hel-arabic.ly file.
Neighbor,
1. You contributed to an open-source project. Proposed
changes are posted for public review. GitLab sends
On 2024-02-27 07:14, Luca Fascione wrote:
inline constexpr vsize VPOS (vsize(-1));
OK, but don't repeat the type.
inline constexpr auto VPOS = vsize (-1);
Personally, I don't like flower's aliases related to vsize,
ssize, and Real -- I'd rather just use standard names --
but I remember
On 2024-02-23 14:10, Mike Blackstock wrote:
> just above the Bulk Barn on Bloor... cheap pints
... 90% whey protein isolate by the kilo ...
But seriously: I'm not keen to tour the 18-lane highway to Hogtown just
to socialize for an hour; however, if this idea grew into a day-long
conference,
On 2024-02-10 07:52, Werner LEMBERG wrote:
systems like macOS that neither have or use '/bin/bash'.
Apple changed the default shell for new users to zsh about 5 years ago,
but bash is still there. I don't oppose making the build scripts more
portable, but let's not misunderstand the
On 2024-02-02 14:29, Éric Würbel wrote:
How can submit a patch ? forking the master branch and submitting a pull
request ?
Yes.
https://lilypond.org/doc/v2.25/Documentation/contributor/summary-for-experienced-developers
--
Dan
On 2024-01-20 20:55, Carl Sorensen wrote:
File
"/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/subprocess.py",
line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/usr/bin/tidy', '-o',
'/dev/null', '-q',
On 2023-12-07 05:12, Saul Tobin wrote:
I’d welcome feedback and I’d be happy to submit this as a pull request for
either OLL or Lilypond itself if there is interest.
They're "merge requests" on GitLab, but they smell as sweet. You would
likely get more engagement from busy developers if you
On Oct 21, 2023, at 01:12, Werner LEMBERG wrote:
>
>
>
>>> Some debugging shows it seems to be the latter: All top-level
>>> definitions are available as paper variables within a book's paper
>>> block, together with all paper variables of the top-level paper
>>> block:
>>>
>>> Is this really
On Oct 20, 2023, at 06:29, Werner LEMBERG wrote:
>>
>> Or is this an inheritance thing? Does a `\book` block inherit all
>> top-level expressions and convert them to paper variables?
>
> Some debugging shows it seems to be the latter: All top-level
> definitions are available as paper
On Aug 31, 2023, at 07:38, Jean Abou Samra wrote:
>
>
>
>> Le 31 août 2023 à 13:22, Dan Eble a écrit :
>>
>> My opinion hasn't changed since we instituted the automation. The previous
>> discussion is in the archive.
>
> I couldn't find it. Do yo
On Aug 31, 2023, at 02:46, Werner LEMBERG wrote:
>
>
>
>>> Colin, something that starts with 'Draft:' in the description
>>> should be omitted from the normal review cycle. So: MR 2089 is
>>> *not* on countdown. Please adjust the tag accordingly.
>>
>> Thanks for the clarification, Werner.
On Jul 27, 2023, at 08:22, Jean Abou Samra wrote:
>
> as Dan said, we're on C++17 now (and I think the experiment has lasted long
> enough without Guile quirks that actually using C++17 features would be fine
> by now).
Good, because I queued up a random bunch of minor improvements during my
On Jul 26, 2023, at 14:38, Jason Yip via Discussions on LilyPond development
wrote:
>
> * ../configure
> --prefix=/home/lj/projects/internships/2023/lilypond/build/release
> --disable-debugging --disable-optimising --enable-checking
> --enable-profiling 'CC=ccache clang' 'CXX=ccache
On Jul 9, 2023, at 10:39, Jean Abou Samra wrote:
>
> It definitely makes sense to keep the option to build without bytecode, since
> that is quite faster for incremental rebuilds (especially in Guile 2.2,
I think it makes sense to skip `make bytecode` when iterating on particular
tests, but I
On Jul 8, 2023, at 13:55, David Kastrup wrote:
>
> Ok, here is the deal: I think it probably is sanest to just ditch the
> operator for ly:pitch-negate and the equivalent for Moment. That being
> said, I've also found incorrect manual conversions in some code. The
> question is whether it is
I'm hitting this on master after (roughly) autogen.sh; make; make bytecode.
```
$ out/bin/lilypond ~/lilypond-src/input/regression/other/display-lily-tests.ly
GNU LilyPond 2.25.7 (running Guile 2.2)
Processing
`/home/user/lilypond-src/input/regression/other/display-lily-tests.ly'
[...]
On Jun 19, 2023, at 13:21, Jason Yip wrote:
> \set minSubdivideInterval = #(ly:make-moment 1 8)
> \set maxSubdivideInterval = #(ly:make-moment 1 16)
These values could be `\musicLength 8` and `\musicLength 16`.
Also, MR 2032 (merged hours ago) adds `musical-length?` and
On Jun 17, 2023, at 09:27, David Kastrup wrote:
>
>>
>> That sounds like it would make more sense to specify those values in the
>> form of a "duration log", like the first argument to a ly:make-duration
>> call.
>
> Or just use a duration in the first place. First iterations would
> likely
On Jun 16, 2023, at 19:13, Jason Yip wrote:
>
> minSubdivideInterval and maxSubdivideInterval. They are both Rationals. Their
> numerator and denominator must be a power of 2. For each power of 2
> (including negative powers of 2 of course) between those two values, the beam
> can be
On Jun 16, 2023, at 04:37, Jean Abou Samra wrote:
>
> I know that 2.25.6 was planned for this weekend. Unfortunately, due to
> https://gitlab.com/lilypond/lilypond/-/issues/6620 , current master is not
> going to work on Kubuntu and possibly other distros.
>
> I will try to find time this
On Jun 4, 2023, at 08:18, Werner LEMBERG wrote
Has anyone here ever used or seen the time-signature cancellation
sign shown in MR 2029, or anything like it?
https://gitlab.com/lilypond/lilypond/-/merge_requests/2029
>>>
>>> Never.
>>> Kieren.
>>
>> Now I'm starting to doubt that
On Jun 4, 2023, at 15:27, Flaming Hakama by Elaine
wrote:
>
> I guess I am kind of confused at the default behavior, why does lilypond
> not reprint a clef when you specify \clef ?
>
> Are people putting \clef commands in their code where they don't want a
> clef to appear?
> Is this a common
On Jun 4, 2023, at 07:53, Kieren MacMillan wrote:
>
> Hi Dan,
>
>> Has anyone here ever used or seen the time-signature cancellation sign shown
>> in MR 2029, or anything like it?
>> https://gitlab.com/lilypond/lilypond/-/merge_requests/2029
>
> Never.
> Kieren.
Now I'm starting to doubt
Has anyone here ever used or seen the time-signature cancellation sign shown in
MR 2029, or anything like it?
https://gitlab.com/lilypond/lilypond/-/merge_requests/2029
—
Dan
On Jun 3, 2023, at 04:09, Kevin Barry wrote:
>
> On Sat, 3 Jun 2023 at 06:06, Carl Sorensen wrote:
>
>>> I vote for adjusting the code so that it follows the documentation,
>>> probably by adding `forceTimeSignature` and `forceKeySignature`
>>> properties, both for orthogonality and a way to
About time signatures, the Notation Reference says briefly,
> Time signatures are printed at the beginning of a piece
> and whenever the time signature changes.
That is true, but incomplete: time signatures are also printed when the time
signature hasn't changed -- and it has been that way for
I was obliquely asked about my reaction to having another person assign an
issue to me.
The main practical effect of assigning an open issue is to deter others from
acting on it: a person interested in working on an issue ought to coordinate
with the current assignee before doing something
On May 18, 2023, at 08:47, Valentin Petzel wrote:
>
> Essentially it checks: Do we start at the begin of a measure, and if so, does
> or repeated music take exactly one or two measures?
I've dropped the user list from this thread.
I suggest looking at
On May 18, 2023, at 00:29, Werner LEMBERG wrote:
>
>
>>> The snippet 'Adding volta brackets to additional staves'
>>>
>>> https://lsr.di.unimi.it/LSR/Item?id=427
>>>
>>> doesn't seem to do what the description says. Honestly, I have no
>>> idea what this snippet actually wants to demonstrate
On May 17, 2023, at 14:04, Werner LEMBERG wrote:
>
> The snippet 'Adding volta brackets to additional staves'
>
> https://lsr.di.unimi.it/LSR/Item?id=427
>
> doesn't seem to do what the description says. Honestly, I have no
> idea what this snippet actually wants to demonstrate at all...
On May 10, 2023, at 16:19, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> Hi all,
>
> due to various constraints, I am kind of restricted when I will be able
> to do the next releases, so I thought I might as well let you know:
>
> LilyPond 2.25.5 will happen on the weekend
On May 5, 2023, at 06:14, Jean Abou Samra wrote:
>
> Le jeudi 04 mai 2023 à 22:51 -0400, Dan Eble a écrit :
>>
>>
>> I thought it would be nice to be able to draw a tick BarLine from a font
>> glyph in lieu of the default rounded rectangle. I have a working
I thought it would be nice to be able to draw a tick BarLine from a font glyph
in lieu of the default rounded rectangle. I have a working prototype that uses
a new property BarLine.tick-font-glyph-name to enable the behavior, but I need
some advice about font-size.
VaticanaStaff has \override
On Apr 23, 2023, at 05:22, Jean Abou Samra wrote:
>
>> {
>> \textLengthOn
>> s1-"loong"
>> \once \omit Staff.BarLine
>> \clef F
>> r1
>> }
>> with a starting spacer _and_ an omitted BarLine _and_ a clef change.
>>
>> 2.22. is ok, but output of 2.24. is bad.
>
>
> The MM
Everything I know about 16th-Century Italian I learned from 20th-Century
Spanish. I hope that someone here is able and willing to check my guesses
about this.
The following text seems to follow an introduction to mensural rests, and it
surrounds a figure of a single bar line and a double bar
On Apr 2, 2023, at 14:39, Kevin Barry wrote:
>
> On Sun, 2 Apr 2023 at 19:31, Jean Abou Samra wrote:
>> I can do
>>
>> (define-public grob-interpret-markup ly:grob-interpret-markup)
>>
>> like we already have for assoc-get aka ly:assoc-get, but it seems
>> clumsy.
>
> That is what I would
On Feb 5, 2023, at 09:28, Dan Eble wrote:
>
> 2. Attack this TODO in flower/include/real.hh.
>
>using std::abs; // TODO: replace abs (x) with std::abs (x) and remove this
https://gitlab.com/lilypond/lilypond/-/merge_requests/1834
—
Dan
Friends,
I don't have a Yosemite or El Capitan environment in which to validate changes.
There are two things I would try.
1. Does changing the few occurrences of `#include ` to `#include
` fix it? I don't know that it will, but it seems like less work than
2.
2. Attack this TODO in
On Jan 26, 2023, at 12:22, David Kastrup wrote:
>
>c'' x2
>
That looks a lot like "twice" to me.
—
Dan
On Jan 23, 2023, at 18:05, David Kastrup wrote:
>
> Dan Eble writes:
>
>> On Jan 23, 2023, at 10:11, David Kastrup wrote:
>>>
>>> I am not saying that 0 is the best choice here. It merely appears to be
>>> rather cheap. I thought of * and / but
On Jan 23, 2023, at 10:11, David Kastrup wrote:
>
> I am not saying that 0 is the best choice here. It merely appears to be
> rather cheap. I thought of * and / but the first renders sequences like
> c4*2 ambiguous and the second would at least become a mess in chord
> mode.
Can you clarify
On Jan 16, 2023, at 16:26, David Zelinsky wrote:
> Or try to make a merge request?
Welcome. This is the way.
—
Dan
Should slurs require Stem_engraver?
No: https://gitlab.com/lilypond/lilypond/-/issues/3760#note_339794300
Yes: https://gitlab.com/lilypond/lilypond/-/merge_requests/1800#note_1227831830
I'm looking for some input from old-timers to help decide this so I can avoid
wasting more time on broken or
On Dec 30, 2022, at 12:10, Thomas Morley wrote:
>
> Hi all,
>
> please have a look at:
>
> \version "2.25.0"
>
> {
> \override Score.BarNumber.break-visibility = ##(#f #t #t)
> % \set Score.alternativeNumberingStyle = #'whatever
> b1
> \repeat volta 2 { c' c' }
> \alternative { d' e' }
>
On Dec 3, 2022, at 08:48, Jean Abou Samra wrote:
>
> It rejects the \sectionLabel that comes at the same
> time as an implicit \codaMark.
>
> Should this be supported, or is there a reasoning that
> I am missing?
It's the same concern as from the beginning: I was reluctant to allow assigning
On Dec 3, 2022, at 10:25, Jean Abou Samra wrote:
>
> Le 03/12/2022 à 16:18, Dan Eble a écrit :
>> Printing "Coda" instead of a coda mark is the defining use case for
>> \sectionLabel.
>
> But judging from how \repeat segno uses it and from its break-vis
On Dec 3, 2022, at 08:48, Jean Abou Samra wrote:
>
> It rejects the \sectionLabel that comes at the same
> time as an implicit \codaMark.
Printing "Coda" instead of a coda mark is the defining use case for
\sectionLabel. I'll try to take a closer look at the example soon.
—
Dan
On Nov 26, 2022, at 17:43, Eric Benson wrote:
>
> ton of warnings, mostly of the form "implicit conversion changes
> signedness". These seem like the sort of thing that might not be too hard
> to fix.
https://gitlab.com/lilypond/lilypond/-/merge_requests/1744 fixes warnings other
than
On Nov 19, 2022, at 05:19, Werner LEMBERG wrote:
>
> Attached you can find an example that demonstrates (a), taken from the
> MR.
The sample LGTM. Beyond that, I prefer not to involve myself in the discussion.
—
Dan
On Nov 14, 2022, at 04:43, Paolo Prete wrote:
>
> I need to execute the following automated test:
> given a .ly file, I would like to check if the produced output is what I
> expect it to be.
For checking the impact of LilyPond changes on my own scores, I use a
Docker container and a bash
On Nov 12, 2022, at 09:07, Werner LEMBERG wrote:
>> 2. Release 2.23.81 without the fix and instead review it properly.
...
> Option 2 is fine with me.
+1
—
Dan
On Oct 22, 2022, at 09:16, Jean Abou Samra wrote:
>
> We have many issues related to ties and to slurs. Would anybody mind creating
> two GitLab labels ~"Ties" and ~"Slurs" for these? It would ease searching for
> defects in those specific areas.
I don't have a problem with your creating any
On Oct 7, 2022, at 13:51, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> On Thu, 2022-10-06 at 08:39 +0200, Jean Abou Samra wrote:
>> A factor that I was starting to forget in my enthusiasm for branching is
>> !1510 (source locations). Here I am guilty of taking forever to
On Oct 7, 2022, at 16:45, Jean Abou Samra wrote:
> Thus I wrote to the general GNU list server admins and proposed
> to step up for being an admin on these lists, just like I am
> already an admin on lilypond-user-fr (the French-speaking equivalent
> of lilypond-user, in case you didn't know).
>
> I'm only familiar with a subset of C++ up to C++03. Would my lack of
> knowledge of modern C++ exclude me from being a contributor?
No. Others will review your code and suggest using new features where it is
appropriate.
> I'm also not an expert on UB in C++, although I very much want to
On Aug 1, 2022, at 10:44, Lukas-Fabian Moser wrote:
>
> fwiw, I'm a bit confused about the GregorianTranscriptionStaff context - for
> example, in the typical liturgical situations where one uses a "modern" staff
> for notating Gregorian chant, one usually doesn't use stems.
I've been going
On Sep 6, 2022, at 12:46, Jean Abou Samra wrote:
>
> I would like to propose moving to clang-format as the canonical
> formatting tool and removing fixcc.py.
I don't care as long as the version is specified.
—
Dan
On Aug 9, 2022, at 10:07, Trevor wrote:
> In more modern hymn books there is a movement to use thin double lines
> throughout rather than commas to show how the lines of the verse map onto the
> music, although settings of traditional hymns usually retain the commas (see
> Common Praise).
On Sep 4, 2022, at 16:38, Jean Abou Samra wrote:
>
> it will create conflicts with everyone's WIP local branches
This is obviously unwelcome.
I would need to read a lot before I would have a hope of speaking competently
on this issue, and I'm very busy right now.
—
Dan
On Sep 4, 2022, at 18:23, Thomas Morley wrote:
>
>> The Contributor's Guide has sections on adding, editing, and renaming
>> snippets. What should I do when I want to stop using a snippet in the
>> Notation Reference?
>
> Well, short answer, adjust NR in
>
Harm,
The Contributor's Guide has sections on adding, editing, and renaming snippets.
What should I do when I want to stop using a snippet in the Notation
Reference? The one I have in mind now is "Inserting a caesura", though there
might have been one in the past that I removed from the
I am trying to document \caesura in the Notation Reference.
I have just made the docs starting from a clean build directory.
I see that CaesuraScript is highlighted differently than other grob names in
this text:
\override Score.Script.color = ...
\override
On Sep 1, 2022, at 14:54, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> Hi all,
>
> it's been 2 years now that development has moved to GitLab. In the very
> beginning, we agreed to keep existing branches on Savannah, but I'd
> like to revisit that decision and propose that
On Sep 2, 2022, at 04:42, Jean Abou Samra wrote:
>
> Does C++ provide tools for making this simpler? I'm thinking that something
> like
>
> LY_DEFINE (ly_grob_relative_coordinate, ..., (Grob *g, Grob *refp, Axis a),
> ...)
> {
> ...
> return ret;
> }
>
> would be equivalent to
>
>
I tried this:
@macro appendixBarLineDemo{BARTYPE}
@code{"\BARTYPE\"}
@lilypond[notime,relative=2]
\bar "\BARTYPE\" b4 \bar "\BARTYPE\" b4 \bar "\BARTYPE\"
@end lilypond
@end macro
but with \BARTYPE\ in the lilypond section, no staff appears in the PDF. I
guess I need
On Aug 14, 2022, at 06:59, Jean Abou Samra wrote:
>
> Le 14/08/2022 à 12:21, David Kastrup a écrit :
>> Jean Abou Samra writes:
>>
>>> We could also introduce a music function. I don't think
>>> tremoli are used frequently enough that having the most
>>> concise syntax for them is very
On Aug 14, 2022, at 04:03, Werner LEMBERG wrote:
>
>> Or maybe \textMark and \textEndMark? I'm not sure.
>
> I prefer `\textMark` over 'ad-hoc' or 'nonce'. As with Jean, I've
> never used the word 'nonce' before.
I also prefer \textMark. Then ad-hoc-mark-event can remain ad-hoc.
FYI,
On Aug 13, 2022, at 19:00, Jean Abou Samra wrote:
>
> I now have a patch locally that renames AdHocMarkEvent into
> LegacyAdHocMarkEvent
> (also ad-hoc-mark-event into legacy-ad-hoc-mark-event),
If I were less familiar with this stuff, I would probably be confused by
leaving "ad-hoc" in these
On Aug 10, 2022, at 18:01, Dan Eble wrote:
>
> On Aug 10, 2022, at 14:20, Jean Abou Samra wrote:
>>
>> \set Score.rehearsalMark =
>> \mark \default
...
> Remember the reasons that you preferred that \bar send an event rather than
> set a property? Maybe they
On Aug 10, 2022, at 14:20, Jean Abou Samra wrote:
>
> There is also \mark . I don't know if it's really that
> useful. If you need this, you can just as well do
>
> \set Score.rehearsalMark =
> \mark \default
I found that interface inconvenient enough not to imitate it in the coda and
On Aug 10, 2022, at 00:38, Werner LEMBERG wrote:
>
> Just imagine a piece (say, a waltz by Johann Strauss[*]) that has not
> a single segno, but a bunch of them. It might confuse an orchestra if
> the conductor asks to start 'at the segno' during a rehearsal – from
> experience I can tell you
On Aug 3, 2022, at 17:22, Jean Abou Samra wrote:
>
> \version "2.23.12"
>
> {
> c'1
> \mark \default
> \repeat segno 2 {
> c'1
> }
> }
>
>
> A power user on -user-fr is frustrated that the above
> doesn't work, as rehearsal-mark-event and segno-mark-event
> are mutually exclusive
On Aug 9, 2022, at 08:26, Kieren MacMillan wrote:
>
> Hi all,
>
> The big difference, in my mind — as composer, arranger, conductor, and
> performer — is that a caesura is generally longer than a comma/breath, and
> intentionally interrupts the flow of the overall line, whereas the
>
On Aug 9, 2022, at 02:31, Jean Abou Samra wrote:
>
> \new Staff {
> \alternative {
> \volta 2 c'1
> }
This unfolds better (but not well):
\alternative {
\volta 2 \new Staff ...
}
Conditional (folded/unfolded) context creation is something I
On Aug 9, 2022, at 07:40, Trevor wrote:
> A comma is the standard way of writing a breathing point in vocal music. It
> is used extensively in Hymns Ancient and Modern, New Standard. Gould writes
> on page 436 in the Vocal Music chapter: "When a note should be sung for its
> full duration,
Gilles,
I would like to learn the reason for using \breathe and \bar "||" in the
LilyPond snippet entitled "Hymn template" [1], Are they intended to
communicate two different things, or was it merely a stylistic decision to use
\bar "||" at the end of a system and \breathe in the middle?
"Hymn template"
https://lsr.di.unimi.it/LSR/Item?id=703
I don't see any way to find the author of a snippet. I'd like to ask the
author of this snippet about the reason for using \breathe and \bar "||". Are
they intended to communicate two different things, or was it merely a stylistic
On Jul 12, 2022, at 09:29, David Kastrup wrote:
>
>> Apparently, document-mod-list in document-context-mods.scm reads
>> an unbound variable.
>
> Well, yes.
>
> ((assign)
> (string-append
>(format #f "@item Sets translator property @code{~a} to" name-sym)
>(if
On Aug 5, 2022, at 22:35, Colin Campbell wrote:
> !1525 Divisio_engraver - Dan Eble
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1525
Those with an interest in ancient music, please take note. I don't want you
thinking of me next time you are singing Psalm 94.
—
Dan
On Aug 3, 2022, at 17:22, Jean Abou Samra wrote:
>
> \version "2.23.12"
>
> {
> c'1
> \mark \default
> \repeat segno 2 {
> c'1
> }
> }
>
> A power user on -user-fr is frustrated that the above
> doesn't work, as rehearsal-mark-event and segno-mark-event
> are mutually exclusive at
> On Aug 3, 2022, at 07:24, Jean Abou Samra wrote:
>
>
>
>> Le 3 août 2022 à 13:12, Dan Eble a écrit :
>>
>> On Aug 3, 2022, at 06:10, Jean Abou Samra wrote:
>>>
>>>> Le 3 août 2022 à 11:44, Werner LEMBERG a écrit :
>
On Aug 3, 2022, at 06:10, Jean Abou Samra wrote:
>
> Le 3 août 2022 à 11:44, Werner LEMBERG a écrit :
>>
>>
>> Two weeks ago Dan asked the following:
>>
Can you force them to face each other?
>>>
>>> I think so, yes, with some TeX trickery.
>>
[… it is possible …]
>
> Sorry for
GregorianTranscriptionStaff currently shows a time signature. Is that
desirable?
If it should be changed, feel free to list other things that should be changed.
—
Dan
On Jul 27, 2022, at 02:02, Jean Abou Samra wrote:
>
> Did you mean for rather than if, or is this syntax I am not aware of?
Yes, sorry.
—
Dan
On Jul 25, 2022, at 16:09, Jean Abou Samra wrote:
>
> Now, the next question. Suppose I just want to iterate over the list, nothing
> else. (This is actually the only case I have found myself in.) Suppose I get
> this list from an lvalue. The compiler won’t let me use ly_scm_list (lvalue).
>
On Jul 26, 2022, at 09:11, Walter Garcia-Fontes wrote:
>
> I checked, and the following packages are installed in my system:
>
> tex-gyre
> texlive-fonts-extra
> fonts-texgyre
>
> How can I get these missing fonts?
Walter,
I'm using
On Jul 24, 2022, at 19:04, Jean Abou Samra wrote:
>
> I understand that ly_scm_list takes an rvalue and disallows
> lvalues for clarity, while as_ly_scm_list takes an lvalue,
> and will fail on an rvalue by design, with the failure being
> a compilation failure since
On Jul 20, 2022, at 15:42, Colin Campbell wrote:
>
> It does, however, lead me to suggest to the developers that we go to a fixed
> schedule, with countdowns beginning on Monday, Wednesday and Friday every
> week, rather than the present, somewhat fluid, setup of every second day.
That works
On Jul 19, 2022, at 18:46, Jean Abou Samra wrote:
>
> Then we have the style of solution found in !1451, with per-engraver
> heuristics. I honestly dislike this. I don't want to sound harsh, but
"\fine does not end iteration"
https://gitlab.com/lilypond/lilypond/-/merge_requests/1496
—
Dan
On Jul 10, 2022, at 12:04, Jean Abou Samra wrote:
>
> The currently recommended syntax for DS al fine
> repeats is
>
> \repeat segno 2 {
> c'1 1 1 1
> \volta 2 \fine
> c'1 1 1 1
> }
>
> This seems to work just as well, though:
>
> \repeat segno 2 {
> c'1 1 1 1
> \volta 2 \fine
>
On Jul 18, 2022, at 09:49, Paulo Matos wrote:
>
> Anyway, let me take a look and see if I can make sense of it. Dan, are
> you the right person to bother if I have any further questions?
It is best to post questions to lilypond-devel so that everyone can participate
in answering and learning.
On Jul 18, 2022, at 01:46, Paulo Matos wrote:
>
> I feel therefore compelled to ask if there's any other suggestion about
> what I could look at. I am familiar with C++/Scheme code (although most
> of my Scheme is done in Racket, not Guile but that shouldn't be a
> blocker).
1 - 100 of 821 matches
Mail list logo
