On Tue, 2010-01-12 at 11:58 -0500, b...@shingarov.com wrote:
Here is a proposed patch to add functionality to the Page Spacer.
When typesetting large quantities of markup lines, Lilypond currently does not
try to avoid widowed/orphaned lines. Some publishers will consider this an
Le mercredi 13 janvier 2010 à 02:24 +0100, John Mandereau a écrit :
Le mercredi 13 janvier 2010 à 01:19 +0100, Francisco Vila a écrit :
I've just pushed the translated Essay into the lilypond/translation
branch but I don't know how to make new files distributable or what
GNUMakefile to copy
Mark Polesky wrote Wednesday, January 13, 2010 5:52 AM
Trevor Daniels wrote:
I've never had to to do it, as I rarely use the git bash
command line for git work. I can do virtually everything
in git gui or gitk, which cut and paste normally in both
Windows and Unix.
Can you really
Le mercredi 13 janvier 2010 à 00:32 +, Graham Percival a écrit :
Given that John's fix *should* have worked (adding stuff to
one of the stepmake/ or make/ files), but didn't,
It worked for me in a in-tree 'make dist', but I just noticed it failed
in a out-of-tree dist because a leading
Le mercredi 13 janvier 2010 à 09:27 +, Trevor Daniels a écrit :
In gitk (in either Unix or Windows) you can only
copy/paste within the fields that you can highlight.
The include only the SHA1 ID and the Find fields, I
think.
You can also copy (but not paste) from the commit content
Mats Bengtsson wrote Tuesday, January 12, 2010 9:41 AM
1) Right-click on the title-bar of the Git Bash window
2) Select Edit Mark
3) Left-click and drag your selection.
4) Press enter to copy it to the clipboard.
I have never tried GIT on Windows, but if the window in question
is a normal
John Mandereau wrote Tuesday, January 12, 2010 10:21 AM
Trevor Daniels wrote
I never did it - with git gui you never need an
editor. It has a pane specifically for displaying,
entering and editing commit messages. It also has
an Amend Last Commit button which was the only
form of rebase -i
2010/1/13 John Mandereau john.mander...@gmail.com:
However, it would be nice if you didn't put into public Git history
commits that do nothing else than copying files from English docs and
didn't make an extra personal branch appear, e.g. by doing
git checkout lilypond/translation
# pull
John Mandereau wrote Wednesday, January 13, 2010 9:44 AM
Le mercredi 13 janvier 2010 =C3=A0 09:27 +, Trevor Daniels a
=C3=A9crit=
In gitk (in either Unix or Windows) you can only
copy/paste within the fields that you can highlight.
The include only the SHA1 ID and the Find fields, I
On Tue, Jan 12, 2010 at 11:56:17PM -0800, Patrick McCarty wrote:
On Tue, Jan 12, 2010 at 9:53 PM, Mark Polesky markpole...@yahoo.com wrote:
git-starting.itexi 1076L, 35094C
That's trivially small. music-glossary.tely is 8755 lines.
I wouldn't worry about, just as long as the texinfo files
On Wed, Jan 13, 2010 at 8:16 AM, Mark Polesky markpole...@yahoo.com wrote:
Okay, here's a patch. Obviously, there's more work to be done,
but it might be good to get the re-structuring stuff out of the
way. `make' succeeded and `make doc' is still going, but I'm off
to bed.
Looks mostly
Le mercredi 13 janvier 2010 à 12:20 +, Graham Percival a écrit :
- I'm not positive, but I believe that we put punctuation outside @q{}
brackets. If you want to change this policy, we can discuss it, but
please don't just go changing things inside the hu/ translation.
Indeed; Mark,
Le mercredi 13 janvier 2010 à 10:56 +0100, Francisco Vila a écrit :
2010/1/13 John Mandereau john.mander...@gmail.com:
git checkout lilypond/translation
# pull lilypond/translation, whatever the command is for you
git diff paco |git apply --whitespace=fix
git add NEW_FILES # only in case
Mark Polesky wrote Wednesday, January 13, 2010 6:12 AM
Patrick McCarty wrote:
Most of the time, on GNU/Linux, I copy and paste by
highlighting the text to copy, and then middle-clicking
where I want to paste.
For no explicable reason, I just assumed that wouldn't work
in gitk. But it does
Joe,
Paper_book::get_system_specs then you wouldn't even need the
markup-list-id property: you could add an avoid-orphan property that
only gets set for the last line of a multi-line markup list if it is
short. That might also simplify Page_spacer::calc_subproblem.
This is the first idea
Le dimanche 10 janvier 2010 à 13:35 +, Graham Percival a écrit :
Yeah, but 80% of the time, that person is me. And I'm doing major
changes to the build system that could potentially screw up other
people. When major developers (be it John in relation to
translation stuff, Carl about new
Le dimanche 10 janvier 2010 à 11:05 -0800, Mark Polesky a écrit :
I was thinking the same thing. What if we all agree to
prepend an exclamation mark (!) to the subject line? Keep
in mind that threads can become significant long after the
first post. Putting a ! in front will be easy to see
On Wed, 2010-01-13 at 09:11 -0500, Boris Shingarov wrote:
Joe,
Paper_book::get_system_specs then you wouldn't even need the
markup-list-id property: you could add an avoid-orphan property that
only gets set for the last line of a multi-line markup list if it is
short. That might also
Hello,
if a nickname for 2.14 is still to be found, I'd like to propose
Taupin for Daniel Taupin.
http://www.google.com/search?source=igrlz==q=daniel+taupin
He did not contribute directly to LilyPond, but made a big effort
towards free music engraving before LP was born.
--
Francisco Vila.
I don't think we should be in the habit of naming all our releases after people.
Cheers,
- Graham
On Wed, Jan 13, 2010 at 2:39 PM, Francisco Vila paconet@gmail.com wrote:
Hello,
if a nickname for 2.14 is still to be found, I'd like to propose
Taupin for Daniel Taupin.
ok, I've uploaded 2.12.3-2, and a quick glance at the web docs looks
like they work.
If anybody cares about 2.12, CHECK IT NOW. I am going to be even more
pissed off if somebody comes along in a few weeks and asks for
anything else to do with 2.12. My gub tree includes a ridiculous
number of
Le mercredi 13 janvier 2010 à 15:15 +0100, John Mandereau a écrit :
Another thing that we could do instead of creating another list is
writing down as a specification (even written quite informally) the
important changes already started i.e. the i18n of Texinfo, stuff
specific to building the
Graham Percival wrote Wednesday, January 13, 2010 12:20 PM
On Wed, Jan 13, 2010 at 8:16 AM, Mark Polesky
markpole...@yahoo.com wrote:
Okay, here's a patch.
- you've reverted some of the ``foo'' - @qq{foo} changes in
essay. Why?
- I'm not positive, but I believe that we put
Thanks Joe
Mark is currently redrafting this section of the CG and it seems
he has picked up and applied your changes in his latest patch.
Is that right, Mark?
Trevor
- Original Message -
From: Joseph Wakeling joseph.wakel...@webdrake.net
To: lilypond-devel lilypond-devel@gnu.org
2010/1/13 Graham Percival gra...@percival-music.ca:
ok, I've uploaded 2.12.3-2, and a quick glance at the web docs looks
like they work.
Yes.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
___
lilypond-devel mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 13. Januar 2010 17:02:18 schrieb David Kastrup:
Alexander Kobel n...@a-kobel.de writes:
Wilbert Berendsen wrote:
LilyPond 2.12.2 and 2.13.1 display the Lyrics lines correctly, at
regular distances.
It seems the new vertical
Graham Percival wrote:
Looks mostly good.
- you've reverted some of the ``foo'' - @qq{foo} changes
in essay. Why?
Freaky. I didn't touch essay. How did that happen? I see
Trevor has some theories... Oh, I see now that Francisco
was doing some work there. I must not have rebased at the
Trevor Daniels wrote:
Mark is currently redrafting this section of the CG and it
seems he has picked up and applied your changes in his
latest patch.
Is that right, Mark?
Yep. Thanks Joe!
- Mark
___
lilypond-devel mailing list
On Wed, Jan 13, 2010 at 02:24:58PM +0100, John Mandereau wrote:
Le mercredi 13 janvier 2010 à 12:20 +, Graham Percival a écrit :
Also, please
use @q{} in the @section name.
... actually, could we just sidestep the whole issue by removing the
quotes entirely? @node Using lily-git
On Wed, Jan 13, 2010 at 08:32:28AM -0800, Mark Polesky wrote:
Graham Percival wrote:
- elsewhere in the docs, we use foo -- bar, not
foo---bar. I don't pretend to be authoritative about
the difference, though.
I've read that the typographical ideal is:
word, hair-space, em-dash,
Here is the new code -- implementing all that's been discussed. (Ok,
not quite all -- the line length functionality is not implemented, but
all the style remarks have been taken into account, the markup-list-id
has been replaced with is-last-line, penalty made configurable, and
also, (new,
Hi,
How do I tell GUB to build Lilypond from a modified source tree which I
have locally, instead of getting it from git? In general, where is the
best place to start reading more on GUB, the info on the GUB page is
very sketchy, and GUB-related messages on lilypond-devel seem far apart
and
On Wed, Jan 13, 2010 at 02:51:47PM -0500, Boris Shingarov wrote:
How do I tell GUB to build Lilypond from a modified source tree which I
have locally, instead of getting it from git?
Wow, you're brave! Look at lilypond.make; I believe you'll want
something like
make -f lilypond.make
Oh, and make sure you're using the latest GUB; IIRC there are 2 or
3 different git repositories floating around. You want the one at
github.
git://github.com/janneke/gub.git -- this one, right?
I believe you'll want something like
make -f lilypond.make LILYPOND_REPO=/location/of/your/tree
On Wed, 2010-01-13 at 17:21 +0100, Reinhold Kainhofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 13. Januar 2010 17:02:18 schrieb David Kastrup:
Alexander Kobel n...@a-kobel.de writes:
Wilbert Berendsen wrote:
LilyPond 2.12.2 and 2.13.1 display the Lyrics lines
lgtm
http://codereview.appspot.com/186112
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Joe Neeman wrote:
Am Mittwoch, 13. Januar 2010 17:02:18 schrieb David Kastrup:
That's basically the approach taken by Joe for spacing staves: Place the
center lines minimum-spacing apart, except if the skylines would (almost?)
overlap (including a padding). In the latter case add space until
On Wed, 2010-01-13 at 23:12 +0100, Alexander Kobel wrote:
Joe Neeman wrote:
Am Mittwoch, 13. Januar 2010 17:02:18 schrieb David Kastrup:
That's basically the approach taken by Joe for spacing staves: Place the
center lines minimum-spacing apart, except if the skylines would (almost?)
Here is the new code -- implementing all that's been discussed. (Ok,
not quite all -- the line length functionality is not implemented,
but
all the style remarks have been taken into account, the
markup-list-id
has been replaced with is-last-line, penalty made configurable, and
also,
Op donderdag 14 januari 2010 schreef Joe:
So it should just be a matter of finding the
right default for minimum-distance.
From my experimentation, 3.2 is a fine default value I think. 3 is a little
tight, 3.5 a little white :)
Thanks for the very fine vertical spacing controls!
best
40 matches
Mail list logo
