Am 29.07.2012 10:10, schrieb David Kastrup:
Marc Hohl writes:
Am 29.07.2012 08:12, schrieb David Kastrup:
"Phil Holmes" writes:
Sorry, Marc. To do this completely, you will need to add the changed
file to snippets/new. The files in snippets get over-written when we
import fr
Am 28.07.2012 14:08, schrieb David Kastrup:
[...]
One thing that occured to me is that this contains a whole lot of public
functions without any DOC string. No idea whether this might cause a
problem for the documentation run, but it certainly is not much of a
help for humans understanding the
Am 29.07.2012 11:16, schrieb David Kastrup:
Marc Hohl writes:
Am 29.07.2012 10:10, schrieb David Kastrup:
Now it is true that we probably did not have a formal discussion of
this in any rate, and you are probably quite keeping with some sort
of de-facto standard and are in the unlucky
Am 01.08.2012 03:42, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-countdown Patch-push
Comment #56 on issue 1320 by colinpkc...@gmail.com: Enhancement:
user-customizable barlines through a Scheme interface.
http://code.google.com/p/lilypond/issues/detail?id=1320
Counted down t
Am 01.08.2012 09:51, schrieb David Kastrup:
Marc Hohl writes:
Am 01.08.2012 03:42, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-countdown Patch-push
Comment #56 on issue 1320 by colinpkc...@gmail.com: Enhancement:
user-customizable barlines through a Scheme interface.
http
Am 01.08.2012 13:02, schrieb Phil Holmes:
- Original Message - From: "Marc Hohl"
To: "David Kastrup"
Cc: ; ;
Sent: Wednesday, August 01, 2012 11:46 AM
Subject: Re: [Lilypond-auto] Issue 1320 in lilypond:
Enhancement:user-customizable barlines through a Sche
Am 02.08.2012 21:09, schrieb David Kastrup:
Rodolfo Zitellini writes:
I think I could come more or less from the 24th to the 27th, do you
have already planned some of the activities?
It is a bit hard to do at the current level of registrations. Graham is
there the whole time, Mike will arriv
Hello list,
I tried to simplify the make-...-bar-line functions
recently defined in scm/bar-line.scm.
However, if I replace the definition
(define (make-simple-bar-line grob extent thickness)
(let ((blot (if rounded
(layout-blot-diameter grob)
0)))
Am 03.08.2012 21:40, schrieb Marc Hohl:
[...]
Programmierfehler: vertical alignment called before line breaking
Fortsetzung, die Daumen drücken
when I try to compile a score with a span bar:
To answer my own question: the extent for span bars is calculated
elsewhere, so (get-grob-property
Am 07.08.2012 11:20, schrieb benko@gmail.com:
the post-1320 version. Marc, please consider patch set 2 for bar-line
related changes.
http://codereview.appspot.com/6419064/
OK. Are there specific regression tests covering the repeat dots?
I think they should be inluded in this patch.
If y
Am 07.08.2012 22:31, schrieb Benkő Pál:
hi Marc,
2012/8/7 Marc Hohl :
Am 07.08.2012 11:20, schrieb benko@gmail.com:
[...]
good idea, but in the end this patch may be split into four and then
the bar-line changes would go as a separate patch anyway.
See the attached patch. It seems to
Am 09.08.2012 11:01, schrieb Graham Percival:
http://lilypond.org/~graham/gop/gop_5.html
** Proposal summary
Speaking academically, scheme code style is a “solved problem”.
Let’s pick one of the existing solutions, and let a computer deal
with this. Humans should not waste their time, energy, a
Am 07.08.2012 22:31, schrieb Benkő Pál:
[...]
If you want to cover all by one patch, I can send the changes
in bar-line.scm to you and you put them into your patch.
What do you think?
good idea, but in the end this patch may be split into four and then
the bar-line changes would go as a separa
Am 10.08.2012 19:00, schrieb Benkő Pál:
hi Marc,
I noticed that your patch didn't include the changes
in bar-line.scm – was that intentional?
The new regtests are already in master; I didn't compile
the regtests, but surely they look strange without the
changes in the colon stencil routine?
ye
your patch.
The attached one should be 1:1 to the status in
http://codereview.appspot.com/6419064/patch/6001/7006
Regards,
Marc
From a267db66489cbde49377b31e09c9e0cb33fd5938 Mon Sep 17 00:00:00 2001
From: Marc Hohl
Date: Wed, 8 Aug 2012 07:30:59 +0200
Subject: [PATCH] line count issues in
Am 19.08.2012 15:02, schrieb David Kastrup:
Details are still somewhat fuzzy since I don't have all that much
feedback concerning who will arrive when and leave, but there are some
corner points.
Apparently Janek will be arriving in advance. No details yet as to his
exact travel time and accomm
Am 19.08.2012 19:12, schrieb David Kastrup:
Marc Hohl writes:
And yes, I'll take my guitar with me, and my wife will be joining,
too, but not the lilypond meeting – she'll take the car and will do
some day trips around Waltrop. I hope she'll be back in time each
night so I
Am 20.08.2012 07:30, schrieb Colin Campbell:
On 12-08-17 06:14 AM, Benkő Pál wrote:
hi all,
[...]
ok, I applied this (and did a bit of restructuring to keep
lyrics-bar.ly the way we like).
I also changed those regtests that show where's the change of dot
placement
inside or outside staff.
I
Am 19.08.2012 22:29, schrieb Janek Warchoł:
On Sun, Aug 19, 2012 at 3:02 PM, David Kastrup wrote:
Details are still somewhat fuzzy since I don't have all that much
feedback concerning who will arrive when and leave, but there are some
corner points.
Apparently Janek will be arriving in advance
Am 22.08.2012 20:29, schrieb m...@mikesolomon.org:
On 22 août 2012, at 20:24, Marc Hohl wrote:
[...]
I'll take the sleeping bag and sleeping pad if you can bring them - I only have
a pillow and toothbrush.
I put it in the car. See you soon!
Am 23.08.2012 10:19, schrieb David Kastrup:
Jan Nieuwenhuizen writes:
I would like to arrive Friday early evening and stay till at least late
Saturday night, possibly Sunday too.
Excellent. How are you fitted regarding sleeping bag/mat/tent/camper?
The two Musescore developers have booked i
Am 26.08.2012 12:32, schrieb gra...@percival-music.ca:
second thought, there's two remaining ones that should be changed:
quick-start.itexi: line 285
programming-work.itexi: line 982
There you are.
http://codereview.appspot.com/6483057/
___
lilypo
Am 27.08.2012 20:00, schrieb David Kastrup:
Note the project lead being on the high horse after having wrapped up
the 2.17.0 release for good.
Congratulations for finishing 2.17.0, Mike's monster patch and stuff!
I am very glad having had the opportunity to meet you guys in
Waltrop. It was a s
Hello list,
my current work on bar lines is ready for uploading
to rietveld (due to the recent amount of work in
Waltrop), but ...
Since some bar lines have to be renamed, I wrote a
rule for 2.17.1 (which works, by the way ;-)
When I apply convert-ly with
sh scripts/auxiliar/update-with-conver
Am 28.08.2012 18:04, schrieb David Kastrup:
Marc Hohl writes:
Hello list,
my current work on bar lines is ready for uploading
to rietveld (due to the recent amount of work in
Waltrop), but ...
Since some bar lines have to be renamed, I wrote a
rule for 2.17.1 (which works, by the way
Am 28.08.2012 18:04, schrieb David Kastrup:
Marc Hohl writes:
Hello list,
my current work on bar lines is ready for uploading
to rietveld (due to the recent amount of work in
Waltrop), but ...
Since some bar lines have to be renamed, I wrote a
rule for 2.17.1 (which works, by the way
Am 28.08.2012 20:52, schrieb David Kastrup:
Marc Hohl writes:
After searching a bit more,
git grep blank-page-force
shows several hits, but in 2.17.x, this should read blank-page-penalty,
so I assume when master gets updated, then the convert rules should be
applied, or am I totally on the
Am 28.08.2012 22:45, schrieb Marc Hohl:
Am 28.08.2012 20:52, schrieb David Kastrup:
Marc Hohl writes:
After searching a bit more,
git grep blank-page-force
shows several hits, but in 2.17.x, this should read blank-page-penalty,
so I assume when master gets updated, then the convert rules
Am 28.08.2012 22:52, schrieb Graham Percival:
On Tue, Aug 28, 2012 at 10:45:00PM +0200, Marc Hohl wrote:
Am 28.08.2012 20:52, schrieb David Kastrup:
Marc Hohl writes:
After searching a bit more,
git grep blank-page-force
shows several hits, but in 2.17.x, this should read blank-page
Am 28.08.2012 23:06, schrieb gra...@percival-music.ca:
LGTM, and I'm quite glad that a few new regtests got bumped to 2.16.0.
Please push directly to staging.
http://codereview.appspot.com/6488047/
Done.
Marking as fixed and going to bed afterwards.
Thanks,
Marc
__
Am 29.08.2012 00:14, schrieb Trevor Daniels:
Marc Hohl wrote Tuesday, August 28, 2012 9:56 PM
Am 28.08.2012 22:52, schrieb Graham Percival:
On Tue, Aug 28, 2012 at 10:45:00PM +0200, Marc Hohl wrote:
Am 28.08.2012 20:52, schrieb David Kastrup:
Marc Hohl writes:
After searching a bit more
Hello list,
I just uploaded part 2/2 of the "Great Bar Line Interface Project",
see
http://codereview.appspot.com/6498052
I hope that it is understandable what I have done, but since the
description of the patch is rather short, I'll give an overview:
* the input string of a bar line called by
Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/detail?id=2790#c3
Patchy the autobot says: lots of: +programming er
Am 30.08.2012 00:07, schrieb David Kastrup:
Marc Hohl writes:
Am 29.08.2012 21:43, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues
Am 30.08.2012 06:46, schrieb lilyp...@googlecode.com:
Comment #6 on issue 2790 by grenoui...@lilynet.net: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/detail?id=2790#c6
Build results are available at
http://grenouille.lilynet.net/patches-tests/2790/test-results
Am 30.08.2012 09:57, schrieb eluze:
there are about 9 commits marked
"Fixed_2_17_1" which have to be changed to "Fixed_2_17_2" since they
missed the proper time to actually make it into 2.17.1.
I found 8 and changed them.
one or two of them were labeled Fixed_2.17.1 which makes it difficult
Am 30.08.2012 01:46, schrieb thomasmorle...@googlemail.com:
Great work so far.
Some minor suggestions:
http://codereview.appspot.com/6498052/diff/5001/scm/bar-line.scm
File scm/bar-line.scm (right):
http://codereview.appspot.com/6498052/diff/5001/scm/bar-line.scm#newcode203
scm/bar-line.s
Am 30.08.2012 15:05, schrieb lilyp...@googlecode.com:
Comment #9 on issue 2783 by benko@gmail.com: wrong placement of
timesignature
http://code.google.com/p/lilypond/issues/detail?id=2783
ok, I actually use centre-of-staff-range, i.e. (min + max) / 2, so all of
(-4 4) (-4 2.5 3 3.5 4) (-4
Am 30.08.2012 18:10, schrieb Trevor Daniels:
John Mandereau wrote Thursday, August 30, 2012 10:38 AM
There's a non negligible number of old issues with Patch=needs-work:
http://code.google.com/p/lilypond/issues/list?can=2&q=Patch=needs_work&sort=-modified&colspec=ID%20Type%20Status%20Stars%20Ow
Hello all,
I am just about rewriting the bar line user interface and stumbled across a
serious problem: with my new approach, the valta brackets are displaced.
For developing a fix, I need to know how this is properly done.
Gould doesn't say much about the details, and this is the only reference
Am 31.08.2012 11:58, schrieb John Mandereau:
Il giorno gio, 30/08/2012 alle 09.29 +0200, Marc Hohl ha scritto:
Am 30.08.2012 06:46, schrieb lilyp...@googlecode.com:
Comment #6 on issue 2790 by grenoui...@lilynet.net: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues
Am 31.08.2012 19:19, schrieb Jan Nieuwenhuizen:
Han-Wen Nienhuys writes:
Manual writers: can we make up our minds here? I've always been
against frivolous syntax for shortcuts (one example in particular is
the "q" for repetition). Why do we put in "q" for users to save some
keystrokes, and at
Hi Arnold, Phil and David,
thanks for your answers!
Just for the record: the image I sent is the actual Lilypond
output.
I think the easiest way to handle volta brackets
is either using the anchor calculated by bar-line::calc-anchor
or the left and right edge of the (span) bar, i.e. the bar ste
Am 31.08.2012 02:05, schrieb thomasmorle...@googlemail.com:
http://codereview.appspot.com/6498052/diff/10001/Documentation/snippets/printing-a-repeat-sign-at-the-beginning-of-a-piece.ly
File
Documentation/snippets/printing-a-repeat-sign-at-the-beginning-of-a-piece.ly
(right):
http://coder
Am 01.09.2012 21:39, schrieb Graham Percival:
[...]
At Waltrop, you only heard about one quarter of the ideas that Janek had.
I think that Janek has spent quite a lot of time collecting and formulating
his ideas. What about posting his ideas and use them as a discussion base
in terms of usabi
Am 01.09.2012 22:02, schrieb pls:
There must have been a change in default with regards to the visibility of string
numbers between 2.15.20 and the current version. In 2.15.20 it was still possible to
add string numbers to notes (e.g. c'4\4) without them showing up in the score. This
was very
Am 01.09.2012 22:22, schrieb David Kastrup:
pls writes:
There must have been a change in default with regards to the
visibility of string numbers between 2.15.20 and the current
version. In 2.15.20 it was still possible to add string numbers to
notes (e.g. c'4\4) without them showing up in the
Am 03.09.2012 15:11, schrieb Graham Percival:
[...]
other people shoot
down ideas by trapping it in a net, lowering it to the ground,
giving it a drink of hemlock, then stroking its head as it falls
asleep.
This is quite an amazing metaphor – if my ideas are supposed
to die, I hope they die like
Am 02.09.2012 22:24, schrieb thomasmorle...@googlemail.com:
More nit-picking:
http://codereview.appspot.com/6498052/diff/7003/python/convertrules.py
File python/convertrules.py (right):
http://codereview.appspot.com/6498052/diff/7003/python/convertrules.py#newcode3395
python/convertrules.py
Am 06.09.2012 08:59, schrieb lilyp...@googlecode.com:
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2813 by mts...@gmail.com: Patch: Allows user to set
ChordName text
http://code.google.com/p/lilypond/issues/detail?id=2813
Allows user to set ChordName text
http://coder
Hello list,
as Graham pointed out in another thread, descriptions like
bar line interface (part 2/2)
are not very informative.
On the other hand, when there is a lot of review/change/re-uploading
involved, the issue tracker gets rather quickly stuffed when the
whole story about the patch is rep
Hello list,
for my work on the volta bracket inclusion for the new bar line interface,
I need to know how the bars are ordered in (ly:grob-object grob 'bars).
Please see the attached file.
For the \musOne, I get a grob array with eight BarLine grobs
(two for each staff) for the first volta brac
Am 11.09.2012 20:48, schrieb m...@mikesolomon.org:
On 11 sept. 2012, at 17:48, Marc Hohl wrote:
Hello list,
for my work on the volta bracket inclusion for the new bar line interface,
I need to know how the bars are ordered in (ly:grob-object grob 'bars).
Please see the attached file.
Am 11.09.2012 21:08, schrieb m...@mikesolomon.org:
On 11 sept. 2012, at 22:02, Marc Hohl wrote:
Am 11.09.2012 20:48, schrieb m...@mikesolomon.org:
On 11 sept. 2012, at 17:48, Marc Hohl wrote:
Hello list,
for my work on the volta bracket inclusion for the new bar line interface,
I need to
Am 11.09.2012 21:54, schrieb m...@mikesolomon.org:
On 11 sept. 2012, at 22:29, Marc Hohl wrote:
Are you certain that every vertical axis group will always contain the same
number of bar lines? If not, it's possible that the matrix you're talking
about may not have complete rows
Am 11.09.2012 21:54, schrieb m...@mikesolomon.org:
On 11 sept. 2012, at 22:29, Marc Hohl wrote:
Are you certain that every vertical axis group will always contain the same
number of bar lines? If not, it's possible that the matrix you're talking
about may not have complete rows
Am 12.09.2012 23:59, schrieb Graham Percival:
On Mon, Sep 10, 2012 at 02:28:36PM +0100, James wrote:
Mark,
On 10 September 2012 14:15, Marc Hohl wrote:
Is there a way to rename the patch description that shows up in the
issue tracker? I think I have seen something like this in a patch
from
Am 11.09.2012 20:48, schrieb m...@mikesolomon.org:
On 11 sept. 2012, at 17:48, Marc Hohl wrote:
Hello list,
for my work on the volta bracket inclusion for the new bar line interface,
I need to know how the bars are ordered in (ly:grob-object grob 'bars).
Please see the attached file.
Am 14.09.2012 20:48, schrieb Graham Percival:
On Fri, Sep 14, 2012 at 11:39:53AM +0200, David Kastrup wrote:
Werner LEMBERG writes:
PS: I'm still not happy with a separate mailing list.
A separate fluffy mailing list not to be taken seriously where people
may decide that no further changes t
Am 14.09.2012 19:10, schrieb m...@mikesolomon.org:
On 14 sept. 2012, at 19:56, Phil Holmes wrote:
OK - so there's been a lot of discussion of pre- and post-fix, and a load of
other stuff I don't understand.So I had a think about what it is about lilypond
syntax that p**s me off. And I concl
Hello list,
I am still working on the barline interface ...
The testing process works fine on my local
machine, but 'make doc' fails due to some
syntax changes in the snippets. For example,
defaultBarType = "empty" will not work once
the patch is applied.
So I looked at
http://lilypond.org/doc
Am 17.09.2012 08:15, schrieb Keith OHara:
Marc Hohl hohlart.de> writes:
The testing process works fine on my local
machine, but 'make doc' fails due to some
syntax changes in the snippets. For example,
defaultBarType = "empty" will not work once
the patch is applied.
Am 18.09.2012 07:16, schrieb Graham Percival:
On Sun, Sep 16, 2012 at 09:06:10PM +0200, Marc Hohl wrote:
So I looked at
http://lilypond.org/doc/v2.17/Documentation/contributor/lsr-to-git
and I wonder if these changes should be included
*in* the barline patch or the procedure described in the
Am 20.09.2012 11:56, schrieb David Kastrup:
David Kastrup writes:
Within your own scores, be consistent in your choices. How this
consistency looks, does not matter. Within LilyPond, there is a large
consistency which elements are uppercase, and which lowercase. The one
thing that actually
Am 20.09.2012 18:17, schrieb lilyp...@googlecode.com:
[...]
Oh. \omit is actually even better, isn't it?
Yes, I like it!
I'll likely change that, short of protests. Still, something more
convincing for \single would be nice.
Yes, but I still have no clue ...
_
[sorry, forgot to hit "Reply to all"]
Am 20.09.2012 19:02, schrieb David Kastrup:
Marc Hohl writes:
[...]
The problem is not people not interested in this kind of
discussions/proposals. The problem is people who stop being interested
in an oh so important problem the moment
Am 20.09.2012 20:08, schrieb gra...@percival-music.ca:
We normally do not include \override in most sections of the Notation
manual. Instead, we ask users to submit LSR snippets showing the
\override, then we include those snippets in the docs. This allows us
to improve the documentation with m
Am 21.09.2012 00:31, schrieb Thomas Morley:
[...]
Hi David, Marc,
speaking only for me: I'm terrible sorry that I currently can't give
you the feedback you desire. Since my injury, I wasn't able to
concentrate on any more involved project or to finish any larger one.
Also, I let Marc a
Am 21.09.2012 11:00, schrieb David Kastrup:
Marc Hohl writes:
But I don't want to tackle around with the documentation *yet* while
it is not sure that my patch gets accepted and the new interface is
considered a good idea by most of the developers. So while in an
ideal world every progr
Am 23.09.2012 08:50, schrieb Graham Percival:
On Sat, Sep 22, 2012 at 01:42:46PM +0200, Marc Hohl wrote:
Am 21.09.2012 11:00, schrieb David Kastrup:
A user interface change without documentation or regtest is dead code.
Regtests are somewhat mandatory:
http://lilypond.org/doc/v2.17
Am 24.09.2012 08:25, schrieb Werner LEMBERG:
\beaming { c8[ c] c r c[ c c c] }
Ouch. Of course.
but yes, that would be great.
This could probably be
\beaming {8[ 8] 8 8 8[ 8 8 8] }
+1
So we have another result of GLISS.
Werner
___
Am 24.09.2012 12:04, schrieb lilyp...@googlecode.com:
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2856 by d...@gnu.org: Patch: Get along with use of
grob-property instead of grob-property-path in overrides
http://code.google.com/p/lilypond/issues/detail?id=2856
Get al
Am 24.09.2012 13:49, schrieb David Kastrup:
"Phil Holmes" writes:
From: "Werner LEMBERG"
Again, with the suggestion above, this is not needed. This part of
the rule is that the bracketed note lengths must form a complete bar
in the current time signature. If not, an error is thrown.
Here
Am 24.09.2012 12:55, schrieb David Kastrup:
Marc Hohl writes:
Am 24.09.2012 12:04, schrieb lilyp...@googlecode.com:
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2856 by d...@gnu.org: Patch: Get along with use of
grob-property instead of grob-property-path in
Am 26.09.2012 02:25, schrieb Thomas Morley:
Hi,
sometimes I heard users complaining about the difficulty of changing
the appearance of customized percussion staves,
The NR "Custom percussion staves"
states: "If you do not like any of the predefined lists you can define
your own list at the top
Hello list,
I am quite frustrated – yesterday I managed to get the shift out of
input/regression/beam-feather-breaking.ly which was one of the
last problematic files for my patch.
Today, I looked at the new results: it seems to me that
*every* other regtest file is affected now, but the one ment
Am 26.09.2012 11:47, schrieb m...@mikesolomon.org:
On 26 sept. 2012, at 11:01, Marc Hohl wrote:
Can anyone with more knowledge than me give me a hint what's wrong?
IIUC correctly, lilypond draws a bar line at the beginning of each line,
but in most cases, this is an invisible one.
If you
Am 26.09.2012 14:45, schrieb Thomas Morley:
[...]
Hi Marc,
an idea, don't know if it's really helpful:
>From 2.16.0-bar-line.scm, bar-glyph-alist:
The old definition of bar "empty" was: ("empty" . (() . ()))
The old definition of bar "" was: ("" . ("" . ""))
The new patch converts bar "empty
Am 26.09.2012 12:23, schrieb David Kastrup:
Marc Hohl writes:
Am 26.09.2012 11:47, schrieb m...@mikesolomon.org:
I unfortunately don't have much time to help you out, but I can tell
you that you are on the right track doing prints to the command
line. I would not, however, stash th
Am 26.09.2012 12:46, schrieb Phil Holmes:
[...]
I've no idea if this will help, so feel free to ignore it. However, my
recollection is that running lily with -ddump-signatures gives
information on extents in the output file?
Thanks for this hint – I didn't know that such an option even exists.
Am 26.09.2012 22:43, schrieb David Kastrup:
Marc Hohl writes:
Am 26.09.2012 12:23, schrieb David Kastrup:
Marc Hohl writes:
Am 26.09.2012 11:47, schrieb m...@mikesolomon.org:
I unfortunately don't have much time to help you out, but I can tell
you that you are on the right track
Am 26.09.2012 12:34, schrieb m...@mikesolomon.org:
On 26 sept. 2012, at 12:07, Marc Hohl wrote:
Am 26.09.2012 11:47, schrieb m...@mikesolomon.org:
On 26 sept. 2012, at 11:01, Marc Hohl wrote:
Can anyone with more knowledge than me give me a hint what's wrong?
IIUC correctly, lil
Am 26.09.2012 14:45, schrieb Thomas Morley:
[...]
Hi Marc,
an idea, don't know if it's really helpful:
>From 2.16.0-bar-line.scm, bar-glyph-alist:
The old definition of bar "empty" was: ("empty" . (() . ()))
The old definition of bar "" was: ("" . ("" . ""))
With regard to that, I have to ma
Am 27.09.2012 09:10, schrieb David Kastrup:
Marc Hohl writes:
Am 26.09.2012 14:45, schrieb Thomas Morley:
[...]
Hi Marc,
an idea, don't know if it's really helpful:
>From 2.16.0-bar-line.scm, bar-glyph-alist:
The old definition of bar "empty" was: ("empty"
Am 28.09.2012 09:30, schrieb d...@gnu.org:
[...]
And things like \once\no Clef also work reasonably well. The proposed
"\single" is more awkward, but "\single\omit Clef" is not that much
better, so maybe "\single" should change.
I don't feel quite happy with \single either; just a spontaneous
Am 28.09.2012 00:21, schrieb ianhuli...@gmail.com:
Apart from a typo in changes.tely (q.v.), LGTM.
http://codereview.appspot.com/6498052/diff/24001/Documentation/changes.tely
File Documentation/changes.tely (right):
http://codereview.appspot.com/6498052/diff/24001/Documentation/changes.tely
Am 28.09.2012 00:54, schrieb thomasmorle...@googlemail.com:
One tiny addition:
http://codereview.appspot.com/6498052/diff/24001/scm/bar-line.scm
File scm/bar-line.scm (right):
http://codereview.appspot.com/6498052/diff/24001/scm/bar-line.scm#newcode1053
scm/bar-line.scm:1053: (define-bar-
Am 28.09.2012 01:38, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #33 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/detail?id=2790
Patchy says 'fail on make check' - took an age to f
Am 28.09.2012 10:16, schrieb Marc Hohl:
Am 28.09.2012 01:38, schrieb lilyp...@googlecode.com:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #33 on issue 2790 by pkx1...@gmail.com: Patch: bar-line
interface part 2/2
http://code.google.com/p/lilypond/issues/detail?id=2790
Patchy
Am 28.09.2012 11:45, schrieb Phil Holmes:
- Original Message - From: "Marc Hohl"
To:
Sent: Friday, September 28, 2012 10:30 AM
Subject: Error tracking through the log files [was: Re: Compilation
errorwith page-breaking-page-count3.ly]
I did a 'make test' on
Am 28.09.2012 11:38, schrieb David Kastrup:
Marc Hohl writes:
Well, it seems to be not as simple as that.
I did a 'make test' on my patch. This fails, obviously.
The console says:
Dissecting...
Writing snippets...
Processing...
Processing
/home/marc/git/lilypond/out/lybook-test
t about \delete ? Afaik it's not taken yet.
Guile begs to differ:
scheme@(guile-user)> delete
$1 = #
On Fri, Sep 28, 2012 at 9:53 AM, Marc Hohl <mailto:m...@hohlart.de>
wrote:
> Am 28.09.2012 09:30, schrieb d...@gnu.org:
>> And things like \once\no Clef also work r
Am 28.09.2012 12:24, schrieb Phil Holmes:
- Original Message - From: "Marc Hohl"
To:
Sent: Friday, September 28, 2012 11:00 AM
Subject: Re: Error tracking through the log files [was: Re:
Compilation errorwith page-breaking-page-count3.ly]
[...]
A brute force method
Am 29.09.2012 07:11, schrieb k-ohara5...@oco.net:
Looks good so far.
In one pdf previewer (evince) at low resolution, the span bars look a
little thicker than the regular bar lines. Maybe a rounding fault of
the viewer, but it would be better if you know how to avoid it.
If you zoom it, this wil
Am 29.09.2012 11:01, schrieb David Kastrup:
Marc Hohl writes:
Am 28.09.2012 17:40, schrieb d...@gnu.org:
hmm... not quite perfect.
No other idea, though...
\here misses the relation to the next item (not that \single is much
better). \directly was nicer in that regard. \next would
Am 29.09.2012 17:01, schrieb lilyp...@googlecode.com:
Comment #1 on issue 2868 by mts...@gmail.com: Patch: Various clean-ups
in stems and beams.
http://code.google.com/p/lilypond/issues/detail?id=2868#c1
Various clean-ups in stems and beams.
*) Eliminates code dups for Kievan work.
*) Transf
Am 29.09.2012 18:39, schrieb Laura Conrad:
"David" == David Kastrup writes:
>> \bar "" inserts an empty stencil, so the padding around the
>> (invisible) bar line is preserved.
David> Yes, I understood that. But what do we need that for?
For the Renaissance music I transcribe,
Am 29.09.2012 18:54, schrieb Colin Campbell:
On 12-09-29 09:47 AM, David Kastrup wrote:
I am not convinced. Unless I see either a new proposal that I feel I
can get behind myself, or more prominent public support for one of the
numerous existing proposals including \next, I am going to stick wi
Am 27.09.2012 00:32, schrieb Thomas Morley:
2012/9/26 Marc Hohl :
I like the idea of giving the user the ability to change only parts of the
list
without having to rewrite the full list; I think that this concept could be
of
use in other parts of lilypond as well,
Hi Marc,
further testing
Am 29.09.2012 19:05, schrieb Laura Conrad:
"Marc" == Marc Hohl writes:
>> I hope that the new interface both makes more sense than the old one,
>> and still allows me to set barless music without ugly gaps where the bar
>> lines aren't.
Ma
301 - 400 of 651 matches
Mail list logo
