On Thu, Oct 20, 2022 at 7:40 AM Jean Abou Samra wrote:
> Le 20/10/2022 à 07:22, Werner LEMBERG a écrit :
>
> It would be a problem if we assigned copyright to the FSF.
> As you mentioned below, we don't do this.
>
> > [*] Here comes the benefit of transferring the copyright to the FSF,
> > w
On Thu, Oct 20, 2022 at 7:57 AM Jean Abou Samra wrote:
> This is not correct, since copyright doesn't
> exist for something in the public domain (as opposed to something released
> under a permissive license). So the file headers need not mention any
> copyright at all, if the code is unmodified.
Le 20/10/2022 à 07:38, Jean Abou Samra a écrit :
You just don't
become the copyright owner of the code, i.e., the copyright
header in the source repository should give the name of
the original author.
I have to correct myself. This is not correct, since copyright doesn't
exist for something i
Le 20/10/2022 à 07:22, Werner LEMBERG a écrit :
Assuming that it is ok with , we can put his
outdated, GPLed code into the public domain. Harm, do you remember
the history of this snippet? [For such historical research it would
be great if the LSR was actually a git repository that gets eventuall
> The LSR is advertised as being released under the public domain.
> [...]
>
> The following exceptions apply:
>
> * It does not apply to input files (contained in the directory
> tree Documentation/snippets/); these are in the public domain.
> [...]
>
> So far, so good. However, take
Hi,
I figured that now I am an LSR editor, I had to learn about what
legal responsibility I have when accepting contributions.
The LSR is advertised as being released under the public domain.
This is supposed to work in conjunction with LilyPond contributors
making modifications in snippets/new/
Here is the current countdown report.
The next countdown will begin on October 21st.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1671 Avoid deprecated fgrep in fix-docsize.sh - Jonas Hahnfeld
https://gitla
Le 19/10/2022 à 23:25, Carl Sorensen a écrit :
Can't we add a batch file or shell script that contains the command
(pointing to the lilypond binary) with the proper environment variable
set, and point Frescobaldi to the batch file/shell script, rather than
to the lilypond binary? We could even
On Wed, Oct 19, 2022 at 2:54 PM Federico Bruni wrote:
>
>
> Il giorno mer 19 ott 2022 alle 18:06:16 +0200, Jean Abou Samra
> ha scritto:
> > Le 19/10/2022 à 17:25, Federico Bruni a écrit :
> >> You have to manually add `/app/dev/bin/lilypond` in Frescobaldi.
> >> (it's explained in the Github R
Il giorno mer 19 ott 2022 alle 18:06:16 +0200, Jean Abou Samra
ha scritto:
Le 19/10/2022 à 17:25, Federico Bruni a écrit :
You have to manually add `/app/dev/bin/lilypond` in Frescobaldi.
(it's explained in the Github README)
It's a Frescobaldi limitation: it checks and adds only the first
Le 19/10/2022 à 17:25, Federico Bruni a écrit :
You have to manually add `/app/dev/bin/lilypond` in Frescobaldi. (it's
explained in the Github README)
It's a Frescobaldi limitation: it checks and adds only the first
lilypond executable in the PATH.
OK, I may have invented a nonexistent proble
> The page
>
> https://lilypond.org/doc/v2.23/Documentation/notation/writing-text.html#text-marks
>
> is missing some backslashes in the box [...]
>
> I don't immediately see what this discrepancy could be caused by,
> apart from a bug or limitation of texi2html 1.82.
>
> Can this be worked aro
Il giorno mer 19 ott 2022 alle 17:12:31 +0200, Jean Abou Samra
ha scritto:
Basically it limits "never recompile" to files whose path starts
with "/app/".
I don't know Flatpak enough to be certain that /app/ is the right
path to check, though.
I think it's correct. I'll test and let you know.
Le 17/10/2022 à 22:23, Federico Bruni a écrit :
If anybody can provide a patch which can disable automatic
recompilation internal to Guile and LilyPond only, I'd be happy to
apply it.
I'm not sure how to test this but I think it should work:
From fa8f848423d6a104aad0e8ba8fdf87feedd0c4a6 Mon
The page
https://lilypond.org/doc/v2.23/Documentation/notation/writing-text.html#text-marks
is missing some backslashes in the box "Note: Older LilyPond
used the [\]mark command ...". On the other hand, the corresponding
PDF https://lilypond.org/doc/v2.23/Documentation/notation.pdf
is fine. The
15 matches
Mail list logo
