Am 03.08.2016 um 18:07 schrieb Pierre-Luc Gauthier:
2016-08-03 11:03 GMT-04:00 Andrew Bernard :
The concept is fine I am sure, but the execution difficult, and acceptance
problematical.
I know it’s difficult but does that mean one cannot try?
Logo design is fraught with difficulty, and you w
2016-08-03 11:03 GMT-04:00 Andrew Bernard :
> The concept is fine I am sure, but the execution difficult, and acceptance
> problematical.
So as with most artistic and identity related questions. :-(
> Logo design is fraught with difficulty, and you will inevitably end up with
> something half the
Hi Malte,
The concept is fine I am sure, but the execution difficult, and acceptance
problematical. Take for example the massive amount of work that went into,
just by way of pertinent example, the Creative Commons logo:
https://creativecommons.org/2015/03/25/a-masterwork-in-simplicity-the-story-
Am 03.08.2016 um 16:13 schrieb Malte Meyn:
b/w vector graphic as a logo for LilyPond
This could also be part of the Feta font.
\markup \musicglyph #"logo.waterlily"
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/
Hi Malte,
> wouldn’t it be nice to have an official b/w vector graphic as a logo for
> LilyPond? Any opinions?
I *love* this idea! Currently, the standard Colophon in all of my scores is
…but I would *love* to have a little Lilypond logo there!
Thanks!
Kieren.
Hi list,
I’m planning to publish an arrangement of Grieg’s Holberg Suite on
IMSLP. I experimented with a copyright \header field which contains not
only text but also the Creative Commons logo. Then I thought that the
tagline could have such an eye catcher too, but there seems to be no
LilyPo
Vinny writes:
> The rationale as to why the weird bar numbers in case you want some
> background and/or have a better idea:
>
>
> I'm part of a /taiko//percussion group that plays pieces composed for
> several instruments which always have repeats at different places and even
> of different lengt
Harm:
This [code, and indeed entire thread] is just awesome.
I will probably never use what’s here… but I’m just so happy that it exists,
and that people like you exist.
Thanks!
K.
On Aug 3, 2016, at 9:16 AM, Thomas Morley wrote:
> My previous code aimed at setting the beam-segments directly.
Hi everybody,
I have a question that may be difficult to express in general terms at
first, so I'm going to start with a minimalistic example:
\time 3/4
% Bar #1
\repeat volta 4 { c4 e g }
% Bar #2
\PhraseTwo
As it is, PhraseTwo starts at bar 2 because it follows bar 1. Fair enough.
But when
Hi Andrew,
2016-08-02 19:13 GMT+02:00 Thomas Morley :
> 2016-08-02 17:13 GMT+02:00 Andrew Bernard :
>> Hi Harm,
>>
>> Thank you for this. I suppose I was not clear enough, as usual. I
>> explicitly need the beams on the individual note to have a longer
>> beamlet on the top, with the rest being sh
Hi David,
> "restart"? LilyPond is a batch program so you need to "restart" it for every
> try anyway.
That’s what I thought; thanks for the confirmation.
> If you taught Frescobaldi to call a particular version of LilyPond
> depending on the \version header, that is what will happen, and ever
Kieren MacMillan writes:
> Hi Harm,
>
> Do I have to recompile or restart Lilypond after modifying a file in scm/?
> Perhaps that’s the problem…?
"restart"? LilyPond is a batch program so you need to "restart" it for
every try anyway. It depends on where/how you run LilyPond whether your
chang
Hi Harm,
Do I have to recompile or restart Lilypond after modifying a file in scm/?
Perhaps that’s the problem…?
Thanks,
Kieren.
Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info
__
Hi Harm,
Thanks for the explanation(s).
> The hash isn't a scheme-thingy here in a .ly-file! It just tells the
> _LilyPond_-parser "scheme follows”.
> But if you use it this way in a .scm-file it throws an error.
That was my original understanding; thanks for the confirmation.
> it usually make
2016-08-03 12:52 GMT+02:00 David Kastrup :
>
> Xpost and Fup2 lilypond-devel
>
> Thomas Morley writes:
>
>> Some remarks/TODOs, especially:
>> Why I cannot _create_ a MultiMeasureRestText-grob via
>> `ly:engraver-make-grob'?
>> It works for TextScript ...
>
> Do you have an example of what doesn'
Kieren MacMillan writes:
> Hi David and Harm,
>
> Thanks for the replies.
>
> On Aug 3, 2016, at 1:04 AM, David Kastrup wrote:
>
>> I think Harm's example was supposed to demonstrate that
>> there is nothing basically wrong with the approach
>
> Well at tleast that’s something I can take to hear
2016-08-03 12:34 GMT+02:00 Kieren MacMillan :
> Hi Harm,
>
> On Aug 3, 2016, at 1:05 AM, Thomas Morley wrote:
>> Regarding scheme, there is no difference.
>
> So
>
> (1) the leading hash (which your example has and mine doesn’t) makes no
> difference; and
The hash isn't a scheme-thingy here in a
Am 3. August 2016 12:34:28 MESZ, schrieb Kieren MacMillan
:
>Hi Harm,
>
>On Aug 3, 2016, at 1:05 AM, Thomas Morley
>wrote:
>> Regarding scheme, there is no difference.
>
>So
>
>(1) the leading hash (which your example has and mine doesn’t) makes no
>difference;
The hash switches from LilyPond
Xpost and Fup2 lilypond-devel
Thomas Morley writes:
> Some remarks/TODOs, especially:
> Why I cannot _create_ a MultiMeasureRestText-grob via `ly:engraver-make-grob'?
> It works for TextScript ...
Do you have an example of what doesn't work?
> %% How to do?
> %% It worked with simple TextScri
Hi Harm,
On Aug 3, 2016, at 1:05 AM, Thomas Morley wrote:
> Regarding scheme, there is no difference.
So
(1) the leading hash (which your example has and mine doesn’t) makes no
difference; and
(2) the functions ‘define' and 'define-public' are identical
?
Perhaps learning Scheme is going to
Hi David and Harm,
Thanks for the replies.
On Aug 3, 2016, at 1:04 AM, David Kastrup wrote:
> I think Harm's example was supposed to demonstrate that
> there is nothing basically wrong with the approach
Well at tleast that’s something I can take to heart as I try to teach myself
Scheme…
> so
21 matches
Mail list logo
