Hi,
2013/10/20 SoundsFromSound :
> Hello,
>
> I stumbled upon this website recently and just noticed they have this font
> offered for sale, dubbed "Lilypond look is here!"
>
> Do any of you know anything about this vendor and/or fonts? I'm
> curious...anyone try these fonts before?
>
> Paris...
Hello,
On 19/10/13 23:18, Joseph Rushton Wakeling wrote:
On 19/10/13 10:16, James wrote:
The point is that when I am managing 15 patch reviews I don't (won't)
read the
email thread [1] I look at tracker, see what has been said, I click
on Rietveld
see what has been said; it's all there in fron
James writes:
> Yes, although I don't want to be considered arrogant that it should
> only be 'acceptable to me'; but when the last Patch-nanny decided he
> was going 'spend more time with his family' (so to speak speaking) and
> wanted to pass on the role to someone else, the silence from the
>
Hello,
On 20/10/13 10:48, David Kastrup wrote:
James writes:
Yes, although I don't want to be considered arrogant that it should
only be 'acceptable to me'; but when the last Patch-nanny decided he
was going 'spend more time with his family' (so to speak speaking) and
wanted to pass on the ro
I'm getting the following when trying to compile a GUB build:
/home/gub/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/midi-item.cc:
In member function 'virtual std::string
Midi_control_function_value_change::to_string() const':
/home/gub/gub/target/freeb
"Phil Holmes" writes:
> I'm getting the following when trying to compile a GUB build:
>
> /home/gub/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/midi-item.cc:
> In member function 'virtual std::string
> Midi_control_function_value_change::to_string() cons
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc: "Heikki Tauriainen" ; "Devel"
Sent: Sunday, October 20, 2013 11:47 AM
Subject: Re: GUB failing
"Phil Holmes" writes:
I'm getting the following when trying to compile a GUB build:
/home/gub/gub/target/freebsd-x86/
Hello,
Is anyone who 'manages' the Linuxaudio website (or anyone who knows
anyone from it) able to explain if I click
http://linuxaudio.org/members
Then look for
LilyPond Software Design
Support, custom development and maintenance for the LilyPond music
typesetter
Then click on the link I
- Original Message -
From: "James"
To: "Devel"
Sent: Sunday, October 20, 2013 12:40 PM
Subject: Linux Audio link to 'Lilypond'
Hello,
Is anyone who 'manages' the Linuxaudio website (or anyone who knows anyone
from it) able to explain if I click
http://linuxaudio.org/members
Then
2013/10/19 Joseph Rushton Wakeling :
> On 16/10/13 00:11, Janek Warchoł wrote:
>>
>> I need at least 2 people who'd like to experiment with me - doing this
>> alone doesn't make sense. Colin, Joe - are you still interested?
>> Anyone else?
>
> Yup, still in. :-)
Good! I've created a test organiz
On 20/10/13 12:53, Phil Holmes wrote:
- Original Message - From: "James"
To: "Devel"
Sent: Sunday, October 20, 2013 12:40 PM
Subject: Linux Audio link to 'Lilypond'
Hello,
Is anyone who 'manages' the Linuxaudio website (or anyone who knows
anyone from it) able to explain if I click
- Original Message -
From: "James"
To: "Phil Holmes" ; "Devel"
Sent: Sunday, October 20, 2013 1:21 PM
Subject: Re: Linux Audio link to 'Lilypond'
On 20/10/13 12:53, Phil Holmes wrote:
- Original Message - From: "James"
To: "Devel"
Sent: Sunday, October 20, 2013 12:40 PM
Su
"Phil Holmes" writes:
>> lround is part of the C99 standard. For one thing, we are using C++
>> rather than C, for another, we don't rely on standards as new as that.
>>
>> --
>> David Kastrup
>
>
> So will we have to wait for Heikki to provide a fix, or are you able
> to fix it yourself?
Well
Le 05/10/2013 20:03, Werner LEMBERG disait :
Is there any workaround other than locally revert Julien's commit?
That's not a "workaround" since your fonts would all be broken.
Maybe install TeXlive2013 to a local tree and update to the newest
version using tlmgr?
It's not necessary to downl
"Phil Holmes" writes:
> So will we have to wait for Heikki to provide a fix, or are you able
> to fix it yourself?
Pushed a fix to staging.
--
David Kastrup
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinf
https://codereview.appspot.com/8647044/diff/48001/scm/music-functions.scm
File scm/music-functions.scm (right):
https://codereview.appspot.com/8647044/diff/48001/scm/music-functions.scm#newcode2118
scm/music-functions.scm:2118: (let* ((immutable
(ly:grob-basic-properties grob))
I just noticed so
On 2013/10/20 15:51:57, david.nalesnik wrote:
https://codereview.appspot.com/8647044/diff/48001/scm/music-functions.scm
File scm/music-functions.scm (right):
https://codereview.appspot.com/8647044/diff/48001/scm/music-functions.scm#newcode2118
scm/music-functions.scm:2118: (let* ((immutable
On Sun, 2013-10-20 at 15:32 +0200, David Kastrup wrote:
> "Phil Holmes" writes:
>
> > So will we have to wait for Heikki to provide a fix, or are you able
> > to fix it yourself?
>
> Pushed a fix to staging.
This patch just keeps on giving trouble... I'm very sorry for breaking
things this bad
On 20/10/13 11:15, James wrote:
Yes, although I don't want to be considered arrogant that it should only be
'acceptable to me'; but when the last Patch-nanny decided he was going 'spend
more time with his family' (so to speak speaking) and wanted to pass on the role
to someone else, the silence f
On 2013/10/20 16:15:56, dak wrote:
On 2013/10/20 15:51:57, david.nalesnik wrote:
>
https://codereview.appspot.com/8647044/diff/48001/scm/music-functions.scm
> File scm/music-functions.scm (right):
>
>
https://codereview.appspot.com/8647044/diff/48001/scm/music-functions.scm#newcode2118
> scm
Heikki Tauriainen writes:
> On Sun, 2013-10-20 at 15:32 +0200, David Kastrup wrote:
>> "Phil Holmes" writes:
>>
>> > So will we have to wait for Heikki to provide a fix, or are you able
>> > to fix it yourself?
>>
>> Pushed a fix to staging.
>
> This patch just keeps on giving trouble... I'm
On 2013/10/20 20:35:20, david.nalesnik wrote:
OK, that makes sense. I've rewritten offset according to these
guidelines. A
side benefit
is that it was no trouble to allow directed tweaks, so the following
is
possible:
{
4
4
}
Oh. Indeed.
https://codereview.appspot.com/8647044
Heikki Tauriainen writes:
> On Sun, 2013-10-20 at 15:32 +0200, David Kastrup wrote:
>> "Phil Holmes" writes:
>>
>> > So will we have to wait for Heikki to provide a fix, or are you able
>> > to fix it yourself?
>>
>> Pushed a fix to staging.
>
> This patch just keeps on giving trouble... I'm
Hi,
xpdf in Ubuntu had been unworking for quite a bit of time. I am
currently using 13.10 which has been fixed, and I _believe_ that at
least for 13.04 there is by now a backport in the repositories. Can
users of version 13.04 and/or possibly earlier versions report back
their xpdf situation?
On 10/20/13 11:39 AM, "Joseph Rushton Wakeling"
wrote:
>
>I submitted a trial merge request just so we could all explore the
>experience of
>reviewing a proposed change to the library. It's as near the GitHub
>experience
>as makes almost no difference (although there are a couple of tiny ways
On 21/10/13 04:00, Carl Sorensen wrote:
I have to say that I much prefer the Lilypond method for handling tasks
and reviews to the Gitlab method.
Can you describe in more detail what it is that you like about how Lilypond does
things, and how that is missing (or inferior) in GitLab?
However
On 10/20/13 9:04 PM, "Joseph Rushton Wakeling"
wrote:
>On 21/10/13 04:00, Carl Sorensen wrote:
>> I have to say that I much prefer the Lilypond method for handling tasks
>> and reviews to the Gitlab method.
>
>Can you describe in more detail what it is that you like about how
>Lilypond does
>thi
On 21/10/13 06:13, Carl Sorensen wrote:
Even though it can be a pain to rebase commits, when it's done on the
current Lilypond process I feel like the commit messages are much better
than the ones that show up by default on Gitlab (merging branch xyz).
I'll test this out on GitLab just to see w
On 21/10/13 07:41, Werner LEMBERG wrote:
This latter thing bothered me too initially (with GitHub) as I was
used to just pulling from the main repo to my local machine and
submitting patches via email; but I quickly realized that it was
actually sensible, and that those user repos are just plac
>> What me drives crazy is the structure of the main git repository.
>> If you follow github style, the graph gets littered with zillions
>> of `merge request' commits, one per pull request, which makes it
>> quite hard to follow the development IMHO.
>
> It's true it can get annoying if you have
30 matches
Mail list logo
