If you haven't noticed, the issue tracker now has a fantastic "grid"
display for bugs. I like having the rows for type (Collision, Defect,
Enhancement) and columns for Priority (Medium, Regression).
REGRESSIONS
http://code.google.com/p/lilypond/issues/detail?id=127
http://code.google.com/p/lil
Jared Grubb wrote:
and everything finally worked. Wow, that was an adventure getting things
working on the Mac! Thanks for your help!
I confess that I haven't really followed this, but this info would
probably be good in the docs. Could you take a look at the Install
chapter in Program Usag
Han-Wen: You appear to have misconfigured fontconfig;
You were right. It turns out FONTCONFIG_FILE was pointing to
something that didnt exist. I fixed it by doing:
* export FONTCONFIG_FILE=/etc/fonts/fonts.conf
* ./configure --with-ncsb-dir=/sw/share/ghostscript/fonts
* make && make test
John Mandereau wrote:
There's no need to add README.txt to the compiled docs, as we can
directly refer to the sources:
http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=blob_plain;f=Documentation/user/README.txt;hb=lilypond/gdp
Why not adding it on documentation-adding and "Developers
resources" (l
Han-Wen Nienhuys wrote:
Identifier isn't a good term either, that is the term for the lexical
function ("an identifier a sequence of letters").
Perhaps we should just 'variable'
I thought that "macro" was safer, since we can't redefine variables.
But I agree with your points against "macro".
Johannes Schindelin escreveu:
> Hi,
>
> On Fri, 28 Sep 2007, Han-Wen Nienhuys wrote:
>
>> When you've successfully pulled over ssh, you can create a new branch by
>> doing
>>
>> git push master:dev/rlittle
>>
>> Johannes, are there any more finegrined access control mechanisms to
>> control wh
Ralph Little escreveu:
> Hi,
> The code behind MIDI output and Performance seem to be pretty much
> tightly tied together.
>
> Was it ever intended that Performance be used for other output types?
> The Performance class contains specific MIDI references.
It was intended as such, but we never got
Graham Percival escreveu:
> Are there sound technical reasons why we call identifiers "identifiers"?
> I haven't come across the term anywhere else; how objectionable would
> it be if we called them "macros" instead?
Macros are usually reserved for a substitution mechanism where the
result of the
Is this technically a "music expression" ?
c'4
or does it need
{ c'4 }
?
I'm wondering whether I should claim that " c4 " is a music expression
or not, and while I was trying to decide, I realized that I didn't
actually know the real answer.
Cheers,
- Graham
Are there sound technical reasons why we call identifiers "identifiers"?
I haven't come across the term anywhere else; how objectionable would
it be if we called them "macros" instead?
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel
2007/9/28, Graham Percival <[EMAIL PROTECTED]>:
> > very exciting to see so many emails coming in regarding the GDP. Just
> > one question: what is the plan for merging this work? Will GDP be a
> > continuous process, or will we merge into master and delete GDP
> > afterwards?
>
> Limited term. On
Should we add "extender line" to the glossary? Is this a real musical
term, or a made-up lilypond term? Any vocalists want to comment?
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lil
Han-Wen Nienhuys wrote:
2007/9/27, Ralph Little <[EMAIL PROTECTED]>:
I currently have some scheme and C++ code for manipulating Braille.
Also, I have modified a recent git pull to replicate the Performer
implementation into an Embosser framework. This was a bigger job than I
anticipated and
On 9/28/07, Trevor Bača <[EMAIL PROTECTED]> wrote:
> On 9/21/07, Jared Grubb <[EMAIL PROTECTED]> wrote:
> > I am trying to compile Lilypond devel branches (tried 28 to 33) and I
> > *finally* got them to compile, but I cannot get them to pass the
> > test-baseline set:
> >
> > $ ./configure --with-
On 9/21/07, Jared Grubb <[EMAIL PROTECTED]> wrote:
> I am trying to compile Lilypond devel branches (tried 28 to 33) and I
> *finally* got them to compile, but I cannot get them to pass the
> test-baseline set:
>
> $ ./configure --with-ncsb-dir=/sw/share/ghostscript/fonts
> $ make
> $ make test-bas
Han-Wen Nienhuys wrote:
Hi Graham,
very exciting to see so many emails coming in regarding the GDP. Just
one question: what is the plan for merging this work? Will GDP be a
continuous process, or will we merge into master and delete GDP
afterwards?
Limited term. Once 2.12 is released, we'll m
I posted this about a week ago and was wondering if anyone had any
insight. Is the baseline test supposed to fail in the devel branch?
Jared
On 21 Sep 2007, at 07:20, Jared Grubb wrote:
I am trying to compile Lilypond devel branches (tried 28 to 33) and I
*finally* got them to compile, but I
Hi,
On Fri, 28 Sep 2007, Han-Wen Nienhuys wrote:
> When you've successfully pulled over ssh, you can create a new branch by
> doing
>
> git push master:dev/rlittle
>
> Johannes, are there any more finegrined access control mechanisms to
> control who can fastforward which branches?
You coul
Hi Graham,
very exciting to see so many emails coming in regarding the GDP. Just
one question: what is the plan for merging this work? Will GDP be a
continuous process, or will we merge into master and delete GDP
afterwards?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
2007/9/27, Ralph Little <[EMAIL PROTECTED]>:
> Sorry, some more coding questions. I've made quite a few mods to about
> 30 or so files and created a few of my own in my local git pull of
> Lilypond. It occurs to me that I should start doing it properly now ;)
>
> Should I get permission to create a
2007/9/27, Ralph Little <[EMAIL PROTECTED]>:
> I currently have some scheme and C++ code for manipulating Braille.
> Also, I have modified a recent git pull to replicate the Performer
> implementation into an Embosser framework. This was a bigger job than I
> anticipated and affects about 30 or so
21 matches
Mail list logo
