Graham Percival wrote Tuesday, July 24, 2012 10:09 AM
** Summary
Let’s decide whether to try to stabilize the syntax or not.
We /should/ try to stabilize the syntax, but trying to do this
at exactly the time when David is straightening out the
parser seems a bad idea. As yet we do not know
David Kastrup wrote Thursday, July 26, 2012 10:01 AM
Keith OHara k-ohara5...@oco.net writes:
If I make a function
\dichrom3D { c4 d e f } 3.7
that engraves a passage so that the notes appear to float 3.7 staff-spaces
above the paper when viewed with red/cyan 3D glasses,
then if I
David Kastrup wrote Thursday, July 26, 2012 11:12 AM
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Thursday, July 26, 2012 10:01 AM
Keith OHara k-ohara5...@oco.net writes:
If I make a function
\dichrom3D { c4 d e f } 3.7
that engraves a passage so
David Kastrup wrote Thursday, July 26, 2012 6:03 PM
It's much simpler than that. Expressions are greedy: what can become
a part of them, will. For that reason, it may make sense to enclose
simple music in braces, or it is likely to integrate durations and
postevents not intended for it.
David Kastrup wrote Thursday, July 26, 2012 9:16 PM
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Thursday, July 26, 2012 6:03 PM
It's much simpler than that. Expressions are greedy: what can become
a part of them, will. For that reason, it may make sense to enclose
Graham Percival wrote Tuesday, July 24, 2012 10:55 PM
grenouille.lilynet.net.
I like it. Definitely better than crapaud which has an unfortunate
connotation to English-speakers.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Graham Percival wrote Tuesday, July 17, 2012 6:32 AM
http://lilypond.org/~graham/gop/gop_3.html
*** Summary
Let’s appoint David Kastrup as the “benevolent dictator” of the
stable/2.16 git branch.
[etc]
I'm content with this proposal.
Trevor
David Kastrup wrote Monday, July 16, 2012 9:18 AM
Graham Percival gra...@percival-music.ca writes:
On Mon, Jul 16, 2012 at 02:02:31AM +0200, David Kastrup wrote:
One really ugly problem is interpreting things like 4.. Looks like a
duration, but then we have
David Kastrup wrote Thursday, July 19, 2012 2:43 PM
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Monday, July 16, 2012 9:18 AM
Graham Percival gra...@percival-music.ca writes:
On Mon, Jul 16, 2012 at 02:02:31AM +0200, David Kastrup wrote:
One really ugly problem
David Kastrup wrote Thursday, July 19, 2012 5:18 PM
The original proposal was to rule out 0. and .5 as real numbers. This
will introduce foreseen problems: things will break where those had been
used (there are definitely uses of 0. in our own code base but not for
.5). A few of those
David Kastrup wrote Thursday, July 19, 2012 6:53 PM
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Thursday, July 19, 2012 5:18 PM
\relative c' { b = 4. }
(quick: can you guess what this does?).
:) Well, I guessed correctly the 4. would be interpreted as a duration
Phil Holmes wrote Monday, July 16, 2012 4:09 PM
http://lsr.dsi.unimi.it/LSR/Item?id=190. Even with the segno not being
shifted off the left of the page, I don't understand what this demonstrates.
If I was given this to sing, I wouldn't have a clue.
Phil Holmes wrote Monday, July 16, 2012 5:35 PM
From: Trevor Daniels t.dani...@treda.co.uk
To: Phil Holmes em...@philholmes.net; Devel lilypond-devel@gnu.org
Sent: Monday, July 16, 2012 4:37 PM
Subject: Re: Snippet deletion countdown
Phil Holmes wrote Monday, July 16, 2012 4:09 PM
http
David Kastrup wrote Saturday, July 14, 2012 9:30 AM
Graham Percival gra...@percival-music.ca writes:
Let’s appoint David Kastrup as the “benevolent dictator” of the
stable/2.16 git branch.
I'm happy to go along with this. It's hardly a policy, but it
will definitely move things along!
David Kastrup wrote Friday, July 13, 2012 4:27 PM
Janek Warchoł janek.lilyp...@gmail.com writes:
This is important, too, because Graham won't always be the Project
Manager. It's also not guaranteed that there'll always be an
experienced developer with sufficient time to handle release
Phil Holmes wrote Friday, July 13, 2012 5:56 PM
From: Thomas Morley thomasmorle...@googlemail.com
What should I do?
Run the command
git cl issue 6352049
and then repeat
git cl upload
git cl needs to be told the issue number on Rietveld, if it's different from
the most
d...@gnu.org wrote Thursday, July 12, 2012 10:35 AM
On 2012/07/12 09:31:40, Trevor Daniels wrote:
http://codereview.appspot.com/6345086/diff/5001/Documentation/notation/changing-defaults.itely#newcode844
Documentation/notation/changing-defaults.itely:844: \override Stem
#'thickness = #4.0
David Kastrup wrote Tuesday, July 10, 2012 12:21 PM
tdaniels...@gmail.com: Repeat Dots and
Staff Size in 2.15.41
http://code.google.com/p/lilypond/issues/detail?id=2648
This bug first appeared in 2.15.40, so is a critical regression.
I mean, we have too few categories for regressions. I
David Kastrup wrote Tuesday, July 10, 2012 1:19 PM
Trevor Daniels t.dani...@treda.co.uk writes:
We have the technology to identify the commits that introduce bugs
fairly easily. Perhaps once the first release candidate is made we
simply say any commit that introduced a critical
Phil Holmes wrote Tuesday, July 10, 2012 12:03 PM
Kind-of fixed. The way the files are presented is aimed at ensuring no-one
rates a regtest more than once, and that they get the least-rated files
presented to them in a random order. The only way I seem to be able to get
this to work is
David Kastrup wrote Tuesday, July 10, 2012 4:33 PM
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Tuesday, July 10, 2012 1:19 PM
Trevor Daniels t.dani...@treda.co.uk writes:
We have the technology to identify the commits that introduce bugs
fairly easily. Perhaps
Graham Percival wrote Tuesday, June 26, 2012 9:55 PM
*** Summary
Let’s drop the “any unintended change” thing, and go totally with
the regression tests. Tests pass? We can make a stable release.
Also, let’s have an official roadmap.
Rather than discussing each point separately below I
gra...@percival-music.ca wrote Monday, July 09, 2012 5:55 AM
Ignore my other message that talked about using git-cl to upload
an edited patch; I hadn't noticed that you did that here.
OK. It was not worth the effort for a two-word change.
I uploaded a new patch-set here as the changes were
My first reply, identifying this bug as a regression ...
- Original Message -
From: Trevor Daniels t.dani...@treda.co.uk
To: David Stocker notesetters...@gmail.com; lilypond-u...@gnu.org
Sent: Sunday, July 08, 2012 12:48 PM
Subject: Re: Repeat Dots and Staff Size in 2.15.41
Damn
My second reply, identifying a possible source of the bug.
Trevor
- Original Message -
From: Trevor Daniels t.dani...@treda.co.uk
To: Trevor Daniels t.dani...@treda.co.uk; David Stocker
notesetters...@gmail.com; lilypond-u...@gnu.org
Sent: Sunday, July 08, 2012 12:52 PM
Subject: Re
Phil Holmes wrote Sunday, July 08, 2012 4:43 PM
As I said in an earlier mail, I'd like to include the cross-staff stem
functions that Pavel developed as a part of standard lily functionality. It
relies on quite a bit of scheme and a final function like this:
crossStaff =
Phil Holmes wrote Sunday, July 08, 2012 9:13 PM
From: Trevor Daniels t.dani...@treda.co.uk
To: Phil Holmes em...@philholmes.net; Devel lilypond-devel@gnu.org
Sent: Sunday, July 08, 2012 9:05 PM
Subject: Re: Cross-staff stems again
music-functions-init.ly looks good. You'll need to add
David, you wrote Saturday, July 07, 2012 5:13 AM
Trevor Daniels t.dani...@treda.co.uk writes:
Although I should have noticed the error when git cl asked me to
confirm the issue number, why did it pick the wrong one initially?
How does it make its initial guess?
Simple enough. It looks
Trevor Daniels wrote Friday, July 06, 2012 11:18 AM
I'll tart it up a bit and add it to the LSR shortly.
Added to LSR as Creating a short ossia section with lyrics
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org
This is interesting. This should refer to issue 2560, as correctly entered in
the commit message, but git cl for some reason selected issue 2540, and I
failed to notice the error, and even copied it when composing my text.
As I'm still feeling my way with the new (for me) git cl, could someone
Trevor Daniels wrote Friday, July 06, 2012 11:21 PM
This is interesting. This should refer to issue 2560, as correctly entered
in the commit message, but git cl for some reason selected issue 2540, and I
failed to notice the error, and even copied it when composing my text.
Although I
I just made a mistake with git rebase and lost a branch I'd like to recover,
but I don't know how or even if it is possible.
Here's what I did.
I checked out branch A
then entered
git rebase master
This gave merge conflicts, and the usual three options.
I decided not to resolve the merge
David Kastrup wrote Tuesday, July 03, 2012 9:26 PM
Trevor Daniels t.dani...@treda.co.uk writes:
$ git cl upload master
WARNING: terminal is not fully functional
Documentation/notation/input.itely | 56 +
1 files changed, 56 insertions(+), 0 deletions(-)
'vi
John Mandereau wrote Wednesday, July 04, 2012 10:57 AM
Subject: Re: Help with git rebase recovery, please
Il giorno mer, 04/07/2012 alle 10.31 +0100, Trevor Daniels ha scritto:
So, can I now recover my original branch A?
Look at what
git reflog
says, pick out the truncated committish
Trevor Daniels wrote Tuesday, July 03, 2012 11:49 PM
But some changes to git-cl were necessary to run under
Windows, even with 2.7. I'll document these more clearly
tomorrow.
Here's what I found necessary, or at least the easiest way,
to run git-cl under Windows. Surprisingly easy
Has anyone managed to run git-cl under Windows successfully?
The version from github.com/gperciva/git-cl.git ships without the readline
module. It is not required for Unixes as it is included with Unix python, I
believe. But it is not included with the Windows version of python. There is
a
David Kastrup wrote Tuesday, July 03, 2012 4:34 PM
Namely, git-cl first tries importing readline unconditionally, then it
tries importing it again conditionally.
That does not look all too clever. Perhaps removing the unconditional
import is all that is needed?
Yes, this seems to bypass
David Kastrup wrote Tuesday, July 03, 2012 10:46 PM
Graham Percival gra...@percival-music.ca writes:
On Tue, Jul 03, 2012 at 10:26:18PM +0200, David Kastrup wrote:
Trevor Daniels t.dani...@treda.co.uk writes:
Description empty; aborting.
That just means that git-cl called what
Graham Percival wrote Tuesday, July 03, 2012 2:36 PM
On Tue, Jul 03, 2012 at 11:40:58AM +0100, Trevor Daniels wrote:
The version from github.com/gperciva/git-cl.git ships without
the readline module. It is not required for Unixes as it is
included with Unix python, I believe.
Hmm
Thomas Morley wrote Friday, June 29, 2012 10:32 AM
Of course all features (old and new) should be documented.
But, AFAICT, non of the possibilities offered in /ly/titling-init.ly
(i.e. first-page, last-page, not-first-page, part-last-page) is
documented anywhere in LM or NR.
Well, they
Colin Hall wrote Tuesday, June 26, 2012 5:44 PM
On Tue, Jun 26, 2012 at 06:26:34PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Mailing list arguments are a trickier issue. It???s clearly a big
problem, but this isn???t something we can fix by waving a
Graham Percival wrote Wednesday, June 13, 2012 3:52 AM
If you were a lilypond developer at any point in time, was your
motivation to work on lilypond reduced due to problematic
reasons which you are comfortable sharing with us in this
pseudo-anonymous fashion? What were those reasons or the
m...@mikesolomon.org
From: Thierry Coduys thierry.cod...@le-hub.org
The jury wishes to congratulate you on your LilyPond open source software,
that won the First Prize at the LoMus 2012 contest.
A cheque or bank transfer of 2000 € will be sent to you by the AFIM
w00t!
Mazal
Łukasz Czerwiński wrote Sunday, April 29, 2012 12:18 PM
Thanks all three of you for your immediate reply! :) I didn't know
about the glossary. One problem with it is that for musical
terms, except for notes and rests, it works only it the opposite
direction: English - other language, while
Keith OHara wrote Tuesday, May 08, 2012 3:48 AM
Trevor Daniels t.daniels at treda.co.uk writes:
Yes, I now agree. We can't continue to advocate s1*0
in the docs now we are aware of these pitfalls.
I suggest we mention that takes no time in NR 1.5.1
Chorded Notes, but avoid
David Kastrup wrote Tuesday, May 08, 2012 11:06 AM
Trevor Daniels t.dani...@treda.co.uk writes:
Keith OHara wrote Tuesday, May 08, 2012 3:48 AM
I suggest we mention that takes no time in NR 1.5.1 Chorded
Notes, but avoid it in the examples.
Most of the visible uses of s1*0 in the docs
James wrote Monday, May 07, 2012 9:11 AM
Also isn't this a really a GLISS topic?
No. You miss the point: we're not talking about something
new: has been valid syntax for years, but its semantics
are not documented. They should be.
Trevor
Graham Percival wrote Monday, May 07, 2012 10:29 AM
Leaving that question aside, we're talking about the preferred
method of having something which does not tamper with the current
duration but does take post-events.
A number of people think that is the ideal tool for a
non-duration
Nicolas Sceaux wrote Monday, May 07, 2012 8:32 PM
Le 7 mai 2012 à 13:58, David Kastrup a écrit :
\relative c' {
e2\p\ d\ s1*0\!
} \addlyrics { Oh no }
\relative c' {
e2\p\ d\ \!
} \addlyrics { Oh yes }
I think that closes the s1*0 vs. debate.
Because of its unexpected side effects, the
David Kastrup wrote Sunday, May 06, 2012 2:57 AM
In fact, isn't generally prettier than s1*0? Should we be using it
in code and documentation rather than s1*0?
Definitely prettier, but maybe not so transparent as s1*0.
It is not intuitively obvious that an empty chord takes no
time and
David Kastrup wrote Sunday, May 06, 2012 9:34 AM
Quick: tell me what you would expect without too much thinking (imagine
you are a naive user) from the following:
\new Staff
\relative c'' { c4 d e f s1*0-\markup Oops c d e f g1 } \\
\relative c' { c4 d e f -\markup Wow c d e f g1 }
That's
David Kastrup wrote Sunday, May 06, 2012 4:44 PM
Trevor Daniels t.dani...@treda.co.uk writes:
Actually, I don't think s1*0 appears in the docs.
Documentation/notation/vocal.itely: s1*0^\markup { \right-align { \tiny
Flute } }
Documentation/notation/vocal.itely: s1*0_\markup { \right
Graham Percival wrote Sunday, May 06, 2012 10:24 PM
I'm still not happy with an empty chord, especially in the
Learning Manual. I think it leads to the perlization of
lilypond, where we end up looking like a ridiculous language like
Haskell.
My point really is that exists now, so there
d...@gnu.org wrote Friday, May 04, 2012 8:43 PM
Ok, everybody will love me for my late thinking again. But here we go:
:)
we have two cases of footnotes: one that will attach itself to whatever
happens at a given point of time, being an independent event.
I propose we _always_ let
them
Werner LEMBERG wrote Friday, April 27, 2012 6:29 AM
I've received a couple e-mails from colleagues and one nudge from
Valentin about:
http://concours.afim-asso.org/
Aah, very nice! Yes, participating in this contest would be a good
thing; and thanks for your offer to writing up the
m...@apollinemike.com wrote Friday, April 27, 2012 8:39 AM
On 27 avr. 2012, at 09:33, Trevor Daniels wrote:
But it seems the closing date has passed - wasn't it 25 April?
It's extended till the 29th.
Ah, good! If they needed to do that the chance
of winning is somewhat increased
Graham Percival wrote Thursday, April 26, 2012 7:07 AM
The Birmingham Amateur Theatre is presenting Penzance Pirates,
starring our documentation editor Trevor Daniels as the talking lion![1]
[1] this is (probably) not true.
Amazingly, there's an element of truth in it. Read Bicester
Carl Sorensen wrote Monday, April 23, 2012 9:40 PM
Congratulations on having your Lyrics project accepted for Google Summer
of Code!
Wow, congratulations from me too! You really did put the hours in to
generate a great submission - in the middle of your exams too - so you
definitely
Aleksandr Andreev wrote Monday, April 09, 2012 12:39 AM
Looks like the trick with stencil-whiteout does not work in all cases.
Here are two examples.
[snip]
In the second example, the bar line is whited out. But in the first
example, it isn't. Anyone have any pointers as to how to debug
Hi Janek
An impressive collection of suggested enhancements! I hope your exams don't
suffer!
Most look excellent to me, but I have comments on a couple of them which
I'll add to the issues themselves.
Trevor
- Original Message -
From: Janek Warchoł janek.lilyp...@gmail.com
To:
Phil Holmes wrote Thursday, March 15, 2012 8:59 AM
From: Trevor Daniels t.dani...@treda.co.uk
Carl Sorensen wrote Wednesday, March 14, 2012 6:01 PM
So it would be nice to have a feature added to midi2ly that would
automatically create voiceFive, voiceSix, etc. if needed.
Exactly! Having
Julien Rioux wrote Wednesday, March 14, 2012 10:37 AM
On Wed, Mar 14, 2012 at 9:56 AM, Phil Holmes em...@philholmes.net wrote:
- Original Message - From: Julien Rioux
julien.ri...@gmail.com
To: Phil Holmes em...@philholmes.net
The problem with this one is that Lilypond (like
Phil Holmes wrote Wednesday, March 14, 2012 12:00 PM
From: Trevor Daniels t.dani...@treda.co.uk
To: Julien Rioux julien.ri...@gmail.com; Phil Holmes
em...@philholmes.net
Cc: lilypond-devel@gnu.org; re...@codereview-hr.appspotmail.com
Sent: Wednesday, March 14, 2012 11:41 AM
Subject: Re
Carl Sorensen wrote Wednesday, March 14, 2012 6:01 PM
On 3/14/12 11:48 AM, Phil Holmes m...@philholmes.net wrote:
I've looked at midi2ly and it uses explicit instantiation of voices,
which
is what we normally advise. My understanding is that there are only 4
explicit voices - voiceFive does
Keith, you wrote Tuesday, March 13, 2012 5:53 AM
Subject: Re: Doc: Learning: Use voices in the intended order. (issue
5507050)
On 2012/03/10 12:36:05, Trevor Daniels wrote:
I could see no reason for this patch causing problems
I had mis-spelled the option to ignore-collisions, which
Phil Holmes wrote Sunday, March 11, 2012 3:10 PM
I think I have GUB running properly. I gave up trying to get it working on
64-bit Ubuntu and created a new VirtualBox VM with lilydev 1.1 as the OS.
Congratulations! One of the select few!
Trevor
Phil Holmes wrote Sunday, March 11, 2012 4:11 PM
I've just run my pixel comparator and discovered that the regtest
whiteout.ly has a habit of changing between releases - sometimes the not
stem is there, sometimes it's whited out. The description says:
The whiteout command underlays a
Trevor Daniels wrote Sunday, March 11, 2012 4:23 PM
Phil Holmes wrote Sunday, March 11, 2012 4:11 PM
I've just run my pixel comparator and discovered that the regtest
whiteout.ly has a habit of changing between releases - sometimes the not
stem is there, sometimes it's whited out.
Seems
Hi Phil, you wrote Saturday, March 10, 2012 10:16 AM
Once you have a successful make doc, you might be surprised how little
time it takes to remake to check changes now. On my admittedly quick
machine, make -j9 CPU_COUNT=9 LANGS='' doc takes about 5 seconds.
It's certainly a lot better than
I've just pushed some fixes to auxiliar/doc-section.sh to staging, as
several things seemed to have gone wrong with it since I last used it. The
script is intended to be used for quickly checking changes made to the
English docs. It compiles a section of the docs to html in a minute or so
Valentin, you wrote Friday, March 02, 2012 10:05 AM
On Fri, Mar 2, 2012 at 12:29 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Valentin - could they not be retrieved from backup if you ask
nicely?
I hope so, but Graham seemed to imply that there actually was NO backup.
Surely
Janek Warchoł wrote Thursday, March 01, 2012 12:01 AM
The bad news is that for scores containing a lot of lyrics (like my
SATB pieces) compilation times are now 3-4 times longer than wiith
master. For instrumental scores the situation look better, it's 1.5-2
times longer. I can live with
Valentin Villenave wrote Thursday, March 01, 2012 11:05 PM
On Thu, Mar 1, 2012 at 11:26 PM, Graham Percival
gra...@percival-music.ca wrote:
Umm, no? I mean, literally no? Other than the first+last
releases of each stable branch, those files are gone.
Then I'm sorry to hear that. In case my
David Kastrup wrote Wednesday, February 01, 2012 7:00 AM
Trevor Daniels t.dani...@treda.co.uk writes:
David Kastrup wrote Tuesday, January 31, 2012 10:13 PM
Any suggestion of how to do the documentation part of issue 2263
differently? That \new Voice sticks out like a wart.
From
David Kastrup wrote Tuesday, January 31, 2012 12:47 PM
What would you expect the following to do?
\new StaffGroup { \relative c' { \relative c' { c2 } c } }
It does pretty much what I expected, but then I have been explaining the
drawbacks of implicit contexts for some years now.
I
David Kastrup wrote Tuesday, January 31, 2012 2:31 PM
Trevor Daniels t.dani...@treda.co.uk writes:
No, me neither, but leaving Voice contexts to be implied usually works
well, eg with Staff rather than StaffGroup.
Why would you want to have the above end up in _two_ different voices
David Kastrup wrote Tuesday, January 31, 2012 10:13 PM
Any suggestion of how to do the documentation part of issue 2263
differently? That \new Voice sticks out like a wart.
From Documentation/notation/simultaneous.itely (as proposed):
Since nested instances of @code{\relative} don't affect
Eluze wrote Tuesday, January 31, 2012 10:58 PM
Trevor Daniels wrote:
David Kastrup wrote Tuesday, January 31, 2012 2:31 PM
Trevor Daniels t.dani...@treda.co.uk writes:
No, me neither, but leaving Voice contexts to be implied usually works
well, eg with Staff rather than StaffGroup.
Why
David, you wrote Friday, January 27, 2012 2:01 PM
David Kastrup d...@gnu.org writes:
It would be possible to let q set a parser variable that will optimize
this pass away when unset. The drawback would be that ChordRepeat
events entering via different channels (#{ c e g q #} uses its own
Carl, Although I'm not a current developer, I'd like to comment.
In general I agree, but with the caveats below:
Carl Sorensen wrote Tuesday, January 17, 2012 1:27 AM
So after hearing from most of the currently-active developers, I think a
reasonable goal for 2.16 would be:
1) Work through
Graham Percival wrote Sunday, January 15, 2012 8:23 AM
I believe this will work out-of-the-box for any .TELY file,
regardless of whether texi2pdf is in the path or not. Please
test.
http://lilypond.org/~graham/lilypond-2.15.25-4.mingw.exe
Well, not quite. Two problems:
1. should be
Graham, you wrote Sunday, January 15, 2012 9:32 AM
I believe this will at least produce the default line-widths
out-of-the-box for any texinfo or latex file, regardless of
whether texi2pdf is in the path or not. Please test.
http://lilypond.org/~graham/lilypond-2.15.25-5.mingw.exe
I
Graham, you wrote Saturday, January 14, 2012 8:07 AM
I've just realized that I've been debugging this a very silly way;
there's no reason to produce a new binary each time.
Could somebody on windows send me lilypond-book.py ? I only need
that file... actually, I only need the first 20 lines
Graham, you wrote Saturday, January 14, 2012 9:43 AM
Excellent, we're in business. Please put the attached file in
the same directory as lilypond-book, then run
test-subprocess.py
I expect 1 and 2 to work. If 3 works, we're golden. If 4
succeeds then something weirder than I think is
Trevor Daniels wrote Saturday, January 14, 2012 10:31 AM
Graham, you wrote Saturday, January 14, 2012 9:43 AM
Excellent, we're in business. Please put the attached file in
the same directory as lilypond-book, then run
test-subprocess.py
I expect 1 and 2 to work. If 3 works, we're golden
Graham, you wrote Saturday, January 14, 2012 10:38 AM
ok, could you paste these 3 lines to the top of the main()
function, then run the result? you'll need to CTRL-C when it gets
to step 2, but if this looks ok (please check log.txt) then we're
still good.
cmd = dir log.txt
ret =
Graham Percival wrote Saturday, January 14, 2012 10:55 AM
oh mao... ok, does window still have a C:\TEMP ? There's got to
be some directory you can write to... if not, please create such a
directory. I recommend C:\TEMP so that you don't need to type a
lot.
Hhm. There seems to be
Trevor Daniels wrote Saturday, January 14, 2012 12:10 PM
Having done that I then get
$ python test-subprocess2.py
Begin testing 7
0. return code: 0
sleep
Traceback (most recent call last):
File test-subprocess2.py, line 48, in ?
main ()
File test-subprocess2.py, line 41, in main
Graham, you wrote Saturday, January 14, 2012 12:57 PM
Please change line 36:
cmd = sleep 1 dir
into this:
cmd = dir
and try again?
Done; no change. I don't think that was the problem - it'd
got past that and printed sleep from line 40. It seems to
be choking on line 41 -
Graham, you wrote Saturday, January 14, 2012 2:57 PM
ok, here's a new method. os.system() seems much more reliable
than subprocess for python 2.4.2 in windows, so let's see if we
can get that working.
Yes, I think that's how Reinhold fixed a similar problem with subprocess a
year or two
Graham, you wrote Friday, January 13, 2012 8:41 AM
As a cheap experiment, could you add this:
### EXPERIMENTAL HACK: see if this makes mingw behave better?
time.sleep(1)
immediately between the
proc = ...
and
(parameter_string, error_string) = proc.communicate ()
lines?
oh, and
Sorry for the late response - my mail provider lost one of
his RAID drives this morning, so I had no mail for some
hours.
Graham, you wrote Friday, January 13, 2012 9:02 AM
I believe that this should work out of the box on any windows
computer which does **NOT** have texi2pdf or texi2dvi
Graham, you wrote Thursday, January 12, 2012 6:22 AM
I expect to have that sleep(0.001) error. I do not expect any
other errors.
http://lilypond.org/~graham/lilypond-2.15.25-2.mingw.exe
What's the exact error you see when you try this one? I
know/expect that it barfs in threading.py, but
Graham Percival wrote Wednesday, January 11, 2012 6:21 AM
Please test this version:
http://lilypond.org/~graham/lilypond-2.15.25-1.mingw.exe
add it to your PATH, then me exactly what you see when you try to
call lilypond-book.
Running lilypond-book
lilypond-book.py (GNU LilyPond) 2.15.25
Graham, you wrote Wednesday, January 11, 2012 10:43 AM
Just as a quick check of the ridiculous: could you open up
lilypond-book.py and confirm that line 213 is:
stdout=subprocess.PIPE, stderr=subprocess.PIPE)
there might be an off-by-one thing happening.
Yes it is.
if that's the
Trevor Daniels wrote
Running lilypond-book
lilypond-book.py (GNU LilyPond) 2.15.25
Reading
C:/Users/Trevor/LilyPond-git/Documentation/notation/contemporary.itely..
.
Running texi2pdf on file c:\users\trevor\appdata\local\temp\tmpt4vqnk.texi
to de
tect default page settings.
Traceback
Julien Rioux
I would try removing one-by-one the arguments from the subprocess.Popen
call, e.g., remove universal_newlines=True, remove shell=True, remove
stderr=subprocess.PIPE, etc. one-by-one. See if you get further.
Yes, I tried this earlier. Setting universal_newlines False bypasses
Phil Holmes wrote Wednesday, January 11, 2012 5:34 PM
I'd be a little wary of simply making this work on Windows by commenting
code out, without ensuring there is no effect on other platforms. I'd be
even more wary of doing this in a Python delivered file. It'd be a shame
to break the doc
Trevor Daniels wrote Wednesday, January 11, 2012 6:49 PM
To carry things to their logical conclusion I'm installing MikTeX to
see if it is possible to make Reinhold's code work as intended on
Windows. Even if it does, I could not recommend downloading
167Mbytes of MikTeX just to pick up
Trevor Daniels wrote Wednesday, January 11, 2012 11:23 PM
Well, MikTex contains texi2dvi.exe, so I renamed this to texi2pdf.exe
and added its directory to the MinGW path. lilypond-book and
Reinhold's code then seems to work correctly, provided I comment
out the _sleep call in threading.py
401 - 500 of 1527 matches
Mail list logo
