https://codereview.appspot.com/235010043/diff/1/ly/music-functions-init.ly
File ly/music-functions-init.ly (right):
https://codereview.appspot.com/235010043/diff/1/ly/music-functions-init.ly#newcode36
ly/music-functions-init.ly:36: ((integer?) ly:music?)
Why use a number here instead of a
On 2015/05/03 06:28:43, dak wrote:
https://codereview.appspot.com/235010043/diff/1/ly/music-functions-init.ly
File ly/music-functions-init.ly (right):
https://codereview.appspot.com/235010043/diff/1/ly/music-functions-init.ly#newcode36
ly/music-functions-init.ly:36: ((integer?) ly:music?)
Nice! However, I second David's concern: Please use
\absolute pitch
instead of
\absolute number
https://codereview.appspot.com/235010043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Janek Warchoł wrote Sunday, May 03, 2015 12:53 AM
The behaviour that discouraged me from working on LilyPond for some
time was not obviously unacceptable (i.e. it wasn't some ad hominem
attack, nor anything else unanimously condemned by others). Rather,
it was the general attitude of some
I'm in favour of a change like this, but I'd prefer
the syntax and options to parallel those of
\relative. That is, an optional prefix pitch to indicate
the starting octave, and taking the starting octave from
the first contained note if the prefix is omitted. That
would then become an
On 2015/05/03 08:20:03, Trevor Daniels wrote:
I'm in favour of a change like this, but I'd prefer
the syntax and options to parallel those of
\relative. That is, an optional prefix pitch to indicate
the starting octave, and taking the starting octave from
the first contained note if the prefix
Dan Eble d...@faithful.be writes:
On Apr 30, 2015, at 08:26 , David Kastrup d...@gnu.org wrote:
Dan Eble d...@faithful.be writes:
What if we defined \override Grob.property as addressing the nearest
enclosing context named “”, and aliased all contexts except
part/sub-voice to “”. (Maybe
On 2015/05/03 16:42:02, Trevor Daniels wrote:
Yes, in Keith's and my model \relative sets a starting pitch,
\absolute would
set a starting octave only, and pitches thereafter are relative to the
octave of
the previous note.
That's not really absolute. It's a different mode of relative.
Hello dev list,
Below are some notes I made as I worked with the contributor’s guide and
LilyDev in recent months. This started with minor things and grew from there.
They represent my view as a novice who is basically learning git and the
command line as I go. I found the learning curve
On May 3, 2015, at 16:42 , David Kastrup d...@gnu.org wrote:
Dan Eble d...@faithful.be writes:
Adding a wrapper context will have undesirable effects.
The question is what requirements or mechanisms we could employ in order
to remove the undesirable effects.
For example, it could be
On 2015/05/03 20:04:28, dak wrote:
There is no such thing as '' or s'' as a recognizable element in
LilyPond's
syntax and there is not even a tangible representation of it in
Scheme. I don't
think that such a feature warrants both messing with the parser as
well as
introducing new Scheme
Two notes:
Paul Morris p...@paulwmorris.com writes:
CG 3.3.4 Making Patches
git format-patch origin doesn't work if you type it in literally,
but gives ambiguous argument 'origin' message.
Shouldn't happen unless you managed to create either a local branch
named origin or a file with that
On 2015/05/03 20:25:22, dak wrote:
Again: I don't think that this was Keith's proposal. And I am pretty
sure that
none of my suggestions was Keith's proposal either: I just angle for
something
useful to do with \absolute f.
It wasn't Keith's proposal, you're right, I rather ran on ahead.
On 2015/05/03 20:25:22, dak wrote:
I still would recommend
just using c to keep one's options for possible later changes. And
not have too
much choice without associated meaningful difference.
This is wise.
https://codereview.appspot.com/235010043/
Am 04.05.2015 um 00:15 schrieb David Kastrup:
CG 3.3.4 git-cl configuration
add how to set the EDITOR variable for git cl, namely:
export EDITOR=/usr/bin/nano
Nano does not offer point-and-click in connection with LilyPond I think.
I don't think so either. But I don't see why that should
On 5/3/15 8:33 AM, Joseph Rushton Wakeling
joseph.wakel...@webdrake.net wrote:
On 10/04/15 09:34, Werner LEMBERG wrote:
So the question is whether Launchpad has a usable API, right? Joseph,
do you know more?c
Just to follow up on this, I exchanged a few messages on Reddit with
Colin
Watson
On 2015/05/03 20:25:22, dak wrote:
On 2015/05/03 16:42:02, Trevor Daniels wrote:
I find it awkward when \absolute c'' and \absolute g'' mean exactly
the same
thing. But it's not like I could not live with it. But I still would
recommend
just using c to keep one's options for possible
On 2015/05/03 16:42:02, Trevor Daniels wrote:
a continuous scale would be \relativeOctave { c, d e f g a b c' d e f
... }.
The c' resets the octave. This doesn't work so well for a melody
oscillating a
tone or two above and below a c, of course, but it does avoid multiple
''' and
,,,.
Reviewers: dak, lemzwerg, Trevor Daniels, Dan Eble, pwm,
Message:
On 2015/05/03 08:20:03, Trevor Daniels wrote:
I'd prefer the syntax and options to parallel those of
\relative. That is, an optional prefix pitch to indicate
the starting octave, and taking the starting octave from
the first
On Mon, May 04, 2015 at 03:02:32AM +, Carl Sorensen wrote:
A. Suggestions for LilyDev3:
All of these suggestions would actually probably be for LilyDev4. I'm not
sure that we will make another release of LilyDev3. But if we did, I'm
still happy to host it.
If somebody is available and
I also favour
\absolute c'' { ... }
in Keith's original interpretation. However, I suggest to document
somewhere that only letter `c' is supported.
https://codereview.appspot.com/235010043/diff/60001/ly/music-functions-init.ly
File ly/music-functions-init.ly (right):
On 5/3/15 4:09 PM, Paul Morris p...@paulwmorris.com wrote:
I think that it would be great to have you prepare patches for the CG.
The CG is the least-reviewed manual in our set, so it's probably the
easiest manual for which to get patches approved.
A. Suggestions for LilyDev3:
All of these
Le 02/05/2015 20:18, Jean-Charles Malahieude a écrit :
What I've tried so far is:
4- replace any occurrence of @documentlanguage utf-8 by
@documentlanguage UTF-8 and add it where needed
Oops! should have read before sending:
4- @documentencoding UTF-8
Could anybody help?
Cheers,
Hello,
Here is the current patch countdown list. The next countdown will be on
May 6th.
You can always view the most current countdown list here:
http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaitingcolspec=Patch%20Owner%20ID%20Summarysort=patch
If people don't like numbers (I'm with you) are there any other feasible
ways to indicate an octave only? Maybe bare ''' and ,,,? Maybe with an
unpitched name?
\absolute '' { a b c }
\absolute s'' { a b c }
https://codereview.appspot.com/235010043/
Good point, Phil. Perhaps we should slightly amend the text too to
cover this feature, as shown.
Trevor
https://codereview.appspot.com/233110043/diff/20001/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):
Patch counted down - please push to Staging branch.
https://codereview.appspot.com/234900043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: Trevor Daniels, J_lowe,
Message:
Please review
Description:
Update NR font size section (Issue 3370)
Please review this at https://codereview.appspot.com/235920043/
Affected files (+9, -0 lines):
M Documentation/notation/text.itely
Index: Documentation/notation/text.itely
diff
- Original Message -
From: Joseph Rushton Wakeling joseph.wakel...@webdrake.net
To: Werner LEMBERG w...@gnu.org; p...@gnu.org
Cc: lilypond-devel@gnu.org
Sent: Sunday, May 03, 2015 3:33 PM
Subject: Re: Google Code shutting down
On 10/04/15 09:34, Werner LEMBERG wrote:
So the question
Thanks for the comments.
https://codereview.appspot.com/233110043/diff/1/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):
https://codereview.appspot.com/233110043/diff/1/Documentation/notation/simultaneous.itely#newcode931
On 10/04/15 09:34, Werner LEMBERG wrote:
So the question is whether Launchpad has a usable API, right? Joseph,
do you know more?c
Just to follow up on this, I exchanged a few messages on Reddit with Colin
Watson (who's leading the git-support effort) following this announcement:
LGTM
Trevor
https://codereview.appspot.com/235920043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM.
Trevor
https://codereview.appspot.com/233110043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2015/05/03 09:02:51, dak wrote:
However, I _think_ that your comment would suggest \absolute f'' { f
... to be
the same
as \absolute { f'' ...
Correct
whereas I suggested making \absolute f'' { f ... the same
as \absolute { bes'' ...
Now there _is_ a difference between \relative c
On 2015/05/03 13:23:15, Dan Eble wrote:
If people don't like numbers (I'm with you) are there any other
feasible ways to
indicate an octave only? Maybe bare ''' and ,,,? Maybe with an
unpitched name?
\absolute '' { a b c }
\absolute s'' { a b c }
I was thinking along the same lines.
On Apr 30, 2015, at 08:26 , David Kastrup d...@gnu.org wrote:
Dan Eble d...@faithful.be writes:
What if we defined \override Grob.property as addressing the nearest
enclosing context named “”, and aliased all contexts except
part/sub-voice to “”. (Maybe I’ll try that tonight and see what
On 2015/05/03 16:27:58, pwm wrote:
On 2015/05/03 13:23:15, Dan Eble wrote:
If people don't like numbers (I'm with you) are there any other
feasible ways
to
indicate an octave only? Maybe bare ''' and ,,,? Maybe with an
unpitched
name?
\absolute '' { a b c }
\absolute s'' { a b c }
37 matches
Mail list logo
