In the following markup command definition
#(define-markup-command (test layout props enclosure content)
(scheme? markup?)
(interpret-markup layout props (markup #:circle content)))
I would like to make the #:circle parametric, i.e. I want to pass
something into the function (e.g. as the
On 2020-07-03 1:07 pm, Urs Liska wrote:
But I'd rather do something like
(markup (assq-ref enclosures enclosure) "CC")
markup is a macro, and macros appear to have unique rules of evaluation.
The following approach defers the macro expansion:
\version "2.20.0"
#(define (get-scheme-markup-function func)
(string->symbol
(string-append "make-"
(symbol->string func)
"-markup")))
... which should be replaced by
#(define (get-scheme-markup-function func)
(symbol-append 'make- func '-markup))
Sorry, I had
On 03/07/2020 13:48, Paolo Prete wrote:
Hello,
1) Is there a GPL or open-source alternative for FETA fonts for accidentals
that can be used with Lilypond? (If so, is there an example of how to use
them)?
https://www.chiark.greenend.org.uk/~sgtatham/gonville/
?
James
Am Freitag, 03. Juli 2020 21:52 CEST, Urs Liska schrieb:
> Unfortunately I don't really have an idea what "#:circle" actually
> *is*, so I have no clue about getting where I need to.
Syntacilally? That would be a scheme keyword.
Cheers, RalfD
> BestUrs
>
>
--
Ralf Mattes
Hochschule für
Urs Liska wrote:
Unfortunately I don't really have an idea what "#:circle" actually
*is*, so I have no clue about getting where I need to.
I think it's a sort of macro thingy, trying to be easy to be used.
Look at 'Known issues and warnings' at the bottom of
Hi Robin,
Am Freitag, den 03.07.2020, 22:11 +0200 schrieb Robin Bannister:
> Urs Liska wrote:
>
> > Unfortunately I don't really have an idea what "#:circle" actually
> > *is*, so I have no clue about getting where I need to.
>
> I think it's a sort of macro thingy, trying to be easy to be
On Jul 3, 2020, at 3:18 PM, David F. wrote:
> macOS 10.14.6
> Frescobaldi 3.1.2
>
> I was working on a song in Frescobaldi. After renaming the directory that
> the song is in Frescobaldi no longer shows the PDF for the song after
> engraving.
>
> Does Frescobaldi keep track of what PDF
> On 3 Jul 2020, at 18:09, Zone Dremik wrote:
>
> I just upgraded to Mac OS 10.15.5 and now convert.ly has stopped working
> entirely. I get the following error message;
>
> arch: posix_spawnp:
> /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7: Bad
> CPU type in
Am Freitag, 03. Juli 2020 22:07 CEST, Urs Liska schrieb:
> > Syntacilally? That would be a scheme keyword.
>
> So that would be difficult to inject from a variable/argument, isn't
> it?
No, why? You can of course store a keyword in a variable and/or pass it as an
argument.
> I can of course
Hi Urs,
Thanks a lot. That's exactly the kind of procedure I can store and
apply:
\version "2.20.0"
#(define-markup-command (dyna layout props func content)(symbol?
markup?)
(let*
((funcs
`((box . ,make-box-markup)
(circle . ,make-circle-markup
The bad news with Catalina is that is won’t run 32 bit apps (Mojave is the last
version that accepts them), and I suspect that the Python version you’re using
is such an application.
Maybe switching to a 64 bit Python version will solve the issue.
JM
> Le 3 juil. 2020 à 20:38, Hans Åberg a
Am Freitag, den 03.07.2020, 21:58 +0200 schrieb Ralf Mattes:
>
> Am Freitag, 03. Juli 2020 21:52 CEST, Urs Liska <
> li...@openlilylib.org> schrieb:
>
> > Unfortunately I don't really have an idea what "#:circle" actually
> > *is*, so I have no clue about getting where I need to.
>
>
> On 3 Jul 2020, at 21:46, Jacques Menu wrote:
>
> The bad news with Catalina is that is won’t run 32 bit apps (Mojave is the
> last version that accepts them), and I suspect that the Python version you’re
> using is such an application.
> Maybe switching to a 64 bit Python version will
This is *MUCH* better for *MANY* and *MANY* reasons, thanks.
The more I observe them, the more I find excellent adjustments.
They also save useful space.
The only glyph that I don't like is the fermata one. The dot is too small
and, therefore:
1) it does not differ well from the staccato glyph.
macOS 10.14.6
Frescobaldi 3.1.2
I was working on a song in Frescobaldi. After renaming the directory that the
song is in Frescobaldi no longer shows the PDF for the song after engraving.
Does Frescobaldi keep track of what PDF file belongs to what input file? Can
that information be flushed?
Dear David,
Il giorno ven 3 lug 2020 alle ore 23:48 David F. ha scritto:
> Frescobaldi is having problems with file paths that have question marks and
> accented characters.
tomorrow I'll test and get back to you.
> This problem is not present in Frescobaldi 2.20.
This is interesting.
Best
Dear Hans,
Il giorno ven 3 lug 2020 alle ore 20:39 Hans Åberg
ha scritto:
> I think that may be the case: I tried with MacPorts lilypond-devel, of which
> I also made an installer, and it worked standalone, but not in Frescobaldi.
> Perhaps it runs its own convert-ly rather than the one that
On Jul 3, 2020, at 4:18 PM, Davide Liessi wrote:
> Dear David,
>
> Il giorno ven 3 lug 2020 alle ore 23:48 David F. ha scritto:
>> Frescobaldi is having problems with file paths that have question marks and
>> accented characters.
>
> tomorrow I'll test and get back to you.
>
>> This
Am 3. Juli 2020 23:33:42 MESZ schrieb Lukas-Fabian Moser :
>
>> #(define (get-scheme-markup-function func)
>> (string->symbol
>> (string-append "make-"
>> (symbol->string func)
>> "-markup")))
>
>... which should be replaced by
>
>#(define
Il giorno ven 3 lug 2020 alle ore 18:26 Zone Dremik
ha scritto:
> I just upgraded to Mac OS 10.15.5 and now convert.ly has stopped working
> entirely. I get the following error message;
> arch: posix_spawnp:
> /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7: Bad
> CPU
Am 4. Juli 2020 00:18:15 MESZ schrieb Davide Liessi :
>Dear David,
>
>Il giorno ven 3 lug 2020 alle ore 23:48 David F. ha
>scritto:
>> Frescobaldi is having problems with file paths that have question
>marks and accented characters.
>
>tomorrow I'll test and get back to you.
>
>> This problem
> On 4 Jul 2020, at 00:15, Davide Liessi wrote:
>
> Dear Hans,
>
> Il giorno ven 3 lug 2020 alle ore 20:39 Hans Åberg
> ha scritto:
>> I think that may be the case: I tried with MacPorts lilypond-devel, of which
>> I also made an installer, and it worked standalone, but not in Frescobaldi.
On Sat 04 Jul 2020 at 00:24:35 (+0200), Hans Åberg wrote:
>
> With Frescobaldi 3.1.2 using MacPorts lilypond-devel 2.21.2, not the
> installer version, on the small attached file, I got the error below.
>
> --
> Traceback (most recent call last):
> File "/opt/local/bin/convert-ly", line 65,
Hello,
1) Is there a GPL or open-source alternative for FETA fonts for accidentals
that can be used with Lilypond? (If so, is there an example of how to use
them)?
2) IMHO these default accidentals should be changed or improved. The
biggest problem is their vertical lines, which are too bold. As
25 matches
Mail list logo
