https://codereview.appspot.com/8613043/diff/19001/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/8613043/diff/19001/Documentation/changes.tely#newcode153
Documentation/changes.tely:153: @item
I would add a note that, if there is too-snug
Gilles THIBAULT wrote
one way to make point and click work on windows xp follows [...]
...
Eluze
Hello,
in relation to issue 3306
[http://code.google.com/p/lilypond/issues/detail?id=3306]
I analized the point-and-click problem on my Win7/64 computer.
(Why does it not work out of the box
On 2013/04/16 06:05:42, MikeSol wrote:
https://codereview.appspot.com/8613043/diff/19001/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/8613043/diff/19001/Documentation/changes.tely#newcode153
Documentation/changes.tely:153: @item
I would
On 2013/04/16 07:20:59, dak wrote:
On 2013/04/16 06:05:42, MikeSol wrote:
I would add a note that, if there is too-snug spacing
for an object, setting its vertical skylines to #'()
will generally restore old behavior.
I am not really enthused about telling people that,
since too snug is a
On 2013/04/16 07:40:19, Trevor Daniels wrote:
On 2013/04/16 07:20:59, dak wrote:
On 2013/04/16 06:05:42, MikeSol wrote:
I would add a note that, if there is too-snug spacing
for an object, setting its vertical skylines to #'()
will generally restore old behavior.
I am not really enthused
On 2013/04/16 07:51:46, dak wrote:
So for a stable release, we need conservative
settings. Settings that won't _force_ people to
pepper their sources with overrides and tweaks just
to throw them all out again when the next version arrives.
So for this particular case we'd need to add predefs
On 2013/04/16 07:51:46, dak wrote:
On 2013/04/16 07:40:19, Trevor Daniels wrote:
On 2013/04/16 07:20:59, dak wrote:
On 2013/04/16 06:05:42, MikeSol wrote:
I would add a note that, if there is too-snug spacing
for an object, setting its vertical skylines to #'()
will generally restore
On Mon, 2013-04-15 at 23:06 +0200, Janek Warchoł wrote:
2013/4/15 Richard Shann richard.sh...@virgin.net:
On Mon, 2013-04-15 at 17:25 +0200, Janek Warchoł wrote:
Looks like using
\layout {
\context {
\Score
\printRefpoint ##f #'all-grobs
}
}
inserts
On 2013/04/16 08:34:43, MikeSol wrote:
On 2013/04/16 07:51:46, dak wrote:
I hate it when I get last-minute realizations. Here is another
thing we need to do for the stable release: go through all
problems of the too snug kind and work out defaults that avoid
them. It's ok to tell people
On 16 avr. 2013, at 12:59, d...@gnu.org wrote:
On 2013/04/16 08:34:43, MikeSol wrote:
On 2013/04/16 07:51:46, dak wrote:
I hate it when I get last-minute realizations. Here is another
thing we need to do for the stable release: go through all
problems of the too snug kind and work out
So we need feedback from the heavy hitters, and we have annoyingly
few of them I know about. Kieren is one. I don't know how many
tweaks there are in Valentin's opera, but that might be another
opportunity.
For my pieces, I always try to avoid overrides and tweaks as much as
possible. In
2013/4/16 d...@gnu.org:
I hate it when I get last-minute realizations. Here is another thing we
need to do for the stable release: go through all problems of the too
snug kind and work out defaults that avoid them.
This might be impossible. For example to avoid this problem {
d''4-.\downbow
I've considerably shortened the regtests, removing redundancies and
unnecessary line breaks. Thanks for the comments!
https://codereview.appspot.com/8647044/diff/1/input/regression/offsets.ly
File input/regression/offsets.ly (right):
On 2013/04/13 21:39:40, janek wrote:
There's one thing that puzzles me. Current syntax is
\offset property offset-value grob-name
I understand that grob-name is at the end because it's optional, and
we want to
omit it when we're using \offset as a tweak.
However, i find this syntax
On 2013/04/16 12:50:47, david.nalesnik wrote:
On 2013/04/13 21:39:40, janek wrote:
There's one thing that puzzles me. Current syntax is
\offset property offset-value grob-name
I understand that grob-name is at the end because it's optional, and
we want
to
omit it when we're using
On 2013/04/16 13:03:25, dak wrote:
On 2013/04/16 12:50:47, david.nalesnik wrote:
Here I kept the same pattern as \alterBroken and \shape,
as they have been revised by David Kastrup. I agree that
the syntax is a little awkward, and that
it would be nice if the pattern you give were workable.
and there's too many or-nothings there (i suppose
that the biggest problem is an optional argument
followed by non-optional one (value)). However,
in case of \offset, we can have either a \shape-like
syntax
\offset property value grobname-or-music
or
\offset grobwithproperty-or-property
On 2013/04/16 14:33:50, janek wrote:
2013/4/16 d...@gnu.org:
nothing-or-music in the last position only works if nothing is
_explicitly_ specified with \default
There is no way that the last argument of a music function can be
nothing silently.
pity. would it possible (and
2013/4/16 d...@gnu.org:
and there's too many or-nothings there (i suppose
that the biggest problem is an optional argument
followed by non-optional one (value)). However,
in case of \offset, we can have either a \shape-like
syntax
\offset property value grobname-or-music
or
\offset
Hi,
I switched to lily-dev which was referred in CG at last and built lilypond
and documentation successfully. And thank you for your instruction, I have
been reading some countdown patches. I saw the three issues and I'm trying
to solve the first one.
As for git, yes, I used git in my graduate
Thanks very much, I switched to lily-dev now and everything goes well.
The problem with my ghostscript appeared randomly, I will report it in
bug-lilypond.
From: James [mailto:pkx1...@gmail.com]
Sent: Friday, April 12, 2013 6:25 PM
To: Janek Warchoł
Cc: Fan Ziye; LilyPond Developmet Team
https://codereview.appspot.com/8613043/diff/19001/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/8613043/diff/19001/Documentation/changes.tely#newcode160
Documentation/changes.tely:160: #(ly:set-option 'debug-skylines #t)
\override
On 2013/04/16 11:11:03, janek wrote:
2013/4/16 d...@gnu.org:
I hate it when I get last-minute realizations. Here is another
thing we
need to do for the stable release: go through all problems of the
too
snug kind and work out defaults that avoid them.
This might be impossible. For
On 16 avr. 2013, at 22:12, d...@gnu.org wrote:
On 2013/04/16 11:11:03, janek wrote:
2013/4/16 d...@gnu.org:
I hate it when I get last-minute realizations. Here is another
thing we
need to do for the stable release: go through all problems of the
too
snug kind and work out defaults
On Tue, 16 Apr 2013 12:15:23 -0700, m...@mikesolomon.org m...@mikesolomon.org
wrote:
On 16 avr. 2013, at 22:12, d...@gnu.org wrote:
Wrong placement? Seriously? Can you give any articulation where
you'd get bad behavior for considering just its bounding box?
f4--.
In the bad old days,
On Tue, 16 Apr 2013 04:10:32 -0700, Janek Warchoł janek.lilyp...@gmail.com
wrote:
2013/4/16 d...@gnu.org:
I hate it when I get last-minute realizations. Here is another thing we
need to do for the stable release: go through all problems of the too
snug kind and work out defaults that avoid
26 matches
Mail list logo
