--
Michael
>From 7c0fd69ba512a7bdff60e5bf7ea927879add8250 Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Thu, 1 Jul 2010 22:42:59 -0700
Subject: [PATCH] Edit to the music glossary
Added more to the entry on brass.
---
Documentation/music-glossary.tely |3 ++-
1 files changed, 2 inserti
Edited two entries.
>From a7c9678eae46aceace0525f876a9d47d51d6e678 Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Sat, 3 Jul 2010 21:55:10 -0700
Subject: [PATCH] Edits to glossary
Updated "accelerando" and fixed "rallentando" (removed extra period).
---
Documentation/music-glossary.tely |4 +
Removed four instances of double periods.
--
Michael
>From d113bf5029d581b105fa8d764a51fe14db61368b Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Mon, 5 Jul 2010 12:55:53 -0700
Subject: [PATCH 2/2] Remove double periods in glossary
Removed 4 instances of double periods.
---
Documentat
Added German name from "alla breve" and create consistency for "cut
time."
--
Michael
>From db8f11d1f8cfaaaccdf6c921a014378071fac29f Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Mon, 5 Jul 2010 19:04:17 -0700
Subject: [PATCH 2/2] Edits to glossary
Added German nam
Edit to the glossary.
--
Michael
>From 5e68ed89eb9a1c8bf3e8a76ea74ff45fb6d0ab57 Mon Sep 17 00:00:00 2001
From: Mikemoral
Date: Fri, 16 Jul 2010 11:55:36 -0700
Subject: [PATCH 2/2] Edit to glossary
Edited entry "diminuendo." Added a little blurb.
---
Documentation/music-glossar
Whoops, forgot the subject.
Probably would have been "Edit to glossary."
--Michael
On Fri, 2010-07-16 at 23:15 +0100, Trevor Daniels wrote:
> Thanks Michael. Pushed to git.
>
> Trevor
>
> - Original Message -
> From: "Michael"
> To: "Li
[16]" and nothing happens.
As far as I remember, Lily failed in any of the later 2.11. releases
with segfault in the same case. Is this a known issue?
Otherwise I could try to cook a minimal example.
Regards,
Michael
___
lilypond-devel mailin
<<
% \time 4/4
% g\breve
%>>
\layout {
\context {
\Voice
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
}
}
After completion_heads_engraver had called Duration for that note,
LilyPond remains in an endless(?) loop in:
is negative,
but the operator doesn't shift the other way(right).
Am I allowed to cook a patch for testing?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
less, please test and critizize!
Michael
>From 7dc5a8bdef5b04931856eb380939595d4efc3d7e Mon Sep 17 00:00:00 2001
From: root
Date: Thu, 26 Feb 2009 11:01:15 +0100
Subject: [PATCH] This fixes an endless loop in duration.cc:67 when Duration::Duration(Rational r, bool scale) is called
with r.num()
Both fixed. Other comments?
>From c30a3049063acb270332d6f83a43a808a4893b16 Mon Sep 17 00:00:00 2001
From: root
Date: Thu, 26 Feb 2009 13:19:48 +0100
Subject: [PATCH] This fixes an endless loop in duration.cc:67 when Duration::Duration(Rational r, bool scale) is called
with r.num() >= 2 * r.den(
moment I can't imagine cases where this could happen.
Can't happen, AFAICT: by the definition of k, k >= -intlog2(p) and so
-k <= intlog2(p) <= log2(p). Therefore 2^{-k} <= p and so (p >> -k) ==
p*2^k >= 1. That is, you never shift everything away.
Ok, so what's the next step now?
Joe Neeman wrote:
On Thu, 2009-02-26 at 13:24 +0100, Michael Käppler wrote:
Both fixed. Other comments?
Just one: can you set the environment variables GIT_AUTHOR_NAME and
GIT_AUTHOR_EMAIL so that an actual name and email show up in the patch?
Done.
>F
Hi all,
I recently noticed that ligatures are not automatically noticed as a
melismatic section. That means, I always have to
use the syntax: \[ bla \melisma bla \melismaEnd \]
However, I would consider ligatures to be melismatic in >any< case.
What's your point?
Regar
ne is drawn.
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
further investigate (and maybe implement) this?
Even where to look in the code.
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
vary - mostly I found it above notes which
shall have some "extra weight". The figure I attached is very common.
Unfortunately I don't have a scanner at this time, so I can't provide
original images now. But if you're interested in implementing this, I
could see w
ventions for it up to now.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
quot;This short vertical line
placed above the note is commonly used in baroque music. It's meaning
can vary, e.g. it may indicate a slight accent, a strong shortening or
that all notes with those lines shall be stressed similarly. The
following example ..."
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
only criteria you can
base this decision eventually, because in 17th/18th century music nearly
every score looks different...)
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Additionately, maybe it would be nice to increase the >relative<
thickness of the stroke on smaller staff sizes as it's described in NR
4.2.1 for the Feta font. Otherwise the line will look too thin at
smaller staff sizes, I think.
Regar
variant I found in the old Händel print.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi all,
I'd like to test Joe's new spacing code. Has it already been merged into
master or do I have to pull from dev/jneeman?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinf
rs clearly from one
to another without any noticeable reason.
I can send you the affected files off-list, if you want.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
ich time line-width is
calculated if you don't set it explicitly. And, much more confusing, I
don't see any procedures in C++ that actually check the line-width. A
"grep -R line-width *" isn't very informative.
Any ideas?
Regards,
Michael
called about. Therefore (ly:modules-lookup)
returns (* 10 mm) in any case.
You can easily test this: the default line-width is 190 mm in any case,
what margins you ever specify.
I will try to provide a fix as soon as possible.
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
nding on margin settings
- calculate missing values from given values (left-margin, right-margin,
line-width)
Cheers,
Michael
>From 9778370158e39bfe9e0a0015e234adcf1cab7e3e Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Tue, 11 Aug 2009 18:01:01 +0200
Subject
to the normal git package?
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
e61835;hb=HEAD).
This snippet also fails to get a sane value for paper-height in
layout->page-init.
Ok, thanks, I will have a closer look tomorrow.
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
is enough to do just git-cl upload without having
to pass a commitish.
Maybe it would be useful to add this information to CG 8.7.7, too.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Mark Polesky wrote:
Michael,
Don't forget, you need to mention on -devel that you've posted
to Rietveld, and include the link. You'll also need to close
it when it's approved/resolved (CG 8.7.9).
Here's Michael's patch:
http://codereview.appspot.com/104085
-
used elsewhere)
and set default values if the settings are considered bad.
What I would like to add is the possibility to switch off this
"consistency check", so that you can have negative margins and exceeding
line-widths if you need to.
Regards,
Michael
ef contain no paper-width / paper-height etc.? I don't
really know how this can be triggered by my patch since it clones the
output-def and modifies only the margin and line-width parts.
Any idea?
Regards,
Michael
___
lilypond-devel mailing l
ons?
Hopefully I can post something working for review soon.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Are the *.ly-initfiles parsed later?
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Michael Käppler wrote:
Hi Joe,
get_paper is called more than once for each paper block. The first time
is probably from parser.yy:847, which actually _creates_ the first paper
block (so no variables have been parsed at all). Perhaps a better place
for normalize() would be after parser.yy:830
{
foo;
}
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
sheet
music
}
\book {
\bookpart {
\paper {
...
This value will be written in the output ps file, but seems to have no
effect.
To sum up: What's the intention of this line-width value in ps output files?
Cheers,
Michael
___
lilypond-
s.
Ideally, this would output to a list like:
foo1.pdf - 0
foo2.pdf - 13
foo3.pdf - 142
foo4.pdf - 0
(...)
Then the dev's can mark the foo3.pdf like Jerry R. Ehman's wow signal...
;) I mean, this would give a priority for checking, when e.g.
Reinhold Kainhofer wrote:
Isn't this exactly what we already have (make test-baseline to create the
Argh, how embarrassing! Sorry for the noise.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/ma
Hi all,
it took me quite a while but here is a new approach for review:
http://codereview.appspot.com/109051
More in a few hours.
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond
.
that's a good point. However, I'm going to be on vacation for a week and
will rewrite this when I come back.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
odus if they are set (and maybe
discard left- and right-margin). What is your opinion?
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
There
details.last_column_ contains an empty Grob (0x0). When calling the
methods of the Grob class on it, it crashes, which happens after
is_break ().
2.13.3 doesn't have this problem, but there were lots of commits between.
Joe, can you help?
Cheer
Mats Bengtsson wrote:
I can process Documentation/general/examples/granados.ly without
crashes, using latest GIT version of today.
Me too, but test the following snippet:
\version "2.13.4"
\layout {
system-count = #1
}
\repeat unfold 20 { c d e f }
Regard
Hi all,
here's the new version which includes all fixes but for the
"system-count=#1" issue, on which Joe can take a look on I hope.
http://codereview.appspot.com/109051/
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-dev
ed in the
ps-file, but not used?
Btw, were you able to further investigate this system-count issue?
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi all,
please review this patchset, which is based on my former changes:
http://codereview.appspot.com/115065
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Patrick,
I recently noticed that /input/regression/bookparts.ly gives the warning
"Missing stencil expression: utf-8-string" what I think is related to
your patchset.
Could you please have a look at this?
Thanks,
Michael
___
lily
Hi all,
Hmm... was there any progress since July on this topic?
I'd like to year if there's anything new... ;)
Cheers,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi all,
I rewrote the patchset to have less doubled scheme code and make it
extensible.
Any comments are very welcome.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
r. But there's another problem I
fixed now: the old version would crash if the default value isn't
defined in paper-defaults-init.ly or elsewhere. Now it's set to zero in
this case and a programming error is outputted.
Regards,
Michael
__
more easily if programming_errors would be
outputted. I don't know if it's worth the effort, though.
http://codereview.appspot.com/115065/diff/1013/14
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi all,
I'm not very familiar with git for now, therefore I have got a question.
Let's assume I've checked out a fresh master/origin and did some commits
on top of it. How can I concatenate this commits in one to create only
one patch?
R
in scaling patch I posted recently for review.
Regards,
Michael
>From 5e0663dfcf01e68e26572ec7979b9580ab26ea5c Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Wed, 9 Sep 2009 11:48:35 +0200
Subject: [PATCH] Introduce new handling for paper margin settings.
* Make de
chain-assoc-get.
I also recognized that some assoc-get or chain-assoc-get calls occur
with #f set as default value, which I think is unnecessary since #f is
the hardcoded default already.
Regards,
Michael
>From 5fb65494ecb7e25d87fdfea6ce2133a818631df8 Mon Sep 17 00:00:00 2001
From: =?utf-
ther.
(Just to give you an impression about my system's slowness)
Regards,
Michael
>From 7235a6af9fc738cea7e35d0e5063f772c7e94af1 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Fri, 11 Sep 2009 12:06:37 +0200
Subject: [PATCH] Introduce new handling for paper marg
That would be no great deal. More difficult will be to decide to which
of the two classes the assoc-get calls belong. Maybe a task for Mark
Polesky?
Regards,
Michael
>From 8fa96593e20a00107785b024201d30875afa54cc Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Fri
x27;t
think that is intended, since the >absence< of the warning would be
wrong behaviour, not the appearance.
Regards,
Michael
btw. thanks for running the tests.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
same issue Trevor reported one hour ago?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
please look again.
Regards,
Michael
>From 33c05dd7df4000d7f25d2903e2555d9ca86c2e1f Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 01:47:00 +0200
Subject: [PATCH] Introduce new handling for paper margin settings.
* Make default margins accessible
ng. This naturally
applies to default_value too, which could conceivably be any scheme
object.
What about adding a type check to ly_scm2string and add the possibility
to convert from symbols and numbers too?
Isn't there a guile built-in method for converting
Many thanks for all helpful comments.
Attached is the revised patch.
What's the reason that chain-assoc-get is defined separately in
lily-library.scm:210, though ly_chain_assoc_get exists?
Regards,
Michael
>From 740bd0fcb035099086e9e60a325019fdf25595d4 Mon Sep 17 00:00:00 2001
From: =
l correctly, it is only in Scheme optional, but not in C.
Regards,
Michael
>From d49a99745e25b688bc1ef8dd44854bad95067adc Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 23:32:49 +0200
Subject: [PATCH] Improve error checking in ly:assoc-get and
Sorry, silly me. :)
I think we're nearly there. I'm just about to do a regtest check just
to be sure.
Just a few remaining nitpicks:
- trailing spaces
- long lines
That should be fixed now.
Is there a default for maximum line length?
Regards,
Mic
gment.
What is the reason for this behaviour?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Neil,
Thanks, it's applied.
Great. The next step is attached. Can you please run a regtest?
Regards,
Michael
>From 2aa0ede53ec2b8e03f47c3b0f525cfbc636c Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sun, 13 Sep 2009 22:11:36 +0200
Subject: [PATCH] Tu
dcoded with 3 mm and applied to every snipped unless something different
is specified?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
in and send me an png
if it still fails?
Regards,
Michael
>From 62df04e629ba03493a16f0201ffb95c8ffbcf252 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 01:47:00 +0200
Subject: [PATCH] Introduce new handling for paper margin settings.
* Make default marg
Hi Neil,
Thanks, also applied (no regtest problems to report).
that's nice. Here's the next step.
Btw. what's going on with the paper-margins patch? Could you run another
regtest / doc build?
Regards,
Michael
>From 7e0190ccc76f602d1e803f15832af780d449d863 Mon Sep 17
ent for a comparison procedure.
Sorry for missing that. However, don't you think that this '=' is
unnecessary? The default comparison procedure is equal? and I don't see
any differences to = that matter for this case.
Regards,
Michael
>From 66ea82f15798237ced4a4a14d32f
do this? I think
he digged pretty deep into the scheme code recently.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Neil Puttock wrote:
2009/9/14 Michael Käppler :
Hmm, I can't reproduce this here. Can you try again and send me an png if it
still fails?
It's still pretty bad; see the attached image.
This is weird. I've just checked out a fresh master, did a make clean
and
my testing branch.
I fixed this now by removing any line-width setting when calling
(set-paper-dimensions).
Regards,
Michael
>From 70ea27f30399183293e7b5db3cd0af466fd99680 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 01:47:00 +0200
Subject: [PATCH]
Hi all,
I'd like to propose the following as a possibility to provide a simple
progress indicator for the "Preprocessing graphical objects" stage.
I'm happy to read your comments.
http://codereview.appspot.com/122051
Regards,
Michael
I've just finished a regtest check and clean docs build, and as far as
I can tell, everything looks fine; there are no warnings reported for
any of the A6-size paper tests, and all the snippets I compared are
virtually indistinguishable.
Wow, unbelievable! Now ready to apply?
___
hopefully get to
considerable defaults.
Can you propose a good way how to set the constants in Lily or SCM code?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
))). This is ugly,
first because it requires a line-width default and second because it
could be integrated in one line.
To sum up, lilypond-book should compute one line-width instead of
handling different constructs that exclude each other. (Look around
lilypond-book.py:614)
Regards,
Michael
>F
hink; I'll take a look on it later.
Regards,
Michael
>From 9e8766b370e907b9ebb1a626dcc386104680c29e Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Thu, 24 Sep 2009 18:26:32 +0200
Subject: [PATCH] Implement a progress indicator for the grob-preprocessing stages.
Are there still any objections against applying?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi all,
I'd like to know how I can do a git pull on all branches simultaneously.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
matically remove trailing whitespace on saving. What do you mean
with "formatting"? Are there still overlong lines or do you speak of
indentation?
Would you mind preparing a patch to document the changes (in
particular, right-margin
Hi all,
I'd like to post this patch for final review. It was already reviewed a
while ago by Carl.
It aims at scaling paper margins according to which paper size was chosen.
Hopefully no whitespace / style issues this time.
Regards,
Michael
>From e0377c12766f4820512eaa56db22af58930a
Hopefully no whitespace / style issues this time.
Argh... forget this.
Here's a revised version.
Cheers,
Michael
>From cf099ca1134b02a813e47109c684a8a100b04253 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 21:55:17 +0200
Subject: [PA
Would you mind preparing a patch to document the changes (in
particular, right-margin)?
Here you are.
The changes that aren't applied yet (default margin scaling) are already
integrated.
Regards,
Michael
>From 6839cb0e9fa85f2ea7f1ee42faa6877408387704 Mon Sep 17 00:00:00 2001
Fro
Hmm... no comments at all?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
here
else. Then I will have a look on it.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Ok, that should be fixed now. Can you please verify?
Regards,
Michael
>From 117824090d54c9607af476dee9545bd957f5ce96 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 21:55:17 +0200
Subject: [PATCH] Let default margins depend on paper size.
* Make ind
demonstrate the functionality. But they both had just one after
the change, don't they?
Which one shall I do not change and why?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Here you are.
What about the docs patch?
Regards,
Michael
>From 3cda0a2d5326b2359784ca1e10b04b078abd2cb9 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 21:55:17 +0200
Subject: [PATCH] Let default margins depend on paper size.
* Make indent and sh
Hi Neil,
I hope I've lost nothing.
Regards,
Michael
>From aa34f02a9eb85aaa39d3ff45f31597d279330461 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 21:55:17 +0200
Subject: [PATCH] Let default margins depend on paper size.
* Make indent and shor
ught about this. Fixed now.
Cheers,
Michael
>From 99e7ed230c22109e7c93ff26dcbbcd26a76a5539 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Sat, 12 Sep 2009 21:55:17 +0200
Subject: [PATCH] Let default margins depend on paper size.
* Make indent and short-indent defaults
Hi all,
please review this patch:
http://codereview.appspot.com/144049
It's aim is to provide the possibility for setting different margins on
odd and even pages.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hi Neil,
@itemize
There are a few places where a full stop could do with an extra space,
but the rest of the patch looks fine.
You've mentioned check-consistency in the main discussion, but you
might like to add it to `Other layout variables' too.
Fixed.
Regards,
Mic
Now I've rebuilt the docs, I've changed my mind slightly. :)
Otherwise it would have been way too simple so I'm not surprised... :))
Better now?
Regards,
Michael
>From 227afb026946e543eafa228bd4ff42f5bb6003fa Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4pple
/144049/diff/1/6
File scm/paper.scm (right):
http://codereview.appspot.com/144049/diff/1/6#newcode242
Line 242: (("foot-separation" . ,h) - '())
oops ;)
Argh... fixed.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
n.putt...@gmail.com wrote:
Hi Michael,
This looks OK, apart from a few indentation issues. In particular, the
whole of `set-paper-dimensions' is slightly off.
Cheers,
Neil
Hi Neil,
I'm slightly unsure what to do now. Since I'm a little bit tired of this
indentation stuff I g
p and Scheme incorrectly).
Hmm, i've never used vim indenting. What I meant was: "May I simply run
the emacs auto-indenting on any file I've put new code in?"
Please have a look if it's okay now.
Cheers,
Michael
>From 5c4fd6a9017584b64884260490d52e87a0c4afec Mon Sep
Here you are.
Regards,
Michael
>From 5deda137b69c7110b6fc02046497362788347e34 Mon Sep 17 00:00:00 2001
From: =?utf-8?q?Michael=20K=C3=A4ppler?=
Date: Fri, 6 Nov 2009 14:25:52 +0100
Subject: [PATCH] Docs: Add documentation for paper variables involved in two-sided mode.
---
Documentat
rrect. However, it >is< mentioned, but in an unclear
manner:
See NR 4.1.2 "Other layout variables", auto-first-page-number.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
1 - 100 of 414 matches
Mail list logo
