> (CC to Kevin Barry, who mentioned GitLab experience in a separate
> thread. My info here is more based on research than experience, so
> please call out any misunderstandings I have.)
Thank you for the CC. I have read through the messages, and the previous
discussion from 2018.
My
On Fri, Feb 07, 2020 at 01:21:35PM +0100, Han-Wen Nienhuys wrote:
> Proposal: rather than using the patchy scripts for validating
> LilyPond, we use docker images.
Without getting into technical details, I think this is a really good
idea. Automatic building/testing saves lots of time, and having a
"no space left on device"
Is that a full disk or something?
On Sun, Feb 9, 2020, 13:10 wrote:
> Hello,
>
> ..
>
> Making lily/out/metronome-engraver.o < cc
> Making lily/out/warn-scheme.o < cc
> Making lily/out/lexer.o < cc
> Making lily/out/parser.o < cc
> ./out/parser.cc: In function 'int yypa
>
>
> Would docker give us this 'proverbial canary' or would it turn into
> 'worksforme' when someone tried to build their own version of LP on a
> vanilla base of Linux?
>
Docker would eliminate 'worksforme' type issues yes.
>
On Thu, 12 Mar 2020 at 12:48, wrote:
> I'll defer you to Jonas' reply to this thread just after yours.
>
> I'm all for conistent build envs but at least make sure your testing is
> actually ... err testing what it should be testing.
>
> Containers don't protect against that.
A docker container i
>
>
> Frankly, I am more sympathetic to "worksforme" discussions among
> developers than telling users "worksforme". Where is the point in being
> able to tell users that no developer will reproduce their problem?
>
> I'd rather have an error popping up for at least some developers than
> for none
>
>
> I say that having a developer monoculture doesn't buy as anything since
> we still need to provide for a multitude of users.
>
We are talking about testing builds right? If a user gets as far as "I need
to test changes I made to the source code" then surely it would be better
to have somethi
>
>
> The direction of this statement is correct, but the magnitude is not. The
> kernel is still provided by the host. Getting a crash report can be
> frustrating when the guest's behavior hinges on /proc features that the
> host OS has configured appropriately for the host, not the guest.
> Co
On Wed, 25 Mar 2020 at 20:06, David Nalesnik wrote:
>
> I'm getting some spurious characters at
> http://lilypond.org/manuals.html. Screenshot attached.
looks python2 vs python3 related: b'' is how python3 prints byte
strings (which were the default string type in python2, but not in
python3).
Hi David,
Although you have changed the subject to "Resolving standoffs" your
email reads like an attempt to force a resolution - in your favour -
of one *particular* standoff. It seems to be more of a protest than an
attempt to elicit discussion.
I am both a lurker and not capable of understandi
As there is no routine for determining skylines for utf-8-string
stencils, they normally fall back to the grob's bounding box, which is
fine. However, when there is a mixture of utf-8-string and other types
of stencil (which have associated skyline functions) in a single grob,
the entire grob gets
On Fri, Apr 24, 2020 at 09:18:10PM +0200, Han-Wen Nienhuys wrote:
> Can you add a regression test that shows the problem?
Yes. I'll go read the docs to see how to do that and do one up (but feel
free to point me in the right direction...)
Kevin
On Fri, Apr 24, 2020 at 09:25:19PM +0200, Han-Wen Nienhuys wrote:
> Just add a test file under input/regression/ , following the style of
> other files there.
Thanks for the pointer. The only other svg backend file there looks like
it has been deliberately disabled, so apologies if I have done thi
As there is no routine for determining skylines for utf-8-string
stencils, they normally fall back to the grob's bounding box, which is
fine. However, when there is a mixture of utf-8-string and other types
of stencil (which have associated skyline functions) in a single grob,
the entire grob gets
Patch is attached to this mail as a file if that is more convenient.
Kevin
>From 1c5715ad52139aab936ee7dffb2cdef3d123b369 Mon Sep 17 00:00:00 2001
From: Kevin Barry
Date: Fri, 24 Apr 2020 19:26:26 +0100
Subject: [PATCH v1] Issue 3778: Use bounding box as skylines for markup in svg
backend
Hi James,
Thank you for responding.
On Mon, Apr 27, 2020 at 11:09:50AM +0100, James wrote:
> Is this patch read for full testing or is it work-in-progress you just want
> someone to comment on it?
It's not work in progress no - unless someone has objections or
observations, but I don't mean to c
Hi James,
> We do have a process, see:
> http://lilypond.org/doc/v2.19/Documentation/contributor-big-page#summary-for-experienced-developers
I have followed this as best I can, but it seems I need to have write
access to the issue tracker before I can send patches. If that is the
case then can s
Hi Jonas,
> Done (hopefully).
Thank you very much; it looks like it worked!
Kevin
On Sat, May 02, 2020 at 12:25:15AM -0700, hanw...@gmail.com wrote:
> please don't submit; I'm rearranging this file completely.
>
> Can you add your regression test + instructions on how to reproduce the
> problem?
I did add a regression test in the first patch set, but it breaks
testing. It seem
On Sat, May 02, 2020 at 01:16:30AM -0700, beauleetien...@gmail.com wrote:
> On 2020/05/02 07:38:58, hanwenn wrote:
> > I don't completely understand, though: if we put the "utf-8-string"
> directly
> > into the SVG output, the SVG browser might make other font choices,
> making the
> > outline pote
On Sat, May 02, 2020 at 09:59:18AM +0200, Han-Wen Nienhuys wrote:
> Not necessarily, but the refactoring means I'll likely have to
> overwrite the fix wholesale. Because there is no regtest, it willl
> depend on my diligence anyway to fix this again.
OK, so what should we do? I am happy to take re
1.0 --export-background=white
> --export-type="png" svg.cropped.svg
>
> and then do imagemagick diffs on the result.
>
> On Sat, May 2, 2020 at 10:53 AM Kevin Barry wrote:
> >
> > On Sat, May 02, 2020 at 09:59:18AM +0200, Han-Wen Nienhuys wrote:
> > > No
Hi Valentin
On Sun, May 10, 2020 at 10:13:04AM +0200, Valentin Villenave wrote:
> Greetings,
>
> could anyone give me a hint as to where dynamics alignment is handled?
> As far as I can see, the self-alignment-interface functions are not
> used by the (formerly new) dynamic-engraver; and AFAICS t
Hi Federico,
Thank you for the instructions. I will try to help get them done as
well.
On Tue, May 12, 2020 at 12:28:24AM +0200, Federico Bruni wrote:
> In the last comment you should find a commit id (if it's missing you'll have
> to search it).
> The easiest and quickest way to verify that a ce
On Fri, May 15, 2020 at 04:25:52PM +0200, Jonas Hahnfeld wrote:
> That the script is doing exactly what I told it to do: The diff between
> the previous and the rebased commit is not empty. Therefore it adds the
> Patch::new label, removing Patch::push.
Shouldn't `diff staging...HEAD` be the same
On Sun, May 17, 2020 at 10:08:12AM +0200, Urs Liska wrote:
> Do I understand you correctly that README.txt is generated upon
> compiling LilyPond? So where does it end up, I couldn't find a
> README.txt neither in the source repository nor in the installation
> directory. Does it only end up in the
On Mon, May 18, 2020 at 10:48:55AM +0100, James Lowe wrote:
> but how do I know? That is the nub of what I am asking. If a patch is 'new'
> how do I know that an automated make doc is 'in progress, has completed with
> errors, has completed without errors' as I am not going to bother to do any
> wo
On Mon, May 18, 2020 at 12:17:53PM +0200, Urs Liska wrote:
> No, at least not at the time I looked.
> What James needs is additionally an icon that states that MR is
> *currently* being tested.
There is an icon for that (it's blue and looks like a half-filled pie
chart) - I just couldn't find a me
On Mon, May 18, 2020 at 11:29:35AM +0100, James Lowe wrote:
> Countdown.py (which is Jonas' great cli tool) it's what you see when I do
> the countdown (that's literally cut/paste).
I haven't seen that script, but the gitlab API exposes pipeline
information. It should be enough to correlate a merg
The fast-forward rebase has two advantages that I can think of:
- the git history is cleaner/easier to parse
- it prevents the situation that sometimes arises where a couple of
patches - that pass testing independently, but will break when
combined - from making it into master (and breaking it)
> Again, I hope I am not unpleasant and polemic
In my opinion, you are being both. If your goal was genuinely to
encourage improvements in LilyPond, then I hope it's clear from the
response that you are going about it in a poor way. Acting like it's
obvious that LilyPond's default font is badly de
Hi Developers,
I'm struggling with trying to fix these two issues so I'm asking for
help from someone with a better knowledge of LilyPond internals.
I have spent a couple of weeks looking at the code and trying different
solutions (in both C++ and Scheme), so I think I have some understanding
of
> By the way, do you agree that this is a bug in LilyPond?
Gould suggests it is: the example on page 143 in my edition of Behind
Bars, from a Bartok string quartet, shows only the glissando lines that
run into an accidental getting shortened (in fact, when there are enough
accidentals that there a
Hi Dan,
Thank you for responding.
> If this problem involves a twisty maze of callbacks and pure-impure
> properties, it's unlikely that anyone's knowledge reaches the level of
> expertise you're hoping for.
That is a pretty accurate description of it: there are about 50 stack
frames between whe
> OK, thanks. Reducing the size of the accent glyph (both vertically
> and horizontally) is a rather trivial change in Emmentaler, and I
> could submit an MR. However, it might have a large impact on
> formatting older documents. Is this something we should be concerned?
> Given that we adjust g
> I concur with the idea that a properly functioning full conversion to
> Python 3 and workable (though not required) Guile 2 constitutes sufficient
> change for the next stable version. No other features are needed.
I agree with this.
Kevin
On Sat, 26 Sep 2020 at 19:30, Hans Åberg wrote:
> The notes d♯ to e♭ have different pitches in the staff notation
> system, which cannot express E12 enharmonic equivalents, so this
> is slur. So it should be a slur that looks like slur.
> >
> > I disagree. For all practical purpose
> Both cases were discussed. For an orchestra they are not the same pitch, thus
> formally a slur.
You cannot make this assumption. It is exceptional to distinguish D
sharp and E flat since most performed orchestral music is equally
tempered. It is common, for example, for a composer to write D s
On Sun, Nov 15, 2020 at 11:02:52AM +, Kevin Barry wrote:
> - if you have a preference for one of the four, please indicate which
I will be the first responder and say that, of the options in the pdf, I
think Gould is the most appropriate.
Kevin
On Sun, Nov 15, 2020 at 07:07:03AM -0600, David Nalesnik wrote:
> Another vote for Gould. (Though does she have anything to say about
> the normally unshown measure numbers which are stranded beyond the
> line here?)
Those are included in the examples purely for the sake of completeness.
Gould ha
On Sun, Nov 15, 2020 at 01:37:34PM +, Graham King wrote:
> I think Gould's positioning looks _slightly_ better, except at
> line-beginnings where I definitely prefer lilypond's. Moreover, the
> position immediately after a bar line is heavily-contested
> real-estate, as your examples make clea
Hi Federico,
I don't know anything about this part of the code, but the relevant errors
from the doc build pipeline seem to be:
no such file: search-box.ihtml: No such file or directory at
/builds/lilypond/lilypond/Documentation/lilypond-texi2html.init line
836.
/builds/lilypond/lilypond/build/../
On Wed, Mar 17, 2021 at 08:10:08PM +0100, Jonas Hahnfeld wrote:
> In the longer term, I think it could make sense to hold a "bug bash
> weekend" and try to pick some low-hanging fruits. That would not be
> limited to developers to write patches, but everybody to try and
> reproduce old reports with
On Sun, Apr 11, 2021 at 08:11:37PM +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> So, that was the main question of the message (sorry if that got hidden
> in the lengthy text and many numbers): What is "reasonable"? I think
> the numbers I showed are reasonable, but that's
Hi Tim,
I wish I could volunteer for this, but I have a full-time job, and I'm
not really knowledgable enough to do it without help. But I will help if
I can.
Han-wen opined on the merge request he opened for this issue last year
that we would probably have to replace our current pdf rendering sy
Do Debian package LilyPond for aarch64? If they do, their build
scripts are probably available somewhere.
On Thu, 20 May 2021 at 07:26, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
>
> Am Mittwoch, dem 19.05.2021 um 22:54 +0200 schrieb Federico Bruni:
> > On Thu, May 13 2021 at 2
Hi James,
I'm pretty sure that I managed this, but I may not have gone as far as
a full doc build, but I think I managed install-info. I will try to
make time to verify and get back to you.
Kevin
On Wed, 9 Jun 2021 at 07:37, James wrote:
>
> Hello,
>
> Has anyone on this list recently (within t
: error: file not found: version.itexi
I'm running Ubuntu 20.04 on WSL 2. My normal Linux system doesn't have
the same problem.
Kevin
On Wed, 9 Jun 2021 at 10:49, Kevin Barry wrote:
>
> Hi James,
>
> I'm pretty sure that I managed this, but I may not have gone as
week, maybe try an earlier version of Ubuntu if
> > such a thing exists on MS marketplace these days.
> >
> > James
> >
> >
> >
> >>
> >>
> >> On Wed, 9 Jun 2021 at 10:49, Kevin Barry wrote:
> >>> Hi James,
> >&g
> > I resorted to using WSL out of desperation on a system where I can't
> > get the wifi to work on Linux. I was able to develop on LilyPond more
> > or less unhindered (until I checked again recently). If you have a
> > Linux system there's no reason to use WSL (IMO).
>
> Quite.
The final irony
> I'd be grateful if someone could merge this one (on a phone, and GitLab seems
> to heavy for it...).
>
> Thanks,
> Jean
Done
These changes/improvements are exciting. Thank you and Knut for the hard work!
> > I would say that this step requires going to LilyPond 3.0, along with
> > removing all the features and commands that cannot be implemented in
> > the Cairo backend, or that we don't want to.
>
> We can discuss this
> This use case continues to be supported with
> Cairo. Just convert \postscript to \path, wich
> works both in the current PS backend and with Cairo.
Is this something that can be done automatically with convert-ly? If
not then does it justify a major version bump?
Kevin
On Mon, Jan 20, 2020 at 10:05:23PM +, Carl Sorensen wrote:
>
> Wouldn't it be much more simple to build lilypond as a Docker application?
>
> I don't know anything about building lilypond as a Docker application. If it
> were possible to execute a docker application from the command
The minimum length of the stem of the middle note is forcing the beams down.
On Sat, Jan 25, 2020 at 09:27:07AM +0100, Thomas Morley wrote:
> Am Sa., 25. Jan. 2020 um 08:58 Uhr schrieb Kevin Barry :
> >
> > The minimum length of the stem of the middle note is forcing the beams down.
>
> Not here. It's more the relevant value of
> beamed-extr
I don't know if lurkers' opinions count, but on the subject of potential
replacements for Savannah/Sourceforge: I am part of a team that administer
both Gerrit and Gitlab in-house deployments. If choosing between them I
would advocate for Gitlab because it includes issue tracking and CI/CD so
perha
Hi James,
This is a big loss; you will be missed. Thank you for all of your hard work.
> I want to stay a
> developer and that conflicts both time-wise and with respect to
> impartiality.
Finding a non-developer to fill James's shoes sounds difficult. I
would volunteer, but I still plan to contr
On Wed, 25 May 2022 at 07:38, Han-Wen Nienhuys wrote:
> > I equally object to any contribution being merged "because the author
> knows what he's doing".
>
> I object to reviewers blocking contributions just because they have a
> strong opinion on how things should be done. In this case, Jonas ha
> Also technically I cannot "block contributions", nobody in the
> community has the power to do so.
>
This might be true technically, but in practice your objections are usually
enough.
Hi all,
I used to have a style file for creating musical examples (typically, for
printed books and the like) that handily produced cropped images by setting
the backend to eps (and removing margins and headers and footers). I
noticed that this has stopped working in latest master and I am unable
Thank you that definitely looks related! I have posted a comment there.
On Mon, 15 Aug 2022 at 21:35, Jean Abou Samra wrote:
> Le 15/08/2022 à 18:12, Kevin Barry a écrit :
> > Hi all,
> >
> > I used to have a style file for creating musical examples (typically, for
>
behaviour.
I'm not sure if it should be socialised or not. The previous way of
doing it didn't make any more sense.
Kevin
On Wed, 17 Aug 2022 at 17:14, Kevin Barry wrote:
>
> Thank you that definitely looks related! I have posted a comment there.
>
> On Mon, 15 Aug 2022 at
I have no issues when I Google it. Did you search for tlasm or t1asm?
Kevin
On Wed 7 Sept 2022, 09:51 Andrew Bernard,
wrote:
> 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 somebod
> In the last discussion on this topic in
> https://lists.gnu.org/archive/html/lilypond-devel/2022-09/msg00070.html
> the rare crashes on Windows were identified as a blocker. These seem to
> be fixed now, at least for reasonable user scores (we can still trigger
> it when running the garbage colle
On Wed, Oct 05, 2022 at 03:40:03PM +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> > Silence means consent.
>
> How can you consent to a question, whether to branch or not? This
> time I even explicitly asked for thoughts. A (stable) release should
> be a team effort, that
On Mon, Oct 10, 2022 at 11:08:57PM +0200, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> Hi all,
>
> Yes, I'm trying to slightly shorten the timeline to three weeks between
> the release candidates in an attempt to get a release before the end of
> the year. We will see how this
Hi Federico,
On Thu, Oct 13, 2022 at 01:06:17AM +0200, Federico Bruni wrote:
> Hi folks
>
> I've recently used convert-ly to update my private music sheet library and
> test version 2.23.14 (official binaries).
> Two files are failing with the same error message:
Did this work with 2.23.13? Or w
> I tried 2.23.12 and I got the same error.
Do you remember what version it last worked with?
> It works great using the cairo backend!
> I wanted to test it so I think I'll set it as default for all my scores.
> What are the current drawbacks? There's any page in the docs about cairo?
It looks
On Thu, Oct 20, 2022 at 02:32:58AM +0200, Jean Abou Samra wrote:
> What should we do about these snippets? Delete them?
My two cents is that we should leave it alone and not spend time talking
about licences because those discussions rarely arrive at answers, and
most of the time there isn't reall
On Fri, Oct 21, 2022 at 01:12:09PM +0200, Jean Abou Samra wrote:
> -- AFAIK, this is the first time we have to do a relicensing,
> and the odds of a legal case involving LilyPond are very small
> due to its low-key profile in the industry. I feel this would
> be much ado about nothing.
This is why
On Fri, Oct 21, 2022 at 01:27:07PM +0200, Jean Abou Samra wrote:
> It would have helped IMO if all the more or less unrelated side
> questions had been raised in separate threads…
Well yes, but it's totally unavoidable any time licencing comes up for
discussion. The subject itself seems to be a ma
On Tue, Nov 15, 2022 at 02:49:55PM +0100, Jean Abou Samra wrote:
> Le 15/11/2022 à 14:43, David Kastrup a écrit :
> > If it's "mundane", why would the conversion result in a complex
> > replacement?
>
> Have you looked at the replacement?
>
> It is
>
> (lambda* (m #:optional headers)
> (if hea
On Fri, Nov 18, 2022 at 11:06:45AM +0100, Jean Abou Samra wrote:
> Hi,
>
> What should we do? Do we accept releasing 2.24 from
> the release-8_2 branch in BDWGC even though it is not
> released? Do we keep the current workaround, which still
> gives some crashes? Do we replace our workaround
> wit
On Mon, Nov 21, 2022 at 12:03:34PM +0100, Luca Fascione wrote:
> I must say I don't understand this discussion.
I agree with most of what Luca said.
I'm sure whatever the maintenance burden is, Werner is likely to bear it
himself. Supporting newer versions of tools may even help (cf. texi2html
an
On Thu, Nov 24, 2022 at 03:37:43AM +0100, Jean Abou Samra wrote:
> Had anyone seen this??
No, but it's not surprising: Guile sometimes seems to be a one-person
hobby project. It's not a project that cares much about breaking things
for its users.
> https://github.com/wingo/whippet-gc
>
> This lo
On Thu, Nov 24, 2022 at 12:26:57PM +0100, Jean Abou Samra wrote:
> Le 24/11/2022 à 12:12, Kevin Barry a écrit :
>
> GC is definitely not the kind of thing where "passes the
> regtests" means there is no problem. As we have seen in the
> past, the most infuriating a
On Thu, Nov 24, 2022 at 02:58:16PM +0100, Jean Abou Samra wrote:
> What would be the difference with 'make doc'?
I was referring to the kind of scores used to test/reproduce the
heisenbug we had on Windows, i.e. designed to trigger GC-related
problems. Would it be worth saving some scores like tha
On Tue, Dec 13, 2022 at 10:44:26PM +0100, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
> I also realized that I forgot to send a draft release announcement
> text, which I originally wanted to share during the weekend. I went
> with the standard text, copying from the previous sta
> My conclusion is that PDF is the more "logical"
> successor to the inclusion of EPS.)
I'm not on the user list anymore so I didn't see the poll. Personally
I mostly work with EPS (for at least one publisher that I worked with
it was the only acceptable vector format), but I'm glad that we polled
On Sun, 5 Feb 2023 at 13:09, Jonas Hahnfeld via Discussions on
LilyPond development wrote:
>
> Any workaround we introduce will have to be removed at some point.
> When? 5 years after the last system goes EOL sounds like a reasonable
> time, don't you think? So yes, in my opinion "must not".
Work
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 do.
Kevin
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 retain backward
> > compatibility.
> >
>
> I vote for
Dear Lilypond developers,
I read in the contributor's guide that there is a system of mentorship for
people who would like to help the project. Is that still the case? And if
so how do I get involved in it.
Kevin
___
lilypond-devel mailing list
lilypond
> It depends on which part of LilyPond you want to help with as to the
> availability of people to help you. Is there a particular skill-set, set
> of issues or area of LilyPond you are particularly interested in?
Thank you for responding. I would like to be able to contribute code to the
project
>
> Can someone point to a well engraved example (Bärenreiter, UE, etc.)
> of a similar ossia staff that shows clef and key signature? My gut
> feeling is that both clef and key signature should be *before* the
> barline, not after.
Not off the top of my head, but Gould says `When the /ossia/ st
On Thu, Feb 19, 2015 at 4:46 PM, wrote:
> This is not just replacing tabs with spaces. You also reformat here and
> remove empty lines at the end of the file. So the issue description is
> somewhat misleading. Any other changes?
>
Yes, sorry. I wasn't really sure how detailed to be. Where I f
On Sat, Feb 21, 2015 at 5:45 PM, wrote:
> This issue also says it is blocked by
>
> https://code.google.com/p/lilypond/issues/detail?id=777
>
> But I am not sure if what Barry has done so far is relevant to this.
>
> https://codereview.appspot.com/206770044/
>
I did first try using the ly-python
On Fri, Feb 20, 2015 at 5:57 PM, Paul Morris wrote:
> So I look forward to hearing from others on the list!
LGTM
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
hat you wanted.
Kevin
From 976465f12cb50c74f5ad4e36121758a7597d5e53 Mon Sep 17 00:00:00 2001
From: Kevin Barry
Date: Thu, 19 Feb 2015 15:51:52 +
Subject: [PATCH] Doc: replaced tabs with spaces in /ly/*.ly
---
ly/arabic.ly | 26 +-
ly/articulate.ly | 682 ++
3G looks best to me.
K.
On Sun, Mar 1, 2015 at 8:22 PM, Joram wrote:
> Hi Paul,
>
> Am 01.03.2015 um 20:22 schrieb Paul Morris:
> > Joram Berger wrote
> >> all versions have the green background fading in on the top right edge.
> >> I do not like that.
> >
> > Hi Joram, Based on previous feedb
On Tue, Mar 24, 2015 at 2:38 PM, Mark Knoop wrote:
> { \time 2/4 c'4 c'1 c'4 } % 3 bars, 2nd of which is empty
>
> { \time 2/4 c'4 c'2 c'4 } % 2 bars, neither of which is empty
>
At best I would consider these to be non-standard notation. At worst I'd
say it's incorrect. It's possible to write a
For sure the voice context limitations are a pain, and if I knew how, I
would write a function for starting and finishing slurs without the need
for creating a hidden voice, but I don't even know if it is possible. In my
own head, I imagine that LilyPond `thinks' in voices and there isn't much
that
Dear All,
During a transitional period where I have no computer I have tried
compiling the latest stable version of lilypond from source on a raspberry
pi to see if I could get it working. (The latest raspbian - still Debian
wheezy - is using 2.14.2 which will not work on most of my files.)
Everyt
I have some unexpected free time and would like to do this. Should I
contact you off list?
Kevin
On Sun, Jul 19, 2015 at 4:31 PM, Graham Percival
wrote:
> Add weight to your opinions by showing that you're not afraid of
> getting your hands dirty.
>
> texi2html is a vital part of the documentat
Hi David,
Just echoing everyone else's sentiments: your contribution to our
lives and work through your work on LilyPond is incalculable. As a
lurker of course I don't really understand much of what you do, but
it's clear that LilyPond would be far behind where it is now without
your development a
> We need to be able to resist Google. You may observe in real time how
> ready they are to comply with an authoritarian regime: It has long been
> extremely dangerous how much of a chokehold they have on digital
> ecosystems. Being complacent with “everyone uses Google, so let’s have
> it their wa
97 matches
Mail list logo
