Am 07.11.2010 23:51, schrieb Valentin Villenave:
On Thu, Nov 4, 2010 at 9:38 AM, Marc Hohlm...@hohlart.de wrote:
I came up with the idea to parenthesize the Harmonic brackets instead of the
TabNoteHead and thus provide the possibility to left-parenthesize or
right-parenthesize an item, but
Mark Polesky wrote Monday, November 08, 2010 1:24 AM
Instead of these two:
withingroup-staff-staff-spacing
staffgroup-staff-spacing
Let's stay with these.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
2010/11/8 Mark Polesky markpole...@yahoo.com:
Instead of these two:
withingroup-staff-staff-spacing
staffgroup-staff-spacing
While these aren't perfect, i'd say that
within-group-staff-staff-spacing
below-group-staff-staff-spacing
inside-group-staff-staff-spacing
Reinhold Kainhofer wrote Monday, November 08, 2010 12:09 AM
Am Sonntag, 7. November 2010, um 20:46:54 schrieb Trevor Daniels:
I think this would be an improvement, but I don't think it's
essential. The file will be left in an erroneous state so
the user will be forced into further
On Mon, Nov 8, 2010 at 9:21 AM, Marc Hohl m...@hohlart.de wrote:
Carl has some good ideas about this issue, but meanwhile, I think
we (you :-) should put it on the tracker, so it doesn't get lost.
There you go!
http://code.google.com/p/lilypond/issues/detail?id=1386
Cheers,
Valentin.
On 2010-11-07 16:30, Mark Polesky wrote:
[...]
SPACE MINIMUM-DISTANCE
-- --
1) basic-distanceminimum-distance
2) initial-distanceminimum-distance
3) basic-separation minimum-separation
4) initial-separation minimum-separation
On Mon, Nov 8, 2010 at 11:13 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
There might even be an argument for adding something
which made compilation fail - in a way that clearly
indicated the problem, of course.
Bold idea... or insane, I can't decide which one it is. :-)
Anyway, this
Valentin Villenave wrote Monday, November 08, 2010 11:16 AM
On Mon, Nov 8, 2010 at 11:13 AM, Trevor Daniels
t.dani...@treda.co.uk wrote:
There might even be an argument for adding something
which made compilation fail - in a way that clearly
indicated the problem, of course.
Bold idea...
I am top-posting.
James: did you maybe have an answer to this question on another
thread? I am also interested. Docs say something but they could be
possibly clearer on this subject. I'd like to improve this situation.
2010/10/30 James Lowe james.l...@datacore.com:
-Original Message-
Dear LilyPond developers,
Kieren,
We have had a discussion one year ago about a project to rewrite the
{ ... } \\ { ... }
so it behaves exactly like
{
% continuation of the main Voice from outside the polyphony
\voiceOne
...
}
\context Voice = 2 {
Francisco,
On 08/11/2010 11:38, Francisco Vila wrote:
James: did you maybe have an answer to this question on another
thread? I am also interested. Docs say something but they could be
possibly clearer on this subject. I'd like to improve this situation.
I had no specific answer. As my last
Hello,
On 08/11/2010 12:00, James wrote:
I am not a developer so do not know the internal workings of the code,
however the above tracker is a doc bug..
Sorry that was probably badly worded, it is an 'open issue'. ;)
James
___
lilypond-devel
On Mon, Nov 8, 2010 at 12:46 PM, Xavier Scheuer x.sche...@gmail.com wrote:
We have had a discussion one year ago about a project to rewrite the
{ ... } \\ { ... }
Hi Xavier,
isn't that the discussion I tried to sum up on
http://code.google.com/p/lilypond/issues/detail?id=1316
?
Please repost
On 8 November 2010 13:05, Valentin Villenave valen...@villenave.net wrote:
Hi Xavier,
isn't that the discussion I tried to sum up on
http://code.google.com/p/lilypond/issues/detail?id=1316
?
Yes, it is exactly that!
I looked into the tracker but did not find this issue.
Typing \\ into the
Hello Valentin,
I think that
$ git diff Documentation/web/news-front.itexi
@@ -22,7 +22,7 @@ today is LilyPond’s co-founder and core developper
read on to find out what for!
Come
-...@uref{http://news.lilynet.net/The-LilyPond-Report-21, read
On Mon, Nov 8, 2010 at 1:53 PM, Francisco Vila paconet@gmail.com wrote:
Hello Valentin,
I think that
-...@uref{http://news.lilynet.net/The-LilyPond-Report-21, read
Yes indeed, this commit was littered with clumsiness. Hopefully
everything is fixed now; sorry for the git-history noise but I
On Mon, Nov 8, 2010 at 1:51 PM, David Kastrup d...@gnu.org wrote:
Slurs, ties etc from outside to the second voice would still be
forbidden. The problem really is that Lilypond's notion of continuity
(we have that also in repeat alternatives, codas and similar) is too
naive.
About this
Reviewers: ,
Message:
Here's a patch set for this big syntax change. I went with
withingroup since it got more votes. Okay to push?
- Mark
Description:
vertical spacing: Rename properties.
Please review this at http://codereview.appspot.com/2968042/
Affected files:
M
Keith E OHara wrote:
We will use this in context that makes that first
qualifier almost redundant :
\override Context.StaffGrouper #'withingroup-staff-staff-spacing
This is an excellent point, and in response I'd like to
propose one more option -- just remove the withingroup
prefix altogether:
Am 08.11.2010 11:59, schrieb Valentin Villenave:
On Mon, Nov 8, 2010 at 9:21 AM, Marc Hohlm...@hohlart.de wrote:
Carl has some good ideas about this issue, but meanwhile, I think
we (you :-) should put it on the tracker, so it doesn't get lost.
There you go!
On 8 November 2010 13:05, Valentin Villenave valen...@villenave.net wrote:
Please repost your mail as a comment there, I think it will be more
appropriate, useful and (possibly) efficient :-)
Done.
David
Slurs, ties etc from outside to the second voice would still be
forbidden. The
Mark Polesky markpole...@yahoo.com writes:
% space between consecutive staves in a system
\override VerticalAxisGroup #'staff-staff-spacing
% space between consecutive staves in a staff-group
\override StaffGrouper #'staff-staff-spacing
The property descriptions could have a brief
hi list,
the attached patch adds noteheads needed for black mensural notation (BMN)
and coloratio in white mensural notation (WMN).
note that it's just the noteheads: in both BMN and coloratio sections
in WMN a fourth note looks like a flagged half note.
I could reach this look by the following
On 11/8/10 1:14 PM, Mark Polesky markpole...@yahoo.com wrote:
Keith E OHara wrote:
We will use this in context that makes that first
qualifier almost redundant :
\override Context.StaffGrouper #'withingroup-staff-staff-spacing
This is an excellent point, and in response I'd like to
Mark Polesky wrote Monday, November 08, 2010 7:14 PM
Keith E OHara wrote:
We will use this in context that makes that first
qualifier almost redundant :
\override Context.StaffGrouper #'withingroup-staff-staff-spacing
This is an excellent point, and in response I'd like to
propose one more
On Mon, 08 Nov 2010 11:14:11 -0800, Mark Polesky markpole...@yahoo.com wrote:
Similarly, I think the two 'staff-staff-spacing properties
would be intuitive and easy enough to keep separate,
mentally:
% space between consecutive staves in a system
\override VerticalAxisGroup
On 11/8/10 9:34 PM, Keith E OHara k-ohara5...@oco.net wrote:
On Mon, 08 Nov 2010 11:14:11 -0800, Mark Polesky markpole...@yahoo.com
wrote:
Similarly, I think the two 'staff-staff-spacing properties
would be intuitive and easy enough to keep separate,
mentally:
% space between
\override StaffGrouper #'staff-staff-spacing
\override StaffGrouper #'staffgroup-staff-spacing
LGTM
(As I've said before, I admire your persistence :)
If David's comment isn't a valid concern, this is fine with me too.
Werner
___
Before having access to OpenType features, I consider any change in
the font interface premature.
OK, but I have other font-related issues I wanted to report. Maybe
I could report them anyway, so people know developers are aware of
these issues (and in the same time devs could think at
29 matches
Mail list logo
