Hi Thomas,
maybe this can be handy: the `moreutils` package has a utility called `ts`,
that will prepend a timestamp to each line of output.
If you pipe the output of your compilation into it, you can get timing
information quite easily, here's an example:
% ls | ts -s "%H:%M:%.S"
00:00:00.13
So... would anybody be able to lend a hand here please?
Many thanks
Luca
On Sat, Feb 12, 2022 at 7:49 PM Luca Fascione wrote:
> Hello,
> sorry for the double-post, I'm unsure whether this should go to -user or
> -devel.
>
> I'm looking for some guidance to set up fing
t necessarily looking
for a "simple" solution.
If the answer is: "it's a big change involving steps a to f", I'm happy to
have at it, under somebody's guidance.
Given that solving this problem is a need of mine, I feel it's completely
fine that it ends up b
e results. Somewhat like here.
>
> Valentin
>
> Am Sonntag, 20. Februar 2022, 21:17:31 CET schrieb Luca Fascione:
> > So... would anybody be able to lend a hand here please?
> >
> > Many thanks
> > Luca
> >
> > On Sat, Feb 12, 2022 at 7:49 PM Luca Fascione
gt; Am So., 20. Feb. 2022 um 22:41 Uhr schrieb Luca Fascione <
> l.fasci...@gmail.com>:
>
> > a) I'm looking for a way to get the fingerings where I want them without
> > using one-note-chord tricks
>
> Well, for Fingerings not in chord, like b-1 or -2-1 X-parent
&
e chord some note heads are
> on
> the other side of the Stem the alignment of something like -1-2-3
> would
> change (disregarding that it wouldn’t even be clear what note head to use).
>
> Cheers,
> Valentin
>
> Am Montag, 21. Februar 2022, 09:19:30 CET schrieb Luca Fa
the Beam (this does still get messed up by
> very
> slanted Beams, it might be useful to also get a reference to the Beam grob
> to
> factor in the angle of the Beam). With this we can estimate the free space
> between NoteHead and Beam, and depending on this space, shift the
> F
Looks lovely to me.
I notice the inline source is not highlighted, is that on purpose?
(say 2.1.7, page 23). A lot of other text I've seen seems to use the same
highlighting patterns for running code as well as display boxes of code,
esp given the fonts you picked are so regular in the weight, wou
b 21, 2022 at 5:42 PM Valentin Petzel wrote:
> No, not nescessarily. If we want all Fingerings on top or below there is
> no real benefit of doing the chord thing. In fact doing that leads to the
> exact same issue of the fingering for d being next to the other ones.
>
> Cheers,
>
t; rather confusing, as there is no monotonic relating between finger and
> pitch.
> As such I suppose guitar people would want to use fingerings with left or
> right
> orientations in chords anyway.
>
> Cheers,
> Valentin
>
> Am Montag, 21. Februar 2022, 17:47:58 CET schrieb L
lt
look consistent while making it clear what language is what.
(I've done a fair bit of LaTeX over the years)
Luca
On Mon, Feb 21, 2022 at 6:33 PM Jean Abou Samra wrote:
> Le 21/02/2022 à 17:42, Luca Fascione a écrit :
> > Looks lovely to me.
> >
> > I notice the inline
your other script
L
On Mon, 21 Feb 2022, 19:57 Jean Abou Samra, wrote:
> Le 21/02/2022 à 19:17, Luca Fascione a écrit :
> > I haven't worked wirh TexInfo markup before, however it occurs to me
> > that lisp is regular enough that with some effort one could hope to
> > sc
On Mon, Feb 21, 2022 at 9:01 PM Jean Abou Samra wrote:
> Are you aware of
>
> https://myrealbook.vintherine.org/
>
> ?
>
I was not, the material I was working from was the openbook project, by
Mark Veltzer.
He's done all the heavy work, I'm just working on how to build his stuff
and make it beau
On Mon, Feb 21, 2022 at 9:58 PM Jean Abou Samra wrote:
> Not sure what confuses you?
In TCL I got used to bare strings being values, not varnames, so I'm
learning stuff again.
It's just different, but in languages that in many other things are very
similar.
Of course I don't find it confusing i
Cool,
as I was saying, once I'm out of the swamp I'm in with these two things I'm
trying to get done,
I'll see if I can help you
L
On Tue, Feb 22, 2022 at 9:07 PM Werner LEMBERG wrote:
>
> > I haven't worked wirh TexInfo markup before, however it occurs to me
> > that lisp is regular enough tha
I expect this has been considered before,
but what is it that makes it unpalatable to have a step like initex for TeX
to build the .go files upon installation?
Wouldn't it solve the issue at hand?
(The portability would be addressed by the fact that it's the target
platform to build online,
and yo
or
after-line-break)?
Thanks again
Luca
On Mon, Feb 21, 2022 at 10:34 PM Jean Abou Samra wrote:
>
>
> Le 21/02/2022 à 22:19, Luca Fascione a écrit :
> >
> >
> > On Mon, Feb 21, 2022 at 9:58 PM Jean Abou Samra
> > wrote:
> >
> > Not sure what confus
In case it's useful, I'll share my impressions as a recent addition to this
group.
I have some experience with rolling out software, gathered in a different
field.
Where I come from we release often (I think we've averaged in the 30+ cuts
per year, roughly 2 every 3 weeks), and our users have tole
egressions" side, no?
> The one thing I want to get straight are the comments about Guile 3.0
> because that claim keeps coming up:
>
> Am Donnerstag, dem 24.02.2022 um 09:13 +0100 schrieb Luca Fascione:
> > [...] 3.0.x [...] seems to be benchmarking with speeds compa
Jean,
how many times did you run these tests?
Eyeballing your numbers it seems there's effectively no difference in
execution time opt/no-opt and 2.2/3.0.
Is the 5% a stable figure, or is it just a one-sample thing?
Would it be a passable inference that the reason the optimizer has
effectively no
On Sat, Feb 26, 2022 at 10:48 PM Jean Abou Samra wrote:
>
> [Jonas]
> > He, I always thought auto-compilation didn't optimize! 😕 now don't
> > tell me Guile also applies optimizations while just reading and
> > supposedly interpreting code...
>
> I don't think it does. At least, you don't usually
On Sun, Feb 27, 2022 at 12:13 PM Han-Wen Nienhuys wrote:
> On Sun, Feb 27, 2022 at 10:39 AM Luca Fascione
> wrote:
> > is it true that if you double the source size you double the compilation
> time?
>
> it should be, but we have rather complicated page breaking code th
"grep and in the source", it's all in "scm/". Vague pointers like that are hopefully all I'll need.
Many thanks,
Luca
On Mon, Feb 21, 2022 at 6:49 PM Luca Fascione wrote:
> Yes exactly, because of how our finger to note relation works, the
> enhancement in
you want
> to
> know what exact properties a grob has, you can look in define-grobs.scm.
> And
> similar stuff.
>
> And if you encounter something you really do not understand, ask the list.
> We’ve got some really marvellous people here who appear to know about
> everything yo
retired, and various threads on the internet
indicate folks are unable to reach him.
He seems to have done work in the 90's about garbage collection in
languages.
=
HTH
Luca
On Tue, Feb 22, 2022 at 10:08 PM Jean Abou Samra wrote:
> Le 22/02/2022 à 21:46, Luca Fascione a écrit :
&
t much :-)
I've tried various approaches to copying the dtls variable with (list-copy
dtls) and a couple things like that, but I wasn't able to
affect the final result at all.
Could anybody help me understand what's going on please?
Many thanks
Luca
On Sat, Mar 5, 2022 at 6:27 PM L
Hi Valentin,
thanks for the super prompt reply!
On Sun, Mar 6, 2022 at 5:34 PM Valentin Petzel wrote:
> So instead of doing the assoc-set! you might want to do something like
>
> (ly:grob-set-property! grob 'details `((beamed-lengths . ,stem-bmlgths)
> . ,detls))
>
For my edification, I'l
Yip!
https://www.cs.utexas.edu/ftp/garbage/submit/notready/schintro.ps
and
ftp://ftp.cs.utexas.edu/pub/garbage/cs345/schintro-v14/schintro_toc.html
But without ftp support in the browser this is annoying to read
Neither link feels like it would be around long term, and the rendering
is not great.
I was wondering how to do exactly this actually :-)
Thanks Werner!
L
On Mon, 7 Mar 2022, 08:06 Werner LEMBERG, wrote:
>
> > https://www.cs.utexas.edu/ftp/garbage/submit/notready/schintro.ps
> >
> > [...] and the rendering is not great.
>
> Attached you can find a PDF version of `schintro.ps` th
(and it looks _a lot_ better now)
L
On Mon, Mar 7, 2022 at 8:08 AM Luca Fascione wrote:
> I was wondering how to do exactly this actually :-)
> Thanks Werner!
>
> L
>
> On Mon, 7 Mar 2022, 08:06 Werner LEMBERG, wrote:
>
>>
>> > https://www.cs.utexas.edu/ftp
I've been asking myself questions about how to do this for a bit...
It seems to me most natural the TeX would be having the last word (if
you'll look after the lame pun there),
and thereby lilypond should indirect somewhat its internal sense of page
numbering, so that some negotiation
can happen w
Just wanted to say this is great
L
What if you rotate them instead?
Rename the current \partial \partialDuration,
convert.ly now is just s/partial/partialDuration/
and \partial always takes music from now on
It's the same as Werner said, but keeps the good name
L
On Sun, 20 Mar 2022, 08:24 Werner LEMBERG, wrote:
>
> > A con
What if instead of `\upbeat` (which is weirdly named when used in the
end-of-music/phrase/hymn/passage scenario) this new thing is just called
`\partialMusic`?
It's backward compatible, does something easy to use in some simple
scenarios, leaves everything else in place for more refined use cases,
This video shows Hans Kuehner at work
https://www.youtube.com/watch?v=BvyoKdW-Big
at 4m36 shows beams being engraved, he appears to keep the instrument
orthogonal to the line direction,
which makes Valentin's formula appropriate to capture this process.
(I love it when it goes "What happens when
Sorry, forgot to say: instead of correcting with 1/cos(\theta) I wonder if
correcting with 1/cos(\theta/2) would be an idea?
sl2 = sl / (1+sqrt(1+sl*sl)) // tan(\theta/2)
th *= sqrt(1+sl2*sl2)
HTH
L
On Fri, Mar 25, 2022 at 9:35 AM Luca Fascione wrote:
> This video shows Hans Kuehner at w
Yes but look at the took and how it's held in the hand: you won't ever get
a clean line from it holding is slanted to the direction of motion, that
thing is meant to be pushed straight ahead...
On Fri, 25 Mar 2022, 13:19 Dan Eble, wrote:
> On Mar 25, 2022, at 04:35, Luca Fa
... which is what Valentin also just said. Sorry Valentin for the double up!
L
On Fri, 25 Mar 2022, 13:43 Luca Fascione, wrote:
> Yes but look at the took and how it's held in the hand: you won't ever get
> a clean line from it holding is slanted to the direction of motion,
Carl,
If you look at the video I posted, could you explain how you see using that
instrument non along its tooling direction? (Like, "diagonally" wrt cutting
edge at the tip) seemd to me it would be very hard to get a straight line
doing so...
L
On Fri, 25 Mar 2022, 13:52 Carl Sorensen, wrote:
;\reverseMusic \foo
> >
> > rather than learning how to write the equivalent function in
> > Scheme. In other words, syntactic sugar keeps them from learning
> > Scheme as opposed to having to learn it.
> >
> > Am I missing something? Is my experience unique?
On Thu, Apr 21, 2022 at 8:12 AM Jean Abou Samra wrote:
> Le 21/04/2022 à 04:57, Dan Eble a écrit :
> > {
> >// dwc constructor calls scm_dynwind_begin ()
> >Dynwind_context dwc;
> >scm_dynwind_fluid (fluid1, value1);
> >scm_dynwind_fluid (fluid2, value2);
> >
y I loathe
this stateful stuff though)
L
On Thu, Apr 21, 2022 at 12:23 PM Dan Eble wrote:
> On Apr 21, 2022, at 02:55, Luca Fascione wrote:
> >
> > I'd think you can up this by one, and get a cleaner looking piece of code
> > if you implement scm_dynwind_fluid() as a
On Thu, Apr 21, 2022 at 11:46 PM Jean Abou Samra wrote:
> Well, the C++ and Scheme interfaces can feel different and idiomatic
> in their respective languages as long as they share the same
> underlying implementation.
>
I think this is a super important goal. In fact, I'd upgrade 'can' to
'shou
even if this requires effectively supporting barewords.
L
--
Luca Fascione
Distinguished Engineer - Ray Tracing - NVIDIA
Yes I underground that, I was meaning for person's mental parsers, it helps
that tokens (in an informal sense) always look the same
L
On Mon, 25 Apr 2022, 14:01 David Kastrup, wrote:
> Luca Fascione writes:
>
> > I think this is because it being an unquoted string (PE
*understood, of course
On Mon, 25 Apr 2022, 14:14 Luca Fascione, wrote:
> Yes I underground that, I was meaning for person's mental parsers, it
> helps that tokens (in an informal sense) always look the same
>
> L
>
> On Mon, 25 Apr 2022, 14:01 David Kastrup, wrote:
>
Fwiw, I like it, there's all sorts of weird edge cases in there that on
occasion are quite handy
L
On Sat, 7 May 2022, 11:45 Sebastiano Vigna,
wrote:
>
> > On 7 May 2022, at 09:30, Jean Abou Samra wrote:
> >
> > - What is the LSR's bus factor? As far as I can see, 1,
> > since while Sebastia
t; > Hi,
> >
> > After upgrading to Ubuntu 22.04 LTS, I can no longer use GDB
> > with LilyPond, although it runs fine outside of GDB.
> > [...]
>
>
> Thanks to private replies, I have learnt that this is apparently
> expected, and it works to type "continue" when this segfault
> appears.
>
>
>
--
Luca Fascione
On Wed, May 18, 2022 at 9:59 PM Jean Abou Samra wrote:
> Le 18/05/2022 à 13:54, Luca Fascione a écrit :
> >
> > Quoting from that page:
> > [...]
> > The collector will call abort if the signal
> > had another cause, and there was not other han
ng up the parameters to pass to configure I was
wondering what the recommended approach is to tell the current build system
to use (for example) /usr/local/Cellar/bison/3.8.2/bin/bison in lieu of
/usr/bin/bison
(I also need to repoint flex and maybe gettext, gettext is strange)
Thanks for you
wxr-xr-x 1 x x 25 Jan 16 18:18 /usr/local/opt/guile@2 ->
../Cellar/guile@2/2.2.7_1
lrwxr-xr-x 1 x x 21 Feb 27 18:37 /usr/local/opt/guile@3 ->
../Cellar/guile/3.0.8
)
Where is the testing/detection for Guile set up, roughly?
Thanks again,
L
--
Luca Fascione
On Fri, May 20, 2022 at 4:31 PM Jonas Hahnfeld wrote:
> On Thu, 2022-05-19 at 21:50 +0200, Luca Fascione wrote:
> > So I can rely on the build system capturing the resolved path to
> > bison during configure, like it would for CXX/CXXFLAGS?
>
> [...] you can set all-ca
in))
> >(forward-line (1- line))
> >(forward-char pos
> >
> >
> > (setq pdf-links-browse-uri-function
> 'lilypond-pdf-links-browse-uri-function)
> > 3. Open a lilypond generated pdf with \PointAndClickOn and click away.
> >
> > The code might need some refining but it does work here quite well.
> > Immanuel
>
>
> Hello,
>
> What kind of answer to this post do you await?
>
> Best,
> Jean
>
>
>
--
Luca Fascione
Maybe we could see if we can rope Immanuel to contribute a short segment to
the user docs?
L
On Sun, 22 May 2022, 14:17 Jean Abou Samra, wrote:
> Le 21/05/2022 à 22:38, Luca Fascione a écrit :
> > Jean, I think this is a BWV1079...
>
>
> :-)
>
> If the goal is to m
Samra, wrote:
> Le 21/05/2022 à 07:49, Luca Fascione a écrit :
> > I do follow the rationale for shipping one of the sets, what I'm
> > confused about is why _both_, they're the same font set, afaiu
> > (semantically, at least)
>
>
>
> Cf.
>
> commit 500
is an entirely different matter.
> >
> >
> > OK, but in that case, what is your request concretely?
> > Current LilyPond master works with Guile 3.0.
>
> That's essentially all. I wasn't sure of that from the discussion and
> from what I remembered from previous exchanges.
>
> > Do you want to add it to the CI?
>
> I am afraid that I am not tracking the development of Guile and the CI
> resources of LilyPond well enough to venture any opinion that would be
> more qualified than that of the current developers.
>
> --
> David Kastrup
>
>
--
Luca Fascione
erypockery would at least give us true current,
but we'd have to patch it, then again we'd be in a position where we _can_
patch it.
So at the cost of rocking the cage a bit hard, I came asking the
uncomfortable question:
what would happen if (for this unique circumstance) we'd do what one would
normally consider poor practice?
L
--
Luca Fascione
On Sun, May 22, 2022 at 9:05 PM Jonas Hahnfeld wrote:
> On Sun, 2022-05-22 at 20:14 +0200, Luca Fascione wrote:
> > So at the cost of rocking the cage a bit hard, I came asking the
> > uncomfortable question:
> > what would happen if (for this unique circumstance) we&#x
This also makes a lot of sense to me, yes.
L
On Mon, 23 May 2022, 13:12 Jean Abou Samra, wrote:
>
>
> Le 22/05/2022 à 21:52, Luca Fascione a écrit :
> >
> > On Sun, May 22, 2022 at 9:05 PM Jonas Hahnfeld wrote:
> >
> > On Sun, 2022-05-22 at 20:14 +0200,
this is not the first concern for developers, but it'd certainly be
annoying for maintainers
and CI, both of which I completely agree would be undesirable burdens.
Cheers,
L
--
Luca Fascione
t a follow-up MR.
>
> On Wed, May 25, 2022 at 12:01 AM Werner LEMBERG wrote:
> >
> >
> > Folks,
> >
> >
> > Jonas and I have an intense (and very exhausting) discussion where to
> > add kerning data. I want to hear more opinions whether I should go
> > 'route one' (which I prefer) or 'route two' (which Jonas prefers).
> >
> > Please have a look at MR 1368
> >
> > https://gitlab.com/lilypond/lilypond/-/merge_requests/1368
> >
> > and chime in.
> >
> >
> > Werner
> >
>
>
> --
> Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen
>
>
--
Luca Fascione
There! Thanks Aaron!
L
On Wed, 25 May 2022, 15:34 Aaron Hill, wrote:
> On 2022-05-25 1:31 am, Luca Fascione wrote:
> > (*) is there really no way to cross reference/link a commit comment
> > from
> > gitlab? gah.
>
> The post's relative time (e.g. "9 hours
so I had to download a Python
> > 3.10.4 from the Microsoft Store, onto a tablet running Win 10.
>
>
>
> Yes, the script requires the requests package, which
> is not part of the Python standard library. This
> should probably do:
>
> python -m pip install --user requests
>
> Jean
>
>
>
>
--
Luca Fascione
What do you mean Thomas? When the sheet clearly indicates DC al Fine (Da
Capo, from the beginning) why would it be normal to ignore such an explicit
direction?
I wasn't aware of \repeat segno, neat thing, I've always had to do it by
hand with cadenza trickeries...
L
On Sun, 29 May 2022, 10:45 Th
Oh yes. I was taught aaba as well, definitely.
Sorry, somehow I heard you were saying you'd read it aab, you see
L
On Sun, 29 May 2022, 13:33 Thomas Morley, wrote:
> Am So., 29. Mai 2022 um 13:25 Uhr schrieb Luca Fascione <
> l.fasci...@gmail.com>:
> >
> > What
not only do you want wrong code to
look wrong,
you also want code that does the same thing to look the same. And this is
entirely because
it makes it easier to read for humans, who are the ones that find the
difficult bugs.
Leaving it to the compiler to find bugs for you is table stakes, it'll only
find the easy stuff anyways.
That should be your assumed starting point, not your goal:
your goal is attending to the community that does what's hard, so that you
make it less hard.
HTH,
L
[1] https://www.joelonsoftware.com/2005/05/11/making-wrong-code-look-wrong
--
Luca Fascione
27;s on target to you?
Cheers
L
--
Luca Fascione
le as possible, it
seems it's good that decision are carefully analyzed, so we keep the thing
as a whole cleaner and easier to grow.
I won't hide that I enjoy discussing design matters in Computer Science :-)
L
--
Luca Fascione
mized
> to the point that thinking about it causes significant savings. The
> order of the most worthy optimizations is more high-level.
>
Yes, that'd be my expectation too.
I think we all agree that these are good things in
> any software projects. The question is whether a
&g
Sun, 5 Jun 2022, 16:42 David Kastrup, wrote:
> Luca Fascione writes:
>
> > On Sun, Jun 5, 2022 at 2:12 PM Jean Abou Samra
> wrote:
> >
> >> As David already said, the part of LilyPond we're discussing is using
> >> rationals. Furthermore, (a + b) + c
On Sun, 5 Jun 2022, 17:39 David Kastrup, wrote:
> Luca Fascione writes:
>
> > Oh yes absolutely, the growth is normally much slower than worse case
> > unless the addends come from really weird-ass distributions, no doubt.
> > Round to even helps a lot with that
> &
about the CI image?
>
>
> https://gitlab.com/lilypond/lilypond/-/blob/master/docker/base/Dockerfile.ubuntu-18.04
>
> The build passes with it everyday, so it’s guaranteed to work.
>
> Either you use Docker, or you look at the list of packages it installs and
> mimick it.
>
> Best,
> Jean
>
>
--
Luca Fascione
paths for your system
Cheers
L
On Wed, Jul 27, 2022 at 8:29 AM Luca Fascione wrote:
> Hi Walter,
> here's a couple more direct pointers for you:
>
> The TeX fonts (Gyre) will be in a place like
>
> .../texmf-dist/opentype/public/tex-gyre/texgyreschola-regular.otf
>
&g
Side thought: if your CPP code is complex, indenting it helps readability a
lot, here's a goofy example
#if CONDITION
# define AMACRO 6
# include "some/file.h"
#else
# if WIN32
#include "something/else.h"
# elif MACOSX
#include "the/darwin/version.h"
# endif
#endif
I haven't seen cla
Besides whereas Frescobaldi is a Lilypond editor (thereby requires is and
depends on it), Lilypond is not a Frescobaldi compiler, they're not
dependent in the other direction. So the Lilypond installer shouldn't know
about Frescobaldi
Further, a package with no GUI elements doesn't bump me at all.
I agree strongly with this, yes
On Tue, 18 Oct 2022, 18:14 Jean Abou Samra, wrote:
> Le 18/10/2022 à 08:12, Alex Harker a écrit :
> >
> >
> >> On 18 Oct 2022, at 00:05, Carl Sorensen
> >> wrote:
> >>
> >> IMO, what we most want is an app bundle that can be easily relocated
> >> anywhere and tha
13 by Ay B. Cee, and he hereby placed in the public domain".
Disclaimer: Although I have been part of extensive discussions on this
topic,
I am not a lawyer, and my words do not constitute legal advice.
L
--
Luca Fascione
y on the part of the project managers and owners to try and
insulate the contributors
from potential unpleasantness.
I repeat my disclaimer: Although I have been part of extensive discussions
on this topic,
I am not a lawyer, and my words do not constitute legal advice.
Luca
--
Luca Fascione
ble to
get one going, is it?
One thing that seems certain to me is that doing nothing guarantees there
will be no change.
L
--
Luca Fascione
Or you remove it, or you reimplement it
I think having GPL content in the lsr is the least desirable in the long
term, because either folks using it won't notice, or they might find
themselves unable or unwilling to use GPL as part of their content.
I'm not clear what it means to have GPL source
12:59 CEST, Luca Fascione a écrit :
> >
> >
> > Or you remove it, or you reimplement it
>
>
> Well yes.
>
>
> > I think having GPL content in the lsr is the least desirable in the long
> term, because either folks using it won't notice, or they migh
scussion at hand.
L
On Thu, Oct 20, 2022 at 1:56 PM Luca Fascione wrote:
> Hum. It seems to me this is greyer that what you say.
>
> gcc transforms program.c into a.out
>
> Your access to a.out gives you rights to access program.c
>
> s/gcc/lilypond/; s/program.c/score.ly/
On Thu, Oct 20, 2022 at 1:47 PM Jean Abou Samra wrote:
> > Le 20/10/2022 12:59 CEST, Luca Fascione a écrit :
> > I think having GPL content in the lsr is the least desirable in the long
> term, because either folks using it won't notice, or they might find
> themselves
On Fri, Oct 21, 2022 at 1:00 PM Jean Abou Samra wrote:
> Le 20/10/2022 à 15:46, Luca Fascione a écrit :
> > To be clear: the potential issue I see is when the score or some of
> > the headers it includes are GPL licensed, of course.
> > Now of course the boundary between
Note the detail that + a b c and eq? a b c don't do the exact same thing:
+ a b c is equivalent to (a + b) + c
eq? a b c is equivalent to (a == b) && (b == c)
The list form has short circuiting if I remember right (eq? bails out on
the first false it finds), but I don't remember how evaluation wo
Good to know thanks Jean!
L
>
Luatex is always available with modern tex distros (say at least 5 yrs
probably more). In fact pdftex _is_ luatex...
I feel texlive is a stable enough bet for people...
L
On Sat, 19 Nov 2022, 22:15 Jonas Hahnfeld via Discussions on LilyPond
development, wrote:
> On Sat, 2022-11-19 at 10:19 +00
eadily available in moderately recent TeX distribution.
Sorry for spreading misinformation
L
On Sun, Nov 20, 2022 at 6:28 AM Werner LEMBERG wrote:
>
> > Luatex is always available with modern tex distros (say at least 5
> > yrs probably more). In fact pdftex _is_ luatex...
>
> ??? Definitely not.
>
>
>
--
Luca Fascione
e and don't have to or don't want to deal
> with extensions like OpenType font handling, it often makes sense to
> replace `pdftex` with `xetex` or `luatex` since the latter two
> programs usually produce *much* smaller PDF files.
>
>
> Werner
>
>
--
Luca Fascione
On Mon, 21 Nov 2022, 13:34 Jean Abou Samra, wrote:
>
> build problems are fixed by developers, not users, sometimes very
> painfully, and using time that they could spend on other tasks.
>
If Werner's change breaks the build, surely he'll be the first one to argue
it's on him to fix it (possibl
Sorry, luatex is like 10yrs old, what's the need for xetex again? Maybe I
could justify pdftex (I really don't quite see it, but maybe) but xetex
seems just arbitrary... Or do you mean for a transition period?
What's the oldest system that this Lilypond would be used on? What's the
youngest texliv
On Mon, Nov 21, 2022 at 2:05 PM Jean Abou Samra wrote:
> > Le 21 nov. 2022 à 13:46, Luca Fascione a écrit :
> > Sorry, luatex is like 10yrs old, what's the need for xetex again?
> Are you asking this to me (judging from To:/Cc:)? I don’t see one.
>
No, I was aski
all* systems, even old ones based on the
> i386 chips. This means there is no useful answer, AFAICS.
>
Au contraire: it means you can ask anybody that builds our docs to upgrade
their tex distro to a new one,
and they'll have a working LuaTeX "no matter what system they use othrwise".
Which seems to me it's a very useful answer (it removes one constraint I
guess).
--
Luca Fascione
these people, impede their progress, make their planning
invalid
(possibly because we're not delivering to what we promised), we are
behaving poorly to them. I share that concern, and I think it's a very
ethically
sound concern to have, it's an important thing to worry about, I'd say.
I'd characterize it as a user-focused concern, no?
L
--
Luca Fascione
that at the time this regex is active,
> numbers are taken care of.
>
>
> Werner
>
>
--
Luca Fascione
It's not a validation, it's an anchor, it avoids it matching other numbers.
That's why the capture.
If pygments was better designed it'll let you do semi-context-sensitive
stuff like this, so you could say "numbers, but only if the follow a note
name" -> durations
L
On Fri, 25 Nov 2022, 17:52 Wer
I agree this would be a better regex, yes.
(You still have that double re: thing in the subject going on, Werner)
L
On Fri, 25 Nov 2022, 17:55 Werner LEMBERG, wrote:
> >> Note that at the time this regex is active, numbers are taken care
> >> of.
> >
> > Floats are, integers not.
>
> OK, but sh
On Fri, 25 Nov 2022, 18:11 Jean Abou Samra, wrote:
> What makes you think Pygments can’t do this? You can do
>
> (?<=\w+)\d+
>
Nothing but my not remembering lookaheads/lookbehinds, which I may argue
aren't very commom constructs. In fact aside from PERL I'm not even sure
what precedent they hav
Why the difference in value? Red is 10% off, green more like 30%?
What's up with that?
L
On Sat, 26 Nov 2022, 19:21 Werner LEMBERG, wrote:
>
> >>> lukas@Aquarium:~/git/lilypond/scm(master)$ git grep darkred
> >>> color.scm:(darkred 0.54509803921568623 0 0)
> >>> output-lib.scm:(define-publ
Indeed, you even had said before. Thanks Werner
L
On Sat, 26 Nov 2022, 21:55 Werner LEMBERG, wrote:
>
> > Why the difference in value? Red is 10% off, green more like 30%?
>
> Different standards (terminal colors vs. X11/CSS): identical names but
> different colours.
>
>
>Werner
>
1 - 100 of 174 matches
Mail list logo
