(unlurking, i didn't spend much time on lilypond recently)
On Mon, Oct 18, 2010 at 01:59:15AM +0100, Graham Percival wrote:
> > --) Two scripts still have "/usr/bin/python" lines
> > (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
> > Those should be changed to "@PYTHON@", rig
On Mon, 18 Oct 2010 15:40:54 -0700, Keith E OHara wrote:
Corresponding suggestions for vocal.itely will follow shortly.
One thing worth discussing is that I use the verb "to cue" differently from the
original author.
I believe that to cue is to *give* a signal for someone else to begin acti
On Mon, Oct 18, 2010 at 11:57 PM, Matthias Kilian
wrote:
> (unlurking, i didn't spend much time on lilypond recently)
>
>> python/ yes, since it's not something that people call manually.
>> But stuff in scripts/build/ shouldn't have @PYTHON@, otherwise
>> it'll bork if you call it manually.
>
> B
On mailing list lilypond-user, Trevor Daniels wrote:
Keith E OHara wrote Wednesday, October 06, 2010 9:40 AM
I no longer see any reason to use instrumentCueName for the labels
that identify the instrument playing cue notes.
OK. I'll see what you suggest.
I suggest (diff attached) removin
> Can you open an issue directly on the tracker and post your
> attachments there?
Done. It's issue #1335.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM.
Ian, please send me the git patch, and I'll apply it for you.
Thanks,
Patrick
http://codereview.appspot.com/2204044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/2204044/diff/14001/flower/include/guile-compatibility.hh
File flower/include/guile-compatibility.hh (right):
http://codereview.appspot.com/2204044/diff/14001/flower/include/guile-compatibility.hh#newcode28
flower/include/guile-compatibility.hh:28: #define scm_to_uns
On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
wrote:
> Il giorno lun, 18/10/2010 alle 09.02 -0700, Patrick McCarty ha scritto:
>> Yes, but unfortunately, LilyPond needs special sed treatment, since
>> many substitutions are made *after* configure time. I will need to
>> file a bug report...
>>
Il giorno lun, 18/10/2010 alle 09.02 -0700, Patrick McCarty ha scritto:
> Yes, but unfortunately, LilyPond needs special sed treatment, since
> many substitutions are made *after* configure time. I will need to
> file a bug report...
>
> Specifically, I am looking for a way to make life easier wh
On Sun, Oct 17, 2010 at 5:59 PM, Graham Percival
wrote:
> On Sun, Oct 17, 2010 at 05:38:20PM -0700, Patrick McCarty wrote:
>> --) Two scripts still have "/usr/bin/python" lines
>> (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
>> Those should be changed to "@PYTHON@", right?
On Sun, Oct 17, 2010 at 11:19 PM, Mark Polesky wrote:
> Patrick McCarty wrote:
>> Huh. I've been following the Arch Linux development list
>> for a while, but it didn't occur to me that they were
>> doing something radically different than the recommended
>> policy.
>>
>> This is the procedure th
On 10/18/10 9:21 AM, "Werner LEMBERG" wrote:
>
>
> I wrote:
>
>> I've attached fontforge images of two broken glyphs; [...]
Werner,
Can you open an issue directly on the tracker and post your attachments
there?
It seems that there ought to be three issues:
1) varsegno
2) accordion.push
3
On Mon, Oct 18, 2010 at 2:50 AM, Valentin Villenave
wrote:
> On Mon, Oct 18, 2010 at 2:38 AM, Patrick McCarty wrote:
>> Arch Linux will be migrating to Python 3 very soon, and I'm trying to
>> figure out what to do with regard to LilyPond's build system. I don't
>> know if Arch Linux is the firs
I wrote:
> I've attached fontforge images of two broken glyphs; [...]
Listmaster, please approve this mail sitting in the queue!
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Valentin Villenave wrote Monday, October 18, 2010 1:47 PM
On Mon, Oct 18, 2010 at 12:03 PM, Trevor Daniels
wrote:
There's a TODO in vocal.itely that I don't understand:
902 @c TODO: document \new Staff << Voice \lyricsto >> bug
If it really is a bug then we shouldn't be documenting
it anywa
On Mon, Oct 18, 2010 at 12:03 PM, Trevor Daniels wrote:
> There's a TODO in vocal.itely that I don't understand:
>
> 902 @c TODO: document \new Staff << Voice \lyricsto >> bug
>
> If it really is a bug then we shouldn't be documenting
> it anyway, but I'd like to know what it means first.
>
> Do y
AFAICT after a few hours of fiddling this issue is fixed, let's wait for
release to verify it (and not hopefully reopen it :-P). Let me know how
is current master. I've built and have checked both online and offline
targets, both split and big-page manuals, both docs in English and
Italian (so I'
Valentin
There's a TODO in vocal.itely that I don't understand:
902 @c TODO: document \new Staff << Voice \lyricsto >> bug
If it really is a bug then we shouldn't be documenting
it anyway, but I'd like to know what it means first.
Do you know which bug it is referring to?
Trevor
__
On Mon, Oct 18, 2010 at 2:38 AM, Patrick McCarty wrote:
> Arch Linux will be migrating to Python 3 very soon, and I'm trying to
> figure out what to do with regard to LilyPond's build system. I don't
> know if Arch Linux is the first distribution upgrading to Python 3,
> but this migration will b
19 matches
Mail list logo
