Hi,
I think that's too optimistic.
That's the gist; just some tiny corrections to make
sure Kieren knows what he will work on:
#686 certainly involves a bit of C++ programming (the command line is
evaluated in C++).
Not necessarily, options passed with -d and never
used in C++ are handled
Hi Kieren,
Am 06.11.21 um 20:58 schrieb Kieren MacMillan:
Hello all,
Now if what you want is really coding, there are
heaps of open issues waiting for you. Here are a
few that I believe (NB no warranty) would be feasible
for a power user with some minimal understanding of
Scheme:
https://gitla
Le 06/11/2021 à 20:58, Kieren MacMillan a écrit :
Hello all,
Now if what you want is really coding, there are
heaps of open issues waiting for you. Here are a
few that I believe (NB no warranty) would be feasible
for a power user with some minimal understanding of
Scheme:
https://gitlab.com/
Hello all,
> Now if what you want is really coding, there are
> heaps of open issues waiting for you. Here are a
> few that I believe (NB no warranty) would be feasible
> for a power user with some minimal understanding of
> Scheme:
> https://gitlab.com/lilypond/lilypond/-/issues/794
> https://git
Hi,
I also noticed that StaffCollection probably shouldn't have the
Vertical_align_engraver, since this causes vertical spacing to be
different. The original idea was that uncommenting in
\version "2.23.4"
bla = \repeat unfold 30 c'1
<<
\new Staff \bla
%{
\new StaffCollection \with {
Le 04/11/2021 à 21:18, Lukas-Fabian Moser a écrit :
Hi,
But I'm at a bit of a loss about your notion of a StaffMonoid. All
sorts of math puns aside (a CommutativeStaffRing of nonzero
characteristic especially for engraving _Le Spec de la Rose_ by
Berlioz) - what do you mean by a StaffMonoid?
Hi,
But I'm at a bit of a loss about your notion of a StaffMonoid. All
sorts of math puns aside (a CommutativeStaffRing of nonzero
characteristic especially for engraving _Le Spec de la Rose_ by
Berlioz) - what do you mean by a StaffMonoid?
There is absolutely nothing besides the math pun. It
Le 03/11/2021 à 22:16, Lukas-Fabian Moser a écrit :
Hi,
Well, I would say it depends on what you intend to
do. Help out in implementing this particular feature?
The StaffCollection ancestor to StaffGroup might be
a good first contribution. For completeness you could
also add the intermediate ty
Hi,
Well, I would say it depends on what you intend to
do. Help out in implementing this particular feature?
The StaffCollection ancestor to StaffGroup might be
a good first contribution. For completeness you could
also add the intermediate type StaffMonoid.
I already have this ready in a bran
Le 03/11/2021 à 14:40, Kieren MacMillan a écrit :
2. I’m hoping to increase my Lilypond pay grade in the [very] near future, so
if there’s any way I can roll up my sleeves and get involved with actual
coding, please let me know.
Well, I would say it depends on what you intend to
do. Help out
Hi all,
This is already above my pay grade! =)
That being said…
1. I’m available for whatever testing and brainstorming would benefit from my
participation.
2. I’m hoping to increase my Lilypond pay grade in the [very] near future, so
if there’s any way I can roll up my sleeves and get invol
Some random brainstorming thoughts…
Le 02/11/2021 à 22:50, Lukas-Fabian Moser a écrit :
[…]
- I'm not sure if "staff-group names with brackets" should be done as
a new Layout object / by a new engraver, or if this should be added to
the functionality of InstrumentName and the Instrument_name_
Nice! This definitely solves the basic problem nicely.
Lukas sent me [off-list] a totally different solution that was also
excellent.
Maybe we can/should discuss the pros and cons of each approach — and
others, if they’re offered — with an eye to eventually submitting a
patch…?
I don't
Am Di., 2. Nov. 2021 um 03:43 Uhr schrieb Adam M. Griggs
:
>
> Hello,
>
> This topic is of particular interest to me. Using the proof-of-concept code
> Thomas Morley provided, I've arrived at the attached pdf. The results aren't
> quite what I'm aiming for, but it's close.
>
> Some features I'd l
Le 01/11/2021 à 21:41, Kieren MacMillan a écrit :
Hi Harm,
attached code hacks Instrument.Y-offset.
This is a proof of concept, please test thoroughly before using it in serious
work.
Nice! This definitely solves the basic problem nicely.
Lukas sent me [off-list] a totally different solution
Hi Harm,
> attached code hacks Instrument.Y-offset.
> This is a proof of concept, please test thoroughly before using it in serious
> work.
Nice! This definitely solves the basic problem nicely.
Lukas sent me [off-list] a totally different solution that was also excellent.
Maybe we can/should
Hi Kieren,
This should be very well doable with an engraver, similar to the engraver for
group delimiters. Optimally this should integrate with the Instrument name
engraver, so that the instrument name can behave differently depending on
whether the group name is present (e.g. a group KLARINETT
Am Mo., 1. Nov. 2021 um 15:35 Uhr schrieb Kieren MacMillan
:
>
> Hi all,
>
> Having struggled with this for almost a decade (see, e.g.,
> https://lists.gnu.org/archive/html/lilypond-user/2013-03/msg00314.html)… Is
> this something that could be handled really well with an engraver? Or at
> least
Hi all,
Having struggled with this for almost a decade (see, e.g.,
https://lists.gnu.org/archive/html/lilypond-user/2013-03/msg00314.html)… Is
this something that could be handled really well with an engraver? Or at least
a bunch of helpful syntactic sugar? Surely all of this manual work (offse
Hello josh,
To get that you need to draw your postscript code centered, so instead of
going from Y=0 to Y=-height go from Y=height/2 to Y=-height/2.
But the problem is not really getting the bracket, it is getting the height.
Cheers,
Valentin
Am Sonntag, 31. Oktober 2021, 21:51:08 CET schrieb
I was able to use a combination of approaches with one last hurdle and I
am still completely lost when it comes to this facet of Lilypond.
I have used the following input to create the bracket in the attached
image.
#(define-markup-command (openBracket layout props heitgh) (number?)
(interp
Hi all,
> I don’t know of a good way to get this
There are a whole bunch of ways to clothe that particular cat… Here’s one:
%%% SNIPPET BEGINS %%%
\version "2.22.1"
\paper { indent = 1\in }
\layout {
\context {
\Score
\override InstrumentName.self-alignment-X = #RIGHT
Hello Josh,
I don’t know of a good way to get this, but it might be worth a specific
engraver. We might have some sort of instrument group name engraver that
properly handles such stuff. Maybe.
Cheers,
Valentin
Am Freitag, 29. Oktober 2021, 14:58:36 CEST schrieb josh:
> Hello. I have been tryi
23 matches
Mail list logo
