fixed Typo doc de #10
Conversation
|
@aploese thank for the fix! Could you submit the change via GitLab as described here: https://lilypond.org/doc/v2.25/Documentation/contributor/lifecycle-of-a-merge-request ? We don't really accept PRs via GitHub (but have no way of disabling for the repository... |
Is this still true? https://stackoverflow.com/questions/27957454/how-to-disable-pull-requests-in-github seems to indicate that this has changed... |
|
Or maybe this solution might help: |
AFAICT this is for setting up branch protection and then configuring bypassing, ie who is allowed to push. But the ability to create PRs will remain.
Same here: It will just auto-close PRs. And I don't really want GitHub-specific configuration files in the repo... Anyway, this topic should not be discussed here. The current status is that we don't accept PRs on GitHub. |
Inserting QR-codes is a feature that was requested multiple times. Cf. frescobaldi/frescobaldi#312 https://lists.gnu.org/archive/html/lilypond-user/2018-05/msg00350.html https://lists.gnu.org/archive/html/lilypond-user/2012-07/msg00143.html https://lists.gnu.org/archive/html/lilypond-user-fr/2022-07/msg00005.html While this can of course be done with an image, it becomes cumbersome to generate those images for each score one publishes, especially if every part has its own QR code for example. It is much more convenient to insert the URL directly into the LilyPond input. This also opens up the possibility to make sites similar to Mutopia insert a QR code automatically in the footer, with part of the URL computed in Scheme from the file name or such. There was prior art in https://lsr.di.unimi.it/LSR/Item?id=1153, which did not, however, allow inserting the URL directly into the input, instead requiring to copy a bit array representing the code, still generated externally. This patch goes further by implementing a minimal QR code encoder in Scheme, allowing the syntax \markup \qr-code #10 "https://lilypond.org"
No description provided.