I posted my first patch to Rietveld last night, but nothing seems to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com/164063. Here's what it does.
This is the first patch of a series aiming eventually to enable
Baroque lute tablature to be
Trevor Daniels schrieb:
I posted my first patch to Rietveld last night, but nothing seems to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com/164063. Here's what it does.
This is the first patch of a series aiming eventually to enable
Baroque
Trevor Daniels t.dani...@treda.co.uk writes:
I posted my first patch to Rietveld last night, but nothing seems to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com/164063. Here's what it does.
This is the first patch of a series aiming eventually
David Kastrup wrote Wednesday, December 02, 2009 11:15 AM
Trevor Daniels t.dani...@treda.co.uk writes:
I posted my first patch to Rietveld last night, but nothing seems
to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com/164063. Here's what it
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor it
brought up was nano (to edit the list of commits) and
then vi (to edit the commit messages). Not being
familiar with either, the way to
On 12/2/09 2:26 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
I posted my first patch to Rietveld last night, but nothing seems to
have been cc'd to the list. Not sure what I did wrong. It's at
http://codereview.appspot.com/164063. Here's what it does.
This is the second person who
On Wed, Dec 02, 2009 at 12:38:54PM -, Trevor Daniels wrote:
It it possible to configure git to use another editor,
like the ubuntu default, gedit, for these?
export VISUAL=gedit
or something like that. You might be able to set EDITOR instead.
Cheers,
- Graham
Carl Sorensen wrote Wednesday, December 02, 2009 3:21 PM
On 12/2/09 2:26 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
I posted my first patch to Rietveld last night, but nothing seems
to
have been cc'd to the list. Not sure what I did wrong. It's at
Great job, Trevor!
On 12/2/09 2:26 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Following a suggestion by Neil I have also made the whiteout behind
all fret numbers optional. This is controlled by the 'whiteout
property of TabNoteHead. The default is #t to preserve the current
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 2. Dezember 2009 13:38:54 schrieb Trevor Daniels:
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor it
brought up was nano (to
Graham Percival wrote:
Despite my agreements to both paragraphs above, I agree more with
the first than the second. Namely, I don't see the point of
keeping a list of stuff to add to the docs; that's a recipe for
not getting anything done.
I think that can depend on a particular person's work
[whoops! sent only to Trevor the first time...]
On Wed, Dec 2, 2009 at 6:38 AM, Trevor Daniels t.dani...@treda.co.ukwrote:
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor it
brought up
Hi,
On Wed, 2 Dec 2009, Trevor Daniels wrote:
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor it
brought up was nano (to edit the list of commits) and
then vi (to edit the commit
Hi Jonathan, you wrote Wednesday, December 02, 2009 4:27 PM
On Wed, Dec 2, 2009 at 6:38 AM, Trevor Daniels
t.dani...@treda.co.ukwrote:
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor
At 12:38 on 02 Dec 2009, Trevor Daniels wrote:
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor it
brought up was nano (to edit the list of commits) and
then vi (to edit the commit
Carl Sorensen wrote Wednesday, December 02, 2009 3:40 PM
On 12/2/09 2:26 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Following a suggestion by Neil I have also made the whiteout
behind
all fret numbers optional. This is controlled by the 'whiteout
property of TabNoteHead. The
Trevor Daniels t.dani...@treda.co.uk writes:
I used git rebase -i to combine several commits into
one for the first time recently. This was in ubuntu.
It threw me for a while because the first editor it
brought up was nano (to edit the list of commits) and
then vi (to edit the commit
2009/12/2 Carl Sorensen c_soren...@byu.edu:
But it seems to me that if outside-staff-priority is set for one grob, and
not for the other, then they should be compared by script-priority, since
there is *not* an outside-staff priority.
That's exactly what I mean: in the case above, the turn
2009/12/2 Trevor Daniels t.dani...@treda.co.uk:
Happy to do this, but I'm a little puzzled as
the list seems far from complete. The
tab-note-heads-engraver reads several event
properties and sets 'text and 'staff-position.
Should they be added to the list too, or are
all read event
Hi Trevor,
This looks OK apart from a few minor details (I've mentioned the
interface/doc issues in the main thread).
I look forward to the next instalment.
Cheers,
Neil
http://codereview.appspot.com/164063/diff/1/2
File input/regression/tablature-letter.ly (right):
On 12/2/09 2:47 PM, Neil Puttock n.putt...@gmail.com wrote:
2009/12/2 Carl Sorensen c_soren...@byu.edu:
But it seems to me that if outside-staff-priority is set for one grob, and
not for the other, then they should be compared by script-priority, since
there is *not* an outside-staff
On Wed, Dec 02, 2009 at 08:35:27AM +0100, Bertalan Fodor wrote:
Dunno what the wave thing is all about, but I'm totally fine with
better jail instructions. It would go in Usage 1.7 Jail, or
Security issues, or Running as a web service, or something like
that.
Would you prefer providing
On Wed, Dec 02, 2009 at 11:25:00AM -0500, Chris Snyder wrote:
Graham Percival wrote:
Despite my agreements to both paragraphs above, I agree more with
the first than the second. Namely, I don't see the point of
keeping a list of stuff to add to the docs; that's a recipe for
not getting
2009/12/2 Carl Sorensen c_soren...@byu.edu:
Oh, I had misunderstood. Actually, according to gdb, the \turn has a
script-priority of 0.
Oops, of course, since it's the only Script in the stack.
Does this mean we need to establish the outside-staff-priority for *all*
scripts?
No, since
Carl Sorensen wrote Wednesday, December 02, 2009 10:29 PM
In order to do the proper explanation, it seems to me we need to
be clear on
three things:
1) Stacking priority depends on outside-staff-priority if it's
present
2) If not, it depends on script-priority
3) How to decide if objects
Hi Dana
Many thanks for this. It is not only interesting and useful, but
quite a bit _is_ new to me. The variability it exposes is rather
daunting! Makes me wonder how far we shall get along this road, but
we'll proceed one step at a time and hopefully arrive somewhere
useful.
Trevor
I've added a label:Frog for the google issue tracker; this indicates a
task suitable for a new contributor. I'm kind-of bending the
definition of Frog, since a bunch of the issues are documentation
tasks... but then again, I figured that since the main developers get
their hands dirty with the
27 matches
Mail list logo
