Reviewers: Graham Percival,
Message:
On 2012/01/08 03:32:55, Graham Percival wrote:
this breaks make doc.
Sorry. Fixed.
Description:
Doc: Usage - added link for Windows users
This is part of Tracker 1948
The Document now links to the installation instructions to Windows
As it did for MacOS
Hello,
2012/1/8 Łukasz Czerwiński milimet...@gmail.com:
What's the aim of Lilypond?
err..
LilyPond is a music engraving program, devoted to producing the
highest-quality sheet music possible. It brings the aesthetics of
traditionally engraved music to computer printouts.
And why isn't it
On Jan 8, 2012, at 2:54 AM, Graham Percival wrote:
On Sun, Jan 08, 2012 at 01:52:41AM +0100, Łukasz Czerwiński wrote:
Are there some guidelines how to write new code to work in the same
manner as the already written code?
We have a contributor's guide. It is not complete, but that's
Hey all,
On my lilybuntu box, I am consistently getting a doc fail from current master
on this file. The problem is the embedded post script. It seems like it's a
ghostscript error:
Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89
-dCompatibilityLevel=1.4
Mike
On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote:
Hey all,
On my lilybuntu box, I am consistently getting a doc fail from current master
on this file. The problem is the embedded post script. It seems like it's a
ghostscript error:
Invoking `gs -dSAFER
Hello,
On 8 January 2012 13:07, James pkx1...@gmail.com wrote:
Mike
On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote:
Hey all,
On my lilybuntu box, I am consistently getting a doc fail from current
master on this file. The problem is the embedded post script.
Patchy has helped us avoid breaking git master a few times
recently, but each time involves a certain amount of my time and
energy. I need to check the logs to see if it was just an
accident, look through the git history to see if there's any
particularly suspicious commits that may have caused
Graham,
On 8 January 2012 13:39, Graham Percival gra...@percival-music.ca wrote:
Patchy has helped us avoid breaking git master a few times
recently, but each time involves a certain amount of my time and
energy. I need to check the logs to see if it was just an
accident, look through the
Mike
On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote:
Hey all,
On my lilybuntu box, I am consistently getting a doc fail from current master
on this file. The problem is the embedded post script. It seems like it's a
ghostscript error:
Invoking `gs -dSAFER
On Sun, Jan 08, 2012 at 01:46:44PM +, James wrote:
If somebody else could
take over Patchy -- even if only the staging stuff, not the new
patches -- that would free up time I could spend solving
release-critical bugs. If somebody could handle the new patches
as well, that would be
James,
2012/1/8 James pkx1...@gmail.com:
Graham,
On 8 January 2012 13:39, Graham Percival gra...@percival-music.ca wrote:
If somebody else could
take over Patchy -- even if only the staging stuff, not the new
patches -- that would free up time I could spend solving
release-critical bugs.
Graham,
On 8 January 2012 13:55, Graham Percival gra...@percival-music.ca wrote:
On Sun, Jan 08, 2012 at 01:46:44PM +, James wrote:
If somebody else could
take over Patchy -- even if only the staging stuff, not the new
patches -- that would free up time I could spend solving
I am currently replacing the footnote user interface. The doc string
for autoFootnote states:
(_i Footnote the item after which this comes with the text in
@var{footnote} allowing for the footnote to be automatically numbered
such that the number appears at @var{offset}. Note that, for this
On Jan 8, 2012, at 4:16 PM, David Kastrup wrote:
I am currently replacing the footnote user interface. The doc string
for autoFootnote states:
(_i Footnote the item after which this comes with the text in
@var{footnote} allowing for the footnote to be automatically numbered
such that
Mike
On 8 January 2012 12:48, m...@apollinemike.com m...@apollinemike.com wrote:
Hey all,
On my lilybuntu box, I am consistently getting a doc fail from current master
on this file. The problem is the embedded post script. It seems like it's a
ghostscript error:
I'm not getting this. My
m...@apollinemike.com m...@apollinemike.com writes:
On Jan 8, 2012, at 4:16 PM, David Kastrup wrote:
I am currently replacing the footnote user interface. The doc string
for autoFootnote states:
(_i Footnote the item after which this comes with the text in
@var{footnote} allowing for
On Jan 8, 2012, at 4:45 PM, David Kastrup wrote:
I assume the first is supposed to mean use like
an articulation and the second affects every grob of the given type in
the current timestep.
Yup!
In the same patch, you can change the balloon docstring to the same thing, as
the footnote
On 8 January 2012 15:45, David Kastrup d...@gnu.org wrote:
I am also replacing the flowery language Use like @code{\\tweak}. and
Use like @code{\\once}. since neither makes any sense whatsoever: you
don't use the first before a postevent,
What's a postevent these days then? If you want to
Am 07.01.2012 23:56, schrieb Janek Warchoł:
2012/1/7 m...@apollinemike.comm...@apollinemike.com:
On Jan 7, 2012, at 1:49 AM, Janek Warchoł wrote:
Hi,
i'm inside Clef_engraver::create_clef () - line 130 of lily/clef-engraver.cc
I'd like to do sth based on the clef type (G, F or C). What
Neil Puttock n.putt...@gmail.com writes:
On 8 January 2012 15:45, David Kastrup d...@gnu.org wrote:
I am also replacing the flowery language Use like @code{\\tweak}. and
Use like @code{\\once}. since neither makes any sense whatsoever: you
don't use the first before a postevent,
What's a
2012/1/8 Marc Hohl m...@hohlart.de:
Are you sure the attached patch is up-to-date with your work?
I get a small change clef in the fifth line, see attachment.
I get the same result as Janek. I think the problem is that the
glyph-name callback checks break-status, thus shouldn't be called from
- Original Message -
From: Phil Holmes em...@philholmes.net
To: philehol...@googlemail.com; perciv...@gmail.com;
gra...@percival-music.ca; lilypond-devel@gnu.org;
re...@codereview-hr.appspotmail.com
Cc: lilypond-devel@gnu.org; re...@codereview-hr.appspotmail.com
Sent: Tuesday, January
Reviewers: ,
Message:
This patch compiles clean and allows me to finish a doc build (which is
currently blocking me from doing a couple other things) - I'd like to
push it to staging tomorrow morning w/o a count down unless anyone has
objections.
Description:
Gets rid of PostScript in
Hi,
I noticed this while replying to James.
\override Hairpin #'minimum-length = #8 does not take into account the
fact that a hairpin can be shortened by the presence of a DynamicText.
minimum-length is applied not the real length of the hairpin, but to
the length of the hairpin **if it would
Hi James,
Currently we have snippets about DynamicTextSpanner both in
NR 1.3.1 Expressive marks attached to notes Dynamics and in
NR 1.8.1 Writing text Text spanners .
It would be more consistent to have everything about DynamicTextSpanner
in the same section of the NR, i.e. NR 1.3.1, with a
Xavier,
On 8 January 2012 21:08, Xavier Scheuer x.sche...@gmail.com wrote:
Hi James,
Currently we have snippets about DynamicTextSpanner both in
NR 1.3.1 Expressive marks attached to notes Dynamics and in
NR 1.8.1 Writing text Text spanners .
It would be more consistent to have
Hello,
I noticed this command
http://lilypond.org/doc/v2.15/Documentation/contributor/unsorted-policies
:)
So I tried it...
Gosh... that command touches 'one or two' files doesn't it!
chuckle
Umm.. I guess this is something that a 'senior' dev probably should do
as it also touches all the
On Sun, Jan 1, 2012 at 8:14 AM, Phil Holmes em...@philholmes.net wrote:
Julien,
If you look at http://code.google.com/p/lilypond/issues/detail?id=2156
you'll see there were problems with some commits leading up to December
23rd. As a result, a number weren't forwarded to master and staging
W dniu 8 stycznia 2012 02:54 użytkownik Graham Percival
gra...@percival-music.ca napisał:
On Sun, Jan 08, 2012 at 01:52:41AM +0100, Łukasz Czerwiński wrote:
* Let's assume that I would like to help in developing Lilypond, but
I don't have my own idea, what part of it I could
2012/1/8 Marc Hohl m...@hohlart.de:
Am 07.01.2012 23:56, schrieb Janek Warchoł:
I don't have any idea why change clef isn't small.
Are you sure the attached patch is up-to-date with your work?
I get a small change clef in the fifth line, see attachment.
Strange. I'm sure there's an error on
Merged Kievan patch with existing source code and fixed an issue in
output-lib.scm
http://codereview.appspot.com/4951062/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
For 20:00 MST Tuesday January 10
Critical:
Issue 2193
http://code.google.com/p/lilypond/issues/detail?id=2193: collision
between beams and flags - R 5527047 http://codereview.appspot.com/5527047/
Documentation:
Issue 2189
http://code.google.com/p/lilypond/issues/detail?id=2189: Doc:
On Sun, Jan 08, 2012 at 09:53:16PM +, James wrote:
http://lilypond.org/doc/v2.15/Documentation/contributor/unsorted-policies
thanks, run.
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
LGTM
http://codereview.appspot.com/5503093/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
http://codereview.appspot.com/5517050/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
I really don't like the hard-coded numbers, but I suppose I can't
complain -- the patch doesn't make it any worse in that respect.
http://codereview.appspot.com/5530043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
I like some of the changes here, but I have serious doubts about others.
http://codereview.appspot.com/5520056/diff/1/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
On Sun, Jan 08, 2012 at 09:36:22PM +, James wrote:
It isn't as trivial as you think - and can end up a lot of work, and
while I understand the request, there are more pressing items I think
we need to do with the doc before we start to move huge sections
around.
+1
I'm not opposed to
LGTM
I'm vaguely curious as to what's the difference between this postscript
and the regtest for postscript, but that's no reason to hold up
development. Besides, the lilypond markup is easier to understand than
the postscript, so this is a good change to make even if it wasn't a
build problem.
LGTM
http://codereview.appspot.com/5498093/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Begin LilyPond compile, commit: 76801e173f3815c1347e5685195059a01676cd75
Merged staging, now at: cf023c3d5b03b333cb5e5c3c50ab8d6635efdc60
Success:./autogen.sh --noconfigure
Success:../configure --disable-optimising
*** FAILED BUILD ***
On Sun, Jan 08, 2012 at 10:04:59PM -0800, lilypond.patchy.gra...@gmail.com
wrote:
*** FAILED BUILD ***
Previous good commit: 820c7ff5d380e8ca52057717ab3176b5e40107fd
Current broken commit: cf023c3d5b03b333cb5e5c3c50ab8d6635efdc60
oops, fixed. My fault.
- Graham
Begin LilyPond compile, commit: 42984d05239a3c3be1ea859ba5214ce140448afc
Merged staging, now at: 42984d05239a3c3be1ea859ba5214ce140448afc
Success:./autogen.sh --noconfigure
Success:../configure --disable-optimising
Success:
43 matches
Mail list logo
