Big thanks to Werner Lemberg for thoroughly updating (rewriting) the
visual index which I once put here¹ as an easy way to access the
LilyPond documentation. With some delay, I now merged this pull
request², you can look at the latest PDF here³. So it is no »Christmas
present« any longer, but for
> Those are included in the examples purely for the sake of completeness.
> Gould has nothing to say about such bar numbers and I would surprised if
> any scores included them.
But is it possible that they have a different alignment with the current
code? In case a user turns them on, they would
> I would very much like that LilyPond has the ability of automatically
> adjusting the horizontal position of some grobs, in particular dynamic
> signs, bar numbers, and rehearsal marks. The idea is that a large
> delta from the optimum vertical position would make LilyPond retry to
>
Hi,
I like the change in the bar number alignment. I have some comments to
your proposal. (The current solution has similar issues, so most of
these are not speaking against proposed changes.)
The -> denotes the solution for which that is an argument.
1. putting the bar number over the measure
> The python re syntax is clear, it just requires the right amout of
> backslashes or r-prefixes
I definitely overlooked how often there are *too many* backslashes in
the code. So there are a lot more changes requried than what is in merge
request 363:
Hi Jonas,
some comments to that:
1. I (hopefully) fixed all the escaping issues like #6024 in my merge
request: https://gitlab.com/lilypond/lilypond/-/merge_requests/363
The python re syntax is clear, it just requires the right amout of
backslashes or r-prefixes;
re.sub(r'\\command',
For automatic PEP8 formatting, there is
autopep8: https://pypi.org/project/autopep8/ and
yapf: https://pypi.org/project/yapf/
among others.
Cheers,
Joram
>> 1. LilyPond already seems to use some parts of the BOOST library (which
>> is kind of the extended C++ STL).
>
> Not that I know of.
>
You're right. I just quickly skimmed through a grep and found this:
https://github.com/lilypond/lilypond/blob/master/flower/include/yaffut.hh#L2
or a
> in C++ I worked with property_trees from BOOST (under the BOOST license):
>
> https://www.boost.org/doc/libs/1_73_0/doc/html/property_tree.html
Two more remarks:
1. LilyPond already seems to use some parts of the BOOST library (which
is kind of the extended C++ STL). There should be no license
Hi,
in C++ I worked with property_trees from BOOST (under the BOOST license):
https://www.boost.org/doc/libs/1_73_0/doc/html/property_tree.html
Cheers,
Joram
Am 07.06.20 um 12:30 schrieb Jean Abou Samra:
> The real problem merge commits pose in my eyes is that they can
> make 'git bisect' more difficult. I'm not an expert here, so I'll
> ask the question: would it make 'git bisect' completely unusable?
> Or just complicate it only in some specific
Hi,
Am 28.05.20 um 06:44 schrieb Werner LEMBERG:
>> This would mean every user would need to learn the new vocabulary if
>> they want to reference glyphs in their scheme code.
> Definitely not :-) However, I can imagine that LilyPond provides an
> option to *also* allow Bravura glyph names (or
Hi Dan,
as far as I understand (from experience with other projects), you can
clone anonymously (and fetch without authentication then).
If you want to be able to push, you need to authenticate and then you
also need to authenticate for fetch or pull.
A way around that is to use the ssh urls and
Ubuntu 20.04 will come with LilyPond 2.20. Older releases are usually
not updated after the release and will keep 2.18. Ubuntu 2.20 will
probably be released tomorrow.
https://packages.ubuntu.com/focal/lilypond
Frescobaldi will be 3.0.0 and not the latest 3.1.2:
Definitely a python2/3 issue. While python2 uses byte strings by
default, strings are Unicode strings in python3 and byte strings need to
be decoded first.
Surely, you know that and the question is: which part of the website
creation is not fully ported to python3.
python2 [2.7.17]
>>> 'abc',
> My browser complains about mixed content, i.e. http-linked media on the
> page.
>
> Urs
Here (Firefox 73), the only warning is about the "Valid HTML 4.01" image
in the page footer. All other images (on the pages I looked at) have
relative src attributes and are served directly from lilypond.org
FWIW, I remember when "français" was introduced. I could not find it in
the archives. But I think the consensus was that a correct spelling is
better than sticking to ascii and that is why español was added because
it was obvious.
So without finding the reference, I think you logically complete
I /think/ it is Unicode in NTFS now, but UCS/UTF-16 and not UTF-8:
https://stackoverflow.com/questions/2050973/what-encoding-are-filenames-in-ntfs-stored-as
https://en.wikipedia.org/wiki/Universal_Coded_Character_Set#Relationship_with_Unicode
Joram
FWIW, python has getattr and setattr which would perhaps suggest
get_prop(grob, "property") and
set_prop(grob, "property", VALUE)
I am not a fan of "arbitrary abbreviations" and get_property and
set_property are only 4 characters longer. So maybe I would choose the
latter (modulo your naming
> Found "Pidgin messenger" installed on my Ubuntu Studio. It purports to
> talk AIM, Bonjour, Gadu-Gadu, Google Talk, Groupwise, ICQ, IRC, Simple,
> Sametime, XMPP and Zephyr. No idea whether it does screencasts.
FWIW, I’ve had positive experiences with Jitsi:
https://jitsi.org/
It requires a
Dear developers,
tl;dr:
* please continue those discussions to a constructive end
* my experience as a non successful contributor
after more than a year of (relative) abstinence from LilyPond, I enjoy
reading the current drive in both commits and discussions in the
aftermath of the Salzburg
Am 26.04.2018 um 12:13 schrieb Torsten Hämmerle:
> I hardly dare to admit it, but all I used was Windows' infamous Paint
> program
:D
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Torsten,
I've confidence in your algorithm. I just thought I post a situation
which I would have neglected at first – without knowing what your
algorithm does.
Thanks for your explanation! It seems pretty robust and straightforward
to me, now. Are the two algorithms the equivalent if you make
Dear Étienne,
I'd like to understand what your contribution related to
https://codereview.appspot.com/329990043/ does.
Does it mean that after this patch we can automatically crop lilypond
snippets created with the svg backend? So we can use and include the
lilypond-book-preamble and produce svg
Hi,
lilypond.org seems to be downforeveryonenotjustme.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
Am 27.06.2017 um 22:34 schrieb tisimst:
> Take my vote for having it as the default.
It is just my gut feeling and nothing I could prove, but I see (at
least) two use cases for dotted slurs:
1. The current default looks like what I would prefer for "optional
slurs". I.e. in songs with two
Hi,
Am 06.03.2017 um 09:41 schrieb Urs Liska:
>> http://lilypondblog.org/2014/01/smufl-fonts-in-lilypond/
>>
>> I don't know whether this is still up to date.
> Oh, me neither.
> Joram?
1. Nathan was coding this, I just included this into oll and wrote the post.
2. I guess it still works.
3.
Hi,
Am 06.02.2017 um 20:08 schrieb d...@gnu.org:
> https://codereview.appspot.com/313240043/diff/21/scm/define-grob-properties.scm#newcode188
>
> scm/define-grob-properties.scm:188: (collapse-length ,ly:dimension? "An
> automatically generated
> collapse-width maybe? Length is more like a
> As extender events are generated automatically now it probably is a
> good idea to tell yacc / bison to recognize but ignore "__" tokens.
I don't know at which level the __, \overrides and the automatic
extenders interact. But would it make sense to use __ now, to force an
extender e.g. on a
Hi,
I tested the patch on my scores now (SATB choirs) and it works
perfectly. I applied the 0001-Automated-lyric-extenders.patch and it
adds the extenders where I had put them by hand before and a few other
reasonable places. Before, I made a per-syllable-decision whether I put
it or not. Now, a
Am 16.12.2016 um 17:38 schrieb Alexander Kobel:
> [2] Side Note: other proposed names for minimum-length so far:
>
> (1) minimum-space
> (2) show-length
> (3) hide-below-length
> (4) hide-if-shorter-than
> (5) minimum-visibility
> (6) visibility-threshold
> (7) printing-threshold
> (8)
Hi Alexander,
in your example, the last line is just a mockup, isn't it? It is not
done by the proposed function? The extender after "We" in the last line
is unexpected for me.
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Dear David,
I have nothing to add to what others have written here. But I want to
repeat it from my side: Thank you so much for your work on LilyPond!
Thank you for new functionality, for cleaner code, for easier input
syntax, for leading discussions with insightful contributions and
LilyPond
Hi Urs,
a very uneducated guess: Could it be that the html pages are only
generated if the input has changed and as you change the generating code
and not the doc-input, the generation is skipped? It is still strange
that it works if you empty the file.
Cheers,
Joram
Hi Larry,
some comments first:
a) This is a mailing list for Lilypond development (changing the program
itself), please use the lilypond-user list for user questions.
b) If you reduce your code to the absolute minimum, you may find the
issue yourself and you are more likely to find someone
>> I'm fine with making it classier rather than flashy. But removing it is
>> not doing us a favor.
>>
>
> Even though I don't love having print by default, there are times when I do
> leave it and having it classier is a wonderful idea.
Classier sounds good. My proposal stands [1]:
Hi Simon,
Am 24.02.2016 um 21:50 schrieb Simon Albrecht:
> On 23.02.2016 22:22, Noeck wrote:
>> the names \arpeggioUp and \arpeggioDown are still free and
>> would me much more lilypondish.
>
> More imprecise, really. It’s really only the direction of the a
Am 24.02.2016 um 00:08 schrieb Dan Eble:
> Is this a case where attaching an arpeggio to a chord with ^ or _ should make
> a difference, or do I misunderstand the point of those characters?
That was also discussed in the old thread. Not conclusive but with more
insights than I have:
Hi,
> I like this a lot and I feel like I've seen this exact discussion
> before, but it didn't result in any core changes.
https://lists.gnu.org/archive/html/lilypond-user/2015-01/msg00908.html
> Dev Team,
>
> Any reason \arpeggioArrowUp and \arpeggioArrowDown can't be defined this
> way
Hi,
>> 1) It is in *English* ...
>
> So let's try cutting it down to something language independent and
> short. Like
>
> 턵 www.lilypond.org
What is the tiny symbol in front of the url? A time signature but why?
>> 2) In general such a phrase looks *unprofessional* to me ...
>
> Shrug.
Hi
Am 23.02.2016 um 15:00 schrieb David Kastrup:
> I do agree that it should be unobtrusive, but I
> think that the LilyPond tagline meets that bar.
As I wrote in my other mail, I would vote to drop the "music engraving
with" part as it is not language independent and does not provide more
Hi Abraham,
I agree with you. I always change it or remove it for the following reasons:
1) It is in *English* and would be the only English part in my otherwise
German score – that looks just unprofessional. That's the most important
part for me.
2) In general such a phrase looks
Hi,
if you allow non-ascii letters in the note names (namely é in ré), why
not go all the way and call the language "français" instead of
"francais" (or at least in addition)?
Cheers,
Joram
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hi Simon,
> You should have come back to the entire quote: ‘And I think the double
> items suit the advanced functionality better (advanced in comparison to
> printing a hyphen character from a font).’ I didn’t mean ‘advanced’ in
> the sense of ‘only for advanced users’ or ‘rare’.
I know. I'm
Hi,
Am 17.02.2016 um 17:54 schrieb Simon Albrecht:
> And I think the double items suit the advanced functionality better
I thought about this when Dan wrote his first mail, but I wanted to keep
my comment short. I think many of you know the fun you can have with
backslashes and escaping (as in
Hi Dan,
Am 14.02.2016 um 20:41 schrieb Dan Eble:
> Are there technical limitations that require typing a double hyphen to
> hyphenate lyrics? Why not just one?
Because this way, a single hyphen keeps its function as an ordinary
character and a double-hyphen is not a really used/required item,
Both the test file and the issue text show wrong syntax like
\end\lilypond} or \end{lilypond\ and the test file includes a file2
which we do not have. If I correct that it works for me (Ubuntu).
So in order to make this reproducible and trace it down, complete and
correct files would be good to
Hi,
to follow the instructions given on
http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl I
need a Rietveld account. I have a sourceforge account for
testlilyissues, is that equivalent to an Allura account? Do I need
someting more to use git-cl correctly?
Best,
Joram
> To login on Rietveld ...
Perhaps I should rather ask: where is Rietveld? I found this
https://codereview.appspot.com/search?base=http://git.savannah.gnu.org/gitweb/?p=lilypond.git/trunk/
and tried to sign in. But Google wants my phone number, I guess I am out :(
Best,
Joram
Here is the corrected input file.
I ran
lilypond-book testbook.lytex
pdflatex testbook.tex
without errors which produces a correct (though strangely aligned) pdf file.
Cheers,
Joram
% test
\documentclass[a4paper]{article}
\usepackage[utf8]{inputenc}
%
\begin{document}
\begin{center}
Hi Urs,
possible advantages could be: a larger user base and maybe contributions
from more (academic/professional/knowledgeable) people to the engraving
quality of LilyPond. Offering a high quality engraving solution for an
already existing community. And other synergy effects and perhaps
Dear Richard,
first I want to emphasize that this was not against you or Denemo, just
a connection between my favoured workflows and the tools I use.
I don't understand 'traverse the staffs' in your sentence:
> It *does* provide a
> default LilyPond output, but you can just as easily traverse
Hi Peter,
these letters are defined around line 2191 of scm/define-grobs.scm
Adding (not replacing x) the c there turns every unknown number to
c. But perhaps you can find your way from there.
Even though I havn't seen anything else besides pima, I think your point
about completeness is right
I conclude from the patch mail, that this is going to be fixed soon.
PUSH:
Keith OHara: staccato moves to avoid ledge on opposite side of staff
http://code.google.com/p/lilypond/issues/detail?id=4184
If that is true, it is amazing how quick you are!
Thanks,
Joram
Hi,
If I needed to set the Schubert Op90n3, which looks like 4/2 to me,
I might notice a single-C style in the manual, figure out how to use
it, wonder why the c's are not barred where Schubert has them barred,
look into the code, be confused, decide to use markup like I should
have in the
I haven’t implemented the double-C cases yet.
This is what I think would be best:
* leave the default style alone
* add to the C style: 4/2 - CC, 2/1 - cut-CC
This would end the equivalence of default and C styles. Does that seem like
a bad idea to any seasoned Lilypond developers?
Dear developers,
[tl;dr: how about ISO language codes for input language selection?]
some time ago, I suggested to add French (français) to the list of
note-name languages as an alias to italiano. This is the current
state, español was also added.
The discussion back then was about some
57 matches
Mail list logo
