Hello,
This fixes translated bigpages by making
- single-word targets to be lowercased
- anchors match targets
- unneeded anchors be removed, sort of
It brings back the policy of having anchors in English from original
nodenames, thanks to translationof strings which were previously been
igno
Graham Percival wrote:
> A larger question is whether we should keep "3.6
> Post-installation options". In the first place, the word
> "options" implies (to me) something akin to configuration
> options, not "a list of possible commands" (which is the
> meaning used here).
How about restructuring
On Sun, May 16, 2010 at 09:55:09PM +0200, Karl Hammar wrote:
>From the debacle with "Issue 915" I have learned that
>
> . section 8 "Regression tests" is related to section 3.6.3.1
Yes, it's unfortunate that we don't at least have a link from
chapter 8 to 3.6.3. It could also be useful to have s
On 16 May 2010 19:24, Marc Hohl wrote:
> See the attached patch - I hope everything is fine now.
Thanks, applied.
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
>From the debacle with "Issue 915" I have learned that
. "make test-redo" does not catch regression due to program changes
. rest-collision-beam-note.ly changes is more or less expected
. section 8 "Regression tests" is related to section 3.6.3.1
Does "make check" after test-baseline serve any p
Karl Hammar:
> Neil Puttock:
...
> > I basically do what Carl outlined in the other thread:
> >
> > make test-baseline
> >
> > git apply issue931041_1.diff
> >
> > make check
>
> The contributor manual says (3.6.3.1):
>
>* Initial test:
>
> make [-jX]
> make test-basel
Neil Puttock schrieb:
On 16 May 2010 09:35, Marc Hohl wrote:
Now, I have created a patch which
1) restores the former width of the double bar line
2) works properly with the segno sign
\bar ".S|:" is swapped round. Is this what you want?
Of course not - thanks for the hint!
See
Okay to submit?
http://codereview.appspot.com/1240042
This adds error and warning as functions in lilylib.py, as well as
program_name and program_version as variables
These were originally defined in lilypond-book.py, but make more sense
in the library, which can be used by other python appl
On 16 May 2010 09:35, Marc Hohl wrote:
> Now, I have created a patch which
> 1) restores the former width of the double bar line
> 2) works properly with the segno sign
\bar ".S|:" is swapped round. Is this what you want?
Cheers,
Neil
<>___
lilypond-
On Sun, May 16, 2010 at 4:20 PM, Neil Puttock wrote:
> On 16 May 2010 16:12, Graham Percival wrote:
>
>> Oops, I meant to update this once it forgot.
>> The diff from fixcc.py is 724 K.
>
> Is that with emacs 23 installed? I seem to recall there was a wide
> variation in indentation between 22 a
On 16 May 2010 05:58, Mark Polesky wrote:
> Is \newSpacingSection only supposed to be used at the
> beginning of measures? If I use it in the middle of a
> measure, I get a huge gap that I can't seem to remove.
Probably, since it creates a new SpacingSpanner which must have a
NonMusicalPaperColu
On 16 May 2010 16:12, Graham Percival wrote:
> Oops, I meant to update this once it forgot.
> The diff from fixcc.py is 724 K.
Is that with emacs 23 installed? I seem to recall there was a wide
variation in indentation between 22 and 23.
There are many things still wrong with fixcc.py, but it
On Sun, May 16, 2010 at 4:06 PM, Graham Percival
wrote:
> If anybody thinks that the first couple of items on the above list are
> already done, I don't want to hear about it. Running fixcc.py on the
> /lily/ dir produces a diff that's over 100 kb; refering to this as
> having our desires "pinned
On Sun, May 16, 2010 at 4:06 PM, James Lowe wrote:
> Hello,
>
> Does that mean we need to change/edit remove something from the CG?
Yes, but not from you. People who know enough about regtests that
could fix that text can change this themselves. Going through a third
party would only show thing
On Sun, May 16, 2010 at 4:02 PM, Neil Puttock wrote:
> On 16 May 2010 14:35, Karl Hammar wrote:
>
>> Does it matter, if not, why is in the contributor manual ?
>
> I think the instructions were lifted directly from the old (2.10)
> docs, so there may well have been changes to the test suite since
Hello,
On 16 May 2010, at 16:02, Neil Puttock wrote:
On 16 May 2010 14:35, Karl Hammar wrote:
Does it matter, if not, why is in the contributor manual ?
I think the instructions were lifted directly from the old (2.10)
docs, so there may well have been changes to the test suite since they
On Sun, May 16, 2010 at 2:35 PM, Karl Hammar wrote:
> Neil Puttock:
>> > Also, it would be much easier to look throuht the patch if it did not
>> > contain so many whitespace changes. In the first 100lines, I see:
>>
>> Why would you want to look at the bare diff?
>
> Isn't the diff a complete sta
On 16 May 2010 14:35, Karl Hammar wrote:
> Does it matter, if not, why is in the contributor manual ?
I think the instructions were lifted directly from the old (2.10)
docs, so there may well have been changes to the test suite since they
were written. TBH, when I started doing regression test
Neil Puttock:
> On 15 May 2010 14:37, Karl Hammar wrote:
> > git-pull
> > wget http://codereview.appspot.com/download/issue931041_1.diff
> > patch -p1 < issue931041_1.diff --dry-run
> > patch -p1 < issue931041_1.diff
> > make > log 2>&1; make test-redo >> log 2>&1
>
> I very rarely use `make test
On 15/05/10 22:42, Patrick McCarty wrote:
On Sat, May 15, 2010 at 2:22 PM, Graham Percival
wrote:
On Sat, May 15, 2010 at 10:02 PM, Ian Hulin wrote:
As I understand it, these are to get round problems with Guile pre V1.8,7,
which we no longer support. Is it now safe to delete this
Looks good!
http://codereview.appspot.com/969046/show
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hello World,
I often work with drone-instruments like bagpipes which need to know how to
tune their drones. In my handwritten notation I included the Drone indicator
below the keysig as simple text "A" or "A/E" because the absolute notename does
not matter.
How do I do that in Lilypond?
Or do
My first patch was way too trivial and didn't cover all cases
(obviously, I made some errors while testing), so please ignore it.
Now, I have created a patch which
1) restores the former width of the double bar line
2) works properly with the segno sign
For further clarification: I changed the d
23 matches
Mail list logo
