LilyPond code? For instance, if
> the book contains dozens or even hundreds of musical excerpts, do I need to
> disclose all the LaTeX code or just the musical notations?
No. The GFDL is the license telling you what you may or may not do with the
Lilypond documentation. It does not accect
Please don’t restart this 1000 times discussed nonsense.
The result of your typesetting, if you take the PDF or a print, doesn’t
contain source code of the used program. Your work is not subject of the
program’s license.
EOT
Hraban
## Clarification on the GNU Free Documentation License (GFDL) Applicability
### Background
Hello,
I have been exploring the LilyPond 2.24.4 documentation as I plan to use
LilyPond along with LaTeX to write some music education books for sale on
Amazon. However, I have come across some concerns
> This is a very basic question. I have see some examples that use
> constants like "$SELECTION" or ""$CURSOR'$ANCHOR". but despite doing all the
> obvious things (searching the documentation, etc.) I've not found any relevant
> information.
>
&
Hello,
This is a very basic question. I have see some examples that use
constants like "$SELECTION" or ""$CURSOR'$ANCHOR". but despite doing all
the obvious things (searching the documentation, etc.) I've not found any
relevant information.
I would sincer
ar.gz package. No
>> problem. But how may I obtain the documentation in texinfo format for
>> use with emacs? In fact, looking through the archive, it does not
>> appear that there is any documentation at all!
>
>
> Documentation is in a separate tarball, since most p
> I have recently upgraded from 2.22.2 to 2.24.3. However, as I only use
> LTS distributions of ubuntu, I had to download the tar.gz package. No
> problem. But how may I obtain the documentation in texinfo format for
> use with emacs? In fact, looking through the archive, it does not
&
Greetings,
I have recently upgraded from 2.22.2 to 2.24.3. However, as I only use
LTS distributions of ubuntu, I had to download the tar.gz package. No
problem. But how may I obtain the documentation in texinfo format for
use with emacs? In fact, looking through the archive, it does not
appear
Le mardi 02 mai 2023 à 07:05 +0200, Thomas Weißschuh a écrit :
> Hi,
>
> it seems the documenation archives for 2.24 (and 2.25) are missing from
> https://lilypond.org/downloads/binaries/documentation/ .
This is our old downlod site, as mentioned on
https://lilypond.org/old-do
Hi,
it seems the documenation archives for 2.24 (and 2.25) are missing from
https://lilypond.org/downloads/binaries/documentation/ .
Thomas
Le lundi 13 février 2023 à 12:02 -0500, Kevin Cole a écrit :
> That's okay too... as long as, when I ask a question, the answer isn't
> always "upgrade".
To speak for myself: If you say in your post “I know that this feature is in
the latest stable
version but I can't/don't want to upgrade be
On Mon, Feb 13, 2023 at 12:00 PM Saul Tobin wrote:
> Many users have old projects on very old versions of Lilypond, and sometimes
> you just want to make a small edit, not update your whole project to use the
> new version. It's important for documentation to be available.
T
On Mon, Feb 13, 2023 at 11:55 AM Jean Abou Samra wrote:
>
> Le lundi 13 février 2023 à 11:40 -0500, Kevin Cole a écrit :
>
> The point I was trying to make was "Does there REALLY need to be
> documentation for versions 2.13 to 2.25? Maybe 2.20 to 2.25 would
> suffice.&quo
Many users have old projects on very old versions of Lilypond, and
sometimes you just want to make a small edit, not update your whole project
to use the new version. It's important for documentation to be available.
On Mon, Feb 13, 2023, 8:41 AM Kevin Cole wrote:
> On Mon, Feb 13, 20
Le lundi 13 février 2023 à 11:40 -0500, Kevin Cole a écrit :
> The point I was trying to make was "Does there REALLY need to be
> documentation for versions 2.13 to 2.25? Maybe 2.20 to 2.25 would
> suffice."
I'm not sure it would help with Qwant/DuckDuckGo/Goog
may entail helping them navigate the online documentation; in
> > such cases it may sometimes be appropriate to point them to
> > version-agnostic URL paths such as
> > ``[/latest/](https://lilypond.org/doc/latest/Documentation/notation) or
> > ``[/sta
leased every few weeks
> to months.
The point I was trying to make was "Does there REALLY need to be
documentation for versions 2.13 to 2.25? Maybe 2.20 to 2.25 would
suffice."
Hi,
From https://lilypond.org/help-us.html
“Mailing list support: answer questions from fellow users. (This may
entail helping them navigate the online documentation; in such cases
it may sometimes be appropriate to point them to version-agnostic URL
paths such as |/latest/|
<ht
Hi Kevin,
On the other hand, I strongly favor sticking with a distribution's
package rather than starting every day with a "git pull". So, I'm
always slightly behind the latest and greatest.
Just for the record: Your description omits the (actually quite
convenient) middle between the two ext
In the past, when I've asked a question, the answer has often been a
gentle RTFM with a link to the appropriate info, followed by "Oh.
You're using the version from four days ago, rather than the version
du jour. That documentation doesn't apply to your version."
Le lundi 13 février 2023 à 09:42 -0600, David Wright a écrit :
> Very tangential to this, a URL like:
>
>
> [https://lists.gnu.org/archive/html/lilypond-user/recent](https://lists.gnu.org/archive/html/lilypond-user/recent)
>
> that would redirect to:
>
>
> [https://lists.gnu.org/archive/h
On Mon 13 Feb 2023 at 15:58:42 (+0100), Jean Abou Samra wrote:
> Mailing list support: answer questions from fellow users.
> (This may entail helping them navigate the online documentation;
> in such cases it may sometimes be appropriate to point them to
> version-agnostic URL p
Le 13 févr. 2023 à 15:51, Valentin Petzel a écrit :Hello Pondmates!I’ve been wondering recently: When acessing the documentation we are usually acessing a specific version, we have something likelilypond.org/doc/v2.xy/whateverThis seems to mess with Google’s page scoring quite a bit. Now if I
Hello Pondmates!
I’ve been wondering recently: When acessing the documentation we are usually
acessing a specific version, we have something like
lilypond.org/doc/v2.xy/whatever
This seems to mess with Google’s page scoring quite a bit. Now if I were a new
user, oblivious to how certain
weird that the fill chooser dialog won't show .html files (and no,
they are not hidden files). Strange. And I'd still like to know how F
mysteriously display the 2.22 documentation page, with no settings
indicating that. Stupid to even try, but reinstalling F made no
difference.
Where
not hidden files). Strange. And I'd still like to know how F
mysteriously display the 2.22 documentation page, with no settings
indicating that. Stupid to even try, but reinstalling F made no difference.
Where is actually the best place to post about Frescobaldi support nowadays?
Andrew
On Fri 20 Jan 2023 at 14:09:05 (+1100), Andrew Bernard wrote:
> Frescobaldi 3.2 on Linux (EndeavorOS, and Ubuntu), no matter what URL
> or local file I put in the Lilypond Documentation preferences it does
> not work. If I use a URL at lily[pond.org I get an Apache error. If
> try
Frescobaldi 3.2 on Linux (EndeavorOS, and Ubuntu), no matter what URL or
local file I put in the Lilypond Documentation preferences it does not
work. If I use a URL at lily[pond.org I get an Apache error. If trying
to add a local copy the index.html file simply does not appear in the
browser
Le 21/11/2022 à 23:14, Jean Abou Samra a écrit :
I tried doing a speed test myself, but hit
https://gitlab.com/lilypond/lilypond/-/merge_requests/1714#note_1180441076
After correcting my stupid mistake, I got
pdfTeX:
real 21m43,063s
user 117m52,570s
sys 17m24,881s
LuaTeX:
real
Le 21/11/2022 à 22:10, Jonas Hahnfeld via Discussions on LilyPond
development a écrit :
And whether we can just *require* LuaTeX and stop looking for pdfTeX
and XeTeX altogether?
I did a few measurements for the case of building the LilyPond
documentation and, in terms of speed with the &qu
The LilyPond repository is the only one that I follow closely that
actually has (not quite but almost) daily updates anyway. I try to
keep up to date as to where it's going, how it works and who's
implicated (and in what capacity/portion). It is a big and complicated
project that seems to have a li
Le 18/08/2022 à 21:30, Pierre-Luc Gauthier a écrit :
I also read "git log -p" on a daily basis.
Just curious: are you really reading `git log -p` *on the LilyPond
repository* on a daily basis? Or is this a general method to learn
about software that you apply for various pieces of software on
how to do it.
>
> For the record, I learned a *lot* reading all (most) of the change logs :
>
> http://lilypond.org/doc/v2.23/Documentation/changes/
> http://lilypond.org/doc/v2.22/Documentation/changes/
> http://lilypond.org/doc/v2.20/Documentation/changes/
> http://lilypond.or
Thanks Andrew for your input. I did write a few manuals (and still do)
for some system usage and I know how hard it can be to cover all what
a system can do and how to do it.
For the record, I learned a *lot* reading all (most) of the change logs :
http://lilypond.org/doc/v2.23/Documentation
know. For example,
> > the tremolo; I recognized the graphic but I had no way to search for
> > it by appearance, only read every line of the documentation until I
> > find it and the "ah ha".
>
> This is where I imagine the visual index is most helpful. But I
#x27;t know. For
> > example, the tremolo; I recognized the graphic but I had no way to
> > search for it by appearance, only read every line of the
> > documentation until I find it and the "ah ha".
>
> I think you are looking for the 'Visual LilyPond Grob Ind
to
> search for it by appearance, only read every line of the
> documentation until I find it and the "ah ha".
I think you are looking for the 'Visual LilyPond Grob Index':
https://github.com/joram-berger/visualindex
This gives you the name of the grob, which you can
phic but I had no way to search for
it by appearance, only read every line of the documentation until I
find it and the "ah ha".
This is where I imagine the visual index is most helpful. But I do
wonder how often the Music Glossary is overlooked as a resource. It
includes pictures
what it is that I don't know. For example,
the tremolo; I recognized the graphic but I had no way to search for
it by appearance, only read every line of the documentation until I
find it and the "ah ha".
I'm making no complaint about the quality of the documentation; I
t
I call a
'hard problem.'
I agree, and appreciate the effort you put into writing that.
I second Jean Abou Samra's motion for expanding the index if it seems
good to so so.
Lilypond.org is hosted on a Google service, I believe? Are there ways to
see what search terms people use to
d on. The manual is written by one dedicated full
time staff member. It's an amazing effort. I think it is truly
remarkable as documentation, yet when it does not conform to what a user
expects. they whine on the forum.
Why am I telling this? Because it highlights the problem with sof
Le 18/08/2022 à 04:16, Kenneth Wolcott a écrit :
Hi;
Dumb documentation question here:
Kind of like a FAQ but also kind of like an index.
So this would be a "translation" of layman's terms to
Lilypond/professional terminology and an index; it could even point to
existing indic
I do see the FAQ on the documentation page, but I think that this
needs to be expanded, in more detail, as it frequently takes too long
to find things in the existing documentation.
Maybe I just don't use the right search strings to find what I'm looking for.
On Wed, Aug 17, 2022
Hi;
Dumb documentation question here:
Kind of like a FAQ but also kind of like an index.
So this would be a "translation" of layman's terms to
Lilypond/professional terminology and an index; it could even point to
existing indices (in Notation) and/or the Glossary.
Q: Doe
Wols Lists writes:
> On 19/03/2022 20:01, David Kastrup wrote:
>> Sam Roberts writes:
>>
>>> I tried so hard to be accurate, but I missed something:
>>>
>>> On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
After experimentation, I found this worked:
\time 3/4 \partial 1 c4 |
l wrong: its argument does not specify how
long it is _since_ a full bar but how long it is _to_ a full bar.
As such, you'd usually see
... \time 3/4 \partial 4 c4 | ...
in typical contexts.
And the REAL problem is that he quite clearly does not understand the
documentation (or can'
On Sat, Mar 19, 2022 at 1:57 PM Sam Roberts wrote:
>
> > The * syntax is described here:
> >
> > https://lilypond.org/doc/v2.22/Documentation/notation/writing-rhythms#scaling-durations
This is a good page to bookmark if you need to lookup the syntax of a command:
https://l
> The * syntax is described here:
>
> https://lilypond.org/doc/v2.22/Documentation/notation/writing-rhythms#scaling-durations
Thank you, that's perfect.
Sam
> For my more general understanding, is there documentation anywhere for
> the syntax of the argument to partial? Something that will explain the
> * syntax shown on this page?
That is simple. The argument to \partial is a duration.
>
https://music.stackexchange.com/questions/1
On Sat, Mar 19, 2022 at 2:41 PM Sam Roberts wrote:
>
> For my more general understanding, is there documentation anywhere for
> the syntax of the argument to partial? Something that will explain the
> * syntax shown on this page?
>
>
> https://music.stackexchange.com/qu
ore general understanding, is there documentation anywhere for
the syntax of the argument to partial? Something that will explain the
* syntax shown on this page?
https://music.stackexchange.com/questions/106875/how-to-write-a-pickup-measure-with-5-16-duration-in-lilypond
Thanks,
Sam
Sam Roberts writes:
> I tried so hard to be accurate, but I missed something:
>
> On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
>> After experimentation, I found this worked:
>>
>> \time 3/4 \partial 1 c4 |
>
> It "works" in that pdf output looks ok, c4 is in the pickup bar, but
> still wa
I tried so hard to be accurate, but I missed something:
On Sat, Mar 19, 2022 at 12:38 PM Sam Roberts wrote:
> After experimentation, I found this worked:
>
> \time 3/4 \partial 1 c4 |
It "works" in that pdf output looks ok, c4 is in the pickup bar, but
still warns about the bar checks, as it sho
n the duration syntax, but I'm not succeeding yet.
Can someone point me to docs, or perhaps explain the syntax?
https://lilypond.org/doc/v2.21/Documentation/learning/advanced-rhythmic-commands#partial-measure
as an example, just has a couple examples, but not a complete syntax.
Thank you,
Sam
allocate sounds (aka midi channels) in a round robin
fashion when exceeding the 16 channel midi limit. Either follow the
suggested methods as of the documentation or deal with this in a DAW or
proper midi sequencer in post processing (e.g. by reallocating excess
channels to new tracks).
Kind
Well,. I'm part of the same club, the Midi environment has always been a
hard chapter, anyhow, I know the difference between 'track' and 'channel' :
in sound or video editing software, the track is just a container, you can
have multiple tracks, video tracks, audio tracks, Midi tracks and so on,
an
Greetings All,
I preface this by acknowledging that I know nothing about the
innerworkings of MIDI. In section 3.5.7 of the NR, which deals with
MIDI channel mapping, there appears to be a discrepancy in the wording
about channels and tracks. The third paragraph implies that channels
and tracks ar
Hi,
The change to add syntax highlighting in the HTML version of the
LilyPond documentation, discussed at
https://lists.gnu.org/archive/html/lilypond-user/2022-01/msg00012.html
on the lilypond-user list and in various lilypond-devel and GitLab
threads, has now landed in the source tree and
access the English version directly.
(For documentation with a specialised audience, I always wonder if
such divergence between versions would be better avoided with
linguistic monoculture, but I really appreciate the effort! [And I
hope this does not sound deprecating – it's not meant
ree that the explanations regarding markups vs. markup
lists, markup vs. stencils, markup in scheme etc. in the Documentation
might be improved.
For what it's worth, a step has been made
just a few weeks ago with
https://gitlab.com/lilypond/lilypond/-/merge_requests/1089
That merge request
Hi Lukas,
Lukas-Fabian Moser schrieb am 21.01.22 um 17:15:
Also note
[...]
The standard use case for make-XXX-markup is explained in:
http://lilypond.org/doc/v2.23/Documentation/extending/markup-construction-in-scheme.html
under "Known issues and warnings".
I had read that, and
Jean Abou Samra writes:
> Le 21/01/2022 à 08:57, Bernhard Fisseni a écrit :
>> Good morning,
>>
>> Consequence: There is no collision between an auxiliary function
>> CMD and a homonymous markup command \CMD, as they are (CMD ...) and
>> (make-CMD-markup ...), respectively, in scheme.
>
>
> Yes
plans of similar scope, and [I] work on LilyPond as a
hobby in otherwise already LilyPond development
is for me a hobby in already otherwise busy weeks.
Talk about busy weeks...
oc/v2.22/Documentation/extending/markup-construction-in-scheme>
uses this implicitly in the last paragraphs, but an explicit remark
might be helpful.
<http://lilypond.org/doc/v2.22/Documentation/extending/how-markups-work-internally>
explains the correspondence with one example, but
case for make-XXX-markup is explained in:
http://lilypond.org/doc/v2.23/Documentation/extending/markup-construction-in-scheme.html
under "Known issues and warnings".
I would agree that the explanations regarding markups vs. markup lists,
markup vs. stencils, markup in scheme etc.
Hi Bernhard,
unfortunately I don't have much time at the moment (and there's always
the chance that Jean or someone else more knowledgeable than me is
already working on an exhaustive answer), but there's one thing I'd like
to point out:
#(define-markup-command (strut-line layout props line
tions.)
- In my opinion writing the scheme code is much easier than mixing
Lilypond and Scheme.
- For every markup command and every markup list command \CMD, there is
a corresponding scheme function make-CMD-markup.
<http://lilypond.org/doc/v2.22/Documentation/extending/markup-construction-i
Jean Abou Samra wrote:
[Robin]
The stroke width I see is 1px (Firefox at 100%). This makes the
stroke dominated by edge effects; the surrounding white dilutes its
colour.
Do the WCAG recommendations recognise this? If not, please don't
apply their levels to this case.
I don't know. I am
Hello Paul,
The documentation does not specify any fonts. It simply uses the and
tags. That means that the fonts used are whatever font your
browser chooses as default font, which on Windows systems appears to be
Courier for monospace and apparently in your case Georgia for the regular
text
point of view of a
colorblind person myself. The end goal is definitely
to have the documentation site readable for
everyone -- including those with disabilities --
and not just to follow recommendations blindly.
[Paul]
And this seems the appropriate place to ask why the examples are all
in fixed
Le 04/01/2022 à 23:19, Aaron Hill a écrit :
On 2022-01-04 1:42 pm, Jean Abou Samra wrote:
https://www.gnu.org/philosophy/javascript-trap.en.html
[ . . . ]
But I'm probably fretting for something that is
very easy in the end.
The code Lilypond's site would use would be entirely homegrown,
lice
#x27;t see the relevance for
documentation. The goal is to help the reader,
not the documentation writer. Whether the input is
intentional or not -- and it should really be
for documentation --, focusing the reader's
attention on that is inappropriate. Not to mention
that \func a 8 where \func is
On 2022-01-04 1:42 pm, Jean Abou Samra wrote:
https://www.gnu.org/philosophy/javascript-trap.en.html
[ . . . ]
But I'm probably fretting for something that is
very easy in the end.
The code Lilypond's site would use would be entirely homegrown, licensed
under GPL. Not sure there is anything h
t of a banner asking
for explicit consent of the user? Otherwise, as
far as I can read, the requirement is that you
must ask for permission before storing or using
the data, so this permission could be asked
to the reader just when toggling highlighting
and not for everyone reading the documentation,
eader just when toggling highlighting
and not for everyone reading the documentation,
right? I'm a bit at loss trying to understand
what is OK or not in this respect.
The fact that it's stored on the user's own device (and the server never
sees it) means that the GDPR is irrelevant.
On 2022-01-04 11:32 am, Jean Abou Samra wrote:
Forgive my igorance with the inner workings of the
Internet: what does this mean in connection with GDPR
and all that? Am I right that the fact that the
information stored on the user's device serves
a purpose essential to satisfying the very request
> to the reader just when toggling highlighting
> and not for everyone reading the documentation,
> right? I'm a bit at loss trying to understand
> what is OK or not in this respect.
>
> Other than that, well, there is still JavaScript.
> That's may not be the thing to
read, the requirement is that you
must ask for permission before storing or using
the data, so this permission could be asked
to the reader just when toggling highlighting
and not for everyone reading the documentation,
right? I'm a bit at loss trying to understand
what is OK or not in this respe
On 2022-01-04 10:04 am, Valentin Petzel wrote:
The problem is that we probably want to
remember the set color scheme for longer than just the current page,
so we'd need something like cookies.
Not a problem in the slightest. But not cookies... localStorage [1].
[1]:
https://developer.mozilla
ating multiple versions of the docs
referencing different stylesheet.
Of course this would kind of blow up the size of the documentation for changing
a single line.
Sadly the browser functionality for multiple stylesheets usually consists of an
obscure list hidden in some menu.
In my opinion the best
On 04/01/2022 16:23, Aaron Hill wrote:
On 2022-01-04 7:29 am, Erika Pirnes wrote:
Would it be terribly difficult to have a color setting on the
documentation page, so that people can choose between black and color?
It is fairly straightforward with CSS and a little JavaScript:
Is that on
On 04/01/2022 15:14, J Martin Rushton wrote:
OK, I'll admit I only skimmed it, hence "I've saved the paper to read
later"! I've got Doob's "A Gentle Introduction to TeX" and Oetiker's
"The Not So Short Introduction to LaTeX2e" both of which keep to the
fixed width convention. Again, I'll be hon
On 2022-01-04 7:29 am, Erika Pirnes wrote:
Would it be terribly difficult to have a color setting on the
documentation page, so that people can choose between black and color?
It is fairly straightforward with CSS and a little JavaScript:
Dynamic styles
body { font-size
difficult to have a
color setting on the documentation page, so that people can choose between
black and color?
Erika
both TeX and METAFONT entirely in his WEB
> programming
> system for Literate Programming. I have the printed book for TeX.
>
> > On Tue, 2022-01-04 at 05:10 -0800, Aaron Hill wrote:
> > > On 2022-01-04 4:19 am, J Martin Rushton wrote:
> > > > Sorry to disagree, but f
tten both TeX and METAFONT entirely in his WEB programming
system for Literate Programming. I have the printed book for TeX.
>
> On Tue, 2022-01-04 at 05:10 -0800, Aaron Hill wrote:
>> On 2022-01-04 4:19 am, J Martin Rushton wrote:
>> > Sorry to disagree, but fixed pitch is _so_ much
Hello Robin,
as far as I know the Lilypond Documentation does not specify the font to be
used for this. So the system defaults to a standard monospace font.
So the font will depend on the system. We could ship a dedicated font with the
documentation, but I'm not sure if we want that.
C
n wrote:
> > Sorry to disagree, but fixed pitch is _so_ much easier to lay out
> > in an
> > editor. Documentation flows nicely with variable pitch and fancy
> > hidden formats, but for code (and Lily's input is a programming
> > language) you just want the
On 2022-01-04 4:19 am, J Martin Rushton wrote:
Sorry to disagree, but fixed pitch is _so_ much easier to lay out in an
editor. Documentation flows nicely with variable pitch and fancy
hidden formats, but for code (and Lily's input is a programming
language) you just want the plain line-by
Paul,
Sorry to disagree, but fixed pitch is _so_ much easier to lay out in an
editor. Documentation flows nicely with variable pitch and fancy
hidden formats, but for code (and Lily's input is a programming
language) you just want the plain line-by-line ASCII. It is, as you
say, ind
'Hear hear' to these recent posts from Thomas, Paul and the two Davids!
I don't object to the fixed width, but the code font has always been
spindly compared to the rest of the documentation text. I find this
makes it harder to read anyway.
The stroke width I see is 1px
Am Di., 4. Jan. 2022 um 11:15 Uhr schrieb Paul McKay :
>
> Hi
> Speaking as someone whose eyesight isn't quite as good as it used to be,
Same problem here
> I'd like to suggest that anything in a colour is also in bold so that there
> are enough pixels for me to see what the colour is.
I'd go e
t
so that there's a clear contrast with the Georgia used as the text font in
the documentation. Helvetica, Franklin Gothic and Source Sans Pro look good
but I realize they might not be available on some platforms.
HTH
Paul McKay
On Mon, 3 Jan 2022 at 23:33, David Kastrup wrote:
> Flaming H
Flaming Hakama by Elaine writes:
> In this sense, it seems like the place that has the most potential use
> for helping people distinguish different data types is where the
> syntax is the most complicated and dense, which is in music entry.
>
> The ability to quickly distinguish articulations, d
>
> Am Sonntag, 2. Jänner 2022, 01:06:35 CET schrieb David Kastrup:
> > Jean Abou Samra writes:
> > > Hi all,
> > >
> > > There is an ongoing proposal to add syntax highlighting
> > > in LilyPond's documentation. Since it is a notable chang
Jean Abou Samra writes:
> Hi all,
>
> There is an ongoing proposal to add syntax highlighting
> in LilyPond's documentation. Since it is a notable change
> to the documentation reading experience, user feedback would
> be appreciated. You can browse a syntax-highlighted ve
the list at
> lilypond-user-ow...@gnu.org
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of lilypond-user digest..."
> Today's Topics:
> 1. Re: Feedback wanted: syntax highlighting in the LilyPond
>
On 02/01/2022 16:32, Jean Abou Samra wrote:
I am colorblind (which BTW means that it's hard to distinguish certain
colors, not that everything is gray).
Sorry if I gave a wrong impression. I didn't
mean that everything actually looked gray, just
that it was the extreme imaginary case encompa
Le 02/01/2022 à 17:01, Knute Snortum a écrit :
On Sun, Jan 2, 2022 at 7:10 AM Jean Abou Samra wrote:
...
[Marc]
It will be necessary to keep an uncolored version for men (in
principle women do not have this problem) who do not see well certain
colors.
This is taken care of -- the colors have
On 02/01/2022 09:34, Marc Lanoiselée via LilyPond user discussion wrote:
It will be necessary to keep an uncolored version for men (in principle
women do not have this problem) who do not see well certain colors.
In principle (and practice) women DO suffer this problem. It's caused by
a defect
1 - 100 of 1081 matches
Mail list logo
