On Fri 01 Sep 2017 at 23:14:13 (+0200), David Kastrup wrote:
> Anthony Youngman writes:
> > Nothing to do with the distro - as I said I daren't upgrade. Firstly,
> > gentoo has dropped KDE4 which means major UI changes which will give
> > my wife panic attacks (slight
On 01/09/17 23:19, David Kastrup wrote:
Anthony Youngman writes:
On 01/09/17 22:14, David Kastrup wrote:
Change the memory for known good memory, and the kernel
compiled fine. No idea what Gcc does that memory test programs fail to
account for.
Have you come
Anthony Youngman writes:
> On 01/09/17 22:14, David Kastrup wrote:
>> Change the memory for known good memory, and the kernel
>> compiled fine. No idea what Gcc does that memory test programs fail to
>> account for.
>
> Have you come across the memory smashing exploit?
On 01/09/17 22:14, David Kastrup wrote:
Change the memory for known good memory, and the kernel
compiled fine. No idea what Gcc does that memory test programs fail to
account for.
Have you come across the memory smashing exploit? I can't remember much
about it, but if you can hammer memory
Hi Wol,
> I still want some way of making rehearsal marks push notes sideways out of
> the way, as it looks naff and can waste space, but it's much better.
{
\tweak RehearsalMark.extra-spacing-height #'(-inf.0 . +inf.0)
\tweak RehearsalMark.extra-spacing-width #'(-0.5 . 0.5)
\tweak
Anthony Youngman writes:
> On 01/09/17 21:36, David Kastrup wrote:
>>> I find the same thing with databases. So many people have their minds
>>> stuck in the 2-D relational world, and just cannot grasp the concept
>>> of a multi-dimensional database like Pick. Given
On 01/09/17 21:11, Anthony Youngman wrote:
The big problem I can see is if sometimes it occurs at the start of a
line, in which case the rehearsal mark will naturally move left out of
the way, and letting lily move stuff around may move it to the middle of
the line where I get a collision.
On 01/09/17 21:36, David Kastrup wrote:
I find the same thing with databases. So many people have their minds
stuck in the 2-D relational world, and just cannot grasp the concept
of a multi-dimensional database like Pick. Given that Pick is very
much list-based (unlike SQL which is set-based),
Anthony Youngman writes:
> On 01/09/17 15:17, Kieren MacMillan wrote:
>> Hi Wol,
>>
>>
>>> While it may sound weird. the reality is you probably didn't find
>>> it too hard to learn Scheme, because you're a composer not a
>>> programmer.
>>
>> Actually, I am a
On 01/09/17 15:17, Kieren MacMillan wrote:
Hi Wol,
While it may sound weird. the reality is you probably didn't find it too hard
to learn Scheme, because you're a composer not a programmer.
Actually, I am a programmer: started with BASIC (and a little assembler
language) in the early
Hi Wol,
> Given that I can't even do it ONCE successfully, what makes you think I can
> write a function to do it automatically?
Fair point. =)
> While it may sound weird. the reality is you probably didn't find it too hard
> to learn Scheme, because you're a composer not a programmer.
Anthony Youngman writes:
> On 19/08/17 15:11, Kieren MacMillan wrote:
>> Hi Wol,
>>
>>> My usual moan about colliding markups :-)
>>
>> Given how usual your moans are… ;)
>
> Mind you, don't they say moaning customers are the best sort?
Please keep this list safe to
On 19/08/17 15:11, Kieren MacMillan wrote:
Hi Wol,
My usual moan about colliding markups :-)
Given how usual your moans are… ;)
Mind you, don't they say moaning customers are the best sort? They
*want* the product to succeed.
Can I ask why you don't just write a custom function to
On 19/08/17 15:11, Kieren MacMillan wrote:
> Hi Wol,
>
>> My usual moan about colliding markups :-)
>
> Given how usual your moans are… ;)
> Can I ask why you don't just write a custom function to deal with the various
> markups automatically?
> It really wouldn't be that difficult, and would
Hi Wol,
> My usual moan about colliding markups :-)
Given how usual your moans are… ;)
Can I ask why you don't just write a custom function to deal with the various
markups automatically?
It really wouldn't be that difficult, and would reduce the moaning to zero (or
nearly).
As to your
Hi Anthony,
Does that help?
\version "2.19"
\markup\vspace #5
{
s2.*3 s1*8 \bar "||"
\tweak outside-staff-priority #0
\mark \default % 111
\tempo "Languidly"
%\once \override TextScript.outside-staff-priority = #2000
<>^\markup {
%\halign #-1.1
\small "The Last Night Of The
use the Edition engraver with for e.g.
%% example mock-up %%
\editionMod markmove 1 0/4 my.test.Score.A \once \override
Score.MetronomeMark.extra-offset = #'(2 . 0)
cheers
Arne
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Moving-a-tempo-mark-to-the-right
My usual moan about colliding markups :-)
Anyways, I've almost got this bit how I want it ... the following code
has a rehearsal mark, tempo mark, and melody name all in "the same place".
s2.*3 s1*8 \bar "||" \mark \default % 111
\tempo "Languidly"
\once \override
18 matches
Mail list logo