Eluze wrote Tuesday, August 10, 2010 2:54 PM
happenstance or intention?
I don't know, but I'm reluctant to cement this change
into the docs until someone confirms it is working as
intended.
Looks useful though. Thanks for pointing it out.
if you specify a folder name as output option the
Graham, Patrick, Andrew, others?
Is there any requirement to continue with the alternate
css files in the web? These were set up, IIRC, to enable
people to view and comment on alternative designs, but
we seem to have settled the design now.
The files in question are:
lilypond.css
Eluze wrote Tuesday, August 10, 2010 2:54 PM
if you specify a folder name as output option the output will be
directed to
that folder and the name of the file is preserved
so i suggest the following change/addition - or similar - in the
application usage manual:
1.2 Command-line usage
Graham, you wrote Tuesday, August 10, 2010 4:57 AM
actually, now that I think about it some more, make website
really has nothing to do with the compiled scripts in scripts/ or
python/. Just doing
rm -rf out-website/
make website
should get you the complete website. If you have any error
:
No such file: text.itely
Search path:
.:/media/lilypond/lilypond-git/Documentation/:/media/lilypond/lilypond-git/Documentation/:/media/lilypond/lilypond-git/Documentation//snippets/:out-website
Trevor
- Original Message -
From: Trevor Daniels t.dani...@treda.co.uk
To: Graham
Mike Solomon wrote Thursday, August 12, 2010 10:16 AM
I added an extra symbol check to my event class patch:
http://codereview.appspot.com/1867050
Also, I have a regression test that creates a spanner engraver
from the
scheme end using this function (said regtest could also be turned
Graham
My recent activity has shown my RSI is not too bad now,
provided I don't spend long periods at the keyboard.
I'd like to review NR 2.1 Vocal music and try to get
that into better shape by dealing with all the TBC,
TODO's etc. before we release 2.14. First I'd like to
complete the
Graham Percival wrote Thursday, August 12, 2010 7:38 PM
On Thu, Aug 12, 2010 at 07:07:45PM +0100, Trevor Daniels wrote:
However, I realise 2.14 might happen any time real soon
now, so I'd make sure any changes I pushed were complete
and an improvement over what was there before, so that
2.14
Graham Percival wrote Friday, August 13, 2010 7:28 AM
On Thu, Aug 12, 2010 at 03:05:38PM -0700, -Eluze wrote:
The lilypond executable may be called as follows from the command
line.
lilypond [option]... file...[[1]file.log] [2file.txt]
1 and 2 (and, for the matter, ) have nothing to
The mingw binary of 2.13.30 gives the following error
under Vista on my system:
Running lilypond-book
Traceback (most recent call last):
File c:/program files/lilypond/usr/bin/lilypond-book.py, line
86, in ?
import book_base as BookBase
File out/book_base.py, line 4, in ?
File
Patrick McCarty wrote Sunday, August 15, 2010 7:27 AM
On Sat, Aug 14, 2010 at 5:23 PM, Patrick McCarty
pnor...@gmail.com wrote:
On Sat, Aug 14, 2010 at 4:10 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
The mingw binary of 2.13.30 gives the following error
under Vista on my system:
Running
Eluze wrote Sunday, August 15, 2010 10:20 AM
Trevor Daniels wrote:
The mingw binary of 2.13.30 gives the following error
under Vista on my system:
Running lilypond-book
Traceback (most recent call last):
File c:/program files/lilypond/usr/bin/lilypond-book.py, line
86, in ?
import
Francisco
I've just updated a snippet which contained translated
texidoc strings. Only the LilyPond code was changed,
not the texidoc strings themselves. I also updated
the committishes in the four texidocs folders. These
were in commits:
bfc88203ac2572737480e78ef2635ed35b458441
Valentin Villenave wrote Monday, August 16, 2010 10:56 PM
As for the 2.1 headword, for now, let's just start working on the
documentation itself, Trevor and I; when the time comes my patch
will
still be there, or I'll have had a chance of cooking something
more
appropriate by then.
OK.
Ian Hulin wrote Tuesday, August 17, 2010 7:45 PM
I'm just recovering from building and testing my first docs patch
*{s\h/u\d/d\e/r\}*. As I didn't know any better, I had to resort
to
doing make doc and make doc-clean while developing the patch.
Firstly, what's the grown-up doc developer's
Carl Sorensen wrote Tuesday, August 17, 2010 9:45 PM
On 8/17/10 2:24 PM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Ian Hulin wrote Tuesday, August 17, 2010 7:45 PM
Firstly, what's the grown-up doc developer's way of this without
having
to kick off your make doc run and then leave
Actually, Carl, you would be better off starting with
this script. I've just realised it's changed quite
a bit since I posted the message a year ago. It's
still a bit of a mess though, and you'll obviously
have to change the bits specific to me, but it'll
give you a useful start. You'll also
Trevor Daniels wrote Wednesday, August 18, 2010 12:01 AM
You'll also need
refcheck.py to check all the cross-references match,
but this is rather tied to my particular file
structure. I'll have a look at generalising it so
I can put it in scripts/auxiliar.
I've done this now. See scripts
Carl Sorensen wrote Wednesday, August 18, 2010 5:16 PM
Thanks to Trevor, we now have some scripts that will allow you to
quickly test only the section of the documentation you are working
on.
These scripts are now described in CG 4.6 Scripts to ease doc
work.
I see you noticed the script
Neil Puttock wrote Wednesday, August 18, 2010 9:41 PM
On 18 August 2010 13:13, Trevor Daniels t.dani...@treda.co.uk
wrote:
I've done this now. See scripts/auxiliar/ref_check.py.
Its action is driven by scripts/auxiliar/ref_check.tely
Just run it at the top level in the git repository
Trevor Daniels wrote Tuesday, August 17, 2010 1:23 PM
Valentin:
I've just pushed a patch which sets out NR 2.1 the way I want it
to
be. We can now begin work on fleshing out all the missing bits.
To avoid merge conflicts we shall need to avoid changing the
same parts of vocal.itely
Graham Percival wrote Thursday, August 19, 2010 6:43 PM
On Thu, Aug 19, 2010 at 6:40 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
BTW, there are several snippets in the LSR which would be good
to incorporate but which are not tagged with docs. It's a real
pain
for me to do this
Yes
Francisco Vila wrote Friday, August 20, 2010 4:20 PM
2010/8/17 Trevor Daniels t.dani...@treda.co.uk:
I've just updated a snippet which contained translated texidoc
strings.
Only the LilyPond code was changed,
not the texidoc strings themselves. I also updated
the committishes
Reinhold Kainhofer wrote Monday, August 23, 2010 6:08 PM
Am Donnerstag, 19. August 2010, 09:43:11 schrieb Phil Holmes:
Trevor Daniels t.dani...@treda.co.uk wrote in message
news:3df57d198d544514adecfbe3c1278...@trevorlaptop...
Reinhold's refactoring of lilypond-book modules was
first
Phil Holmes m...@philholmes.net wrote in message
news:i53pqa$tp...@dough.gmane.org...
Trevor Daniels t.dani...@treda.co.uk wrote in message
news:305ede3e0e3f4cdc926db8734c558...@trevorlaptop...
However, I'm now back to my original problem first reported
in
http://lists.gnu.org/archive/html
Graham Percival wrote Thursday, August 26, 2010 1:06 PM
CG 1.3 Mentors
Alternately, do any developers want to offer to mentor 1-4 new
contributors? I'm comfortable keeping this section as long as we
have
at least 1 official mentor handling at least 1 contributor.
I'm happy to mentor tyro
Wols Lists wrote Thursday, August 26, 2010 2:19 PM
Learning a bit at a time ... how do I add properties? I've used
\set
ChordNames.capoFret = #3, but it's a new property, and it's
objecting,
as you can see. I've added it to the read section of the
ADD_TRANSLATOR macro of
Trevor Daniels wrote Thursday, August 19, 2010 6:40 PM
I've finished and pushed the first pass through 2.1.7 Choral.
I'll begin work on 2.1.9 Chants hymns and psalms next.
First pass through 2.1.9 Choral done.
I'll look at 2.1.8 Opera and stage musicals next.
Any chance you could look
Graham Percival wrote Friday, August 27, 2010 9:54 PM
On Thu, Aug 26, 2010 at 10:41 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
First pass through 2.1.9 Choral done.
I'll look at 2.1.8 Opera and stage musicals next.
Any chance you could look over and comment on 2.1.7 and 2.1.9
Graham Percival wrote Friday, August 27, 2010 9:54 PM
Let's deal with 2.1.1 first.
I know you didn't say to look at NR 2.1.1, but I noticed that you
used
Common references for vocal music instead of the standard
References for vocal music.
Yes, this was because there are specific
Reinhold Kainhofer wrote Sunday, August 29, 2010 8:33 PM
Thanks, Trevor, for you bisecting... The culprit is actually not
the
refactoring, but a bug fix I did before the refactoring (commit
4da9fc65cbf74f4cbbdb01add4d5f341a16f5065 at 10.06.10 13:01).
The problem I fixed with it was quite
Graham Percival wrote Monday, August 30, 2010 12:02 AM
On Sun, Aug 29, 2010 at 11:25:47PM +0100, Trevor Daniels wrote:
I have to copy an old version of
lilypondbook into every new release in order to get
a working version. We can't expect users to do that.
I'm confused about what's going
Graham Percival wrote Sunday, August 29, 2010 9:48 PM
On Sun, Aug 29, 2010 at 07:09:01PM +0100, Trevor Daniels wrote:
I think we need to reorganise the first few sections
of Vocal a little.
I like it. You have slightly more inside 2.1.1 than I would have
initially guessed, but I've
Graham Percival wrote Friday, August 27, 2010 9:54 PM
Anyway, 2.1.7.
[snip]
Setting annotate-spacing = ##t in the layout block...
Could I convince you to remove that part, and just link to
Displaying
spacing ?
Done
I'd rather that you @ref{Fitting music onto fewer pages} rather
than
Graham Percival wrote Friday, August 27, 2010 9:54 PM
- not related to Vocal, but I winced a bit when seeing
@ref{Lines}.
It might be better to rename this to Expressive marks as lines
or
Line-style expressions or something... Lines by itself looks
fine
if you're looking at the ToC, but by
Eluze wrote Friday, September 03, 2010 11:03 PM
Reinhold Kainhofer wrote:
Am Freitag, 3. September 2010, um 22:49:50 schrieb -Eluze:
New option -dinclude-settings=INCLUDEFILE.ly, which causes
lilypond to
include the given file before the score is processed. This
allows the
i have tried
Alexander Kobel wrote Saturday, September 04, 2010 11:11 AM
On 2010-09-04 00:35, Trevor Daniels wrote:
Am Freitag, 3. September 2010, um 22:49:50 schrieb -Eluze:
my command was: lilypond -V -dinclude-settings
c:\data\ly\includes\myTestInit.ly test.ly
what is wrong?
No idea. Your file
Eluze wrote Saturday, September 04, 2010 12:40 PM
now i found that it works if i rename the lilypond file and start
lilypond
with the full specification:
c:\program files\lilypond2.13.32\usr\bin\lilypond
-dinclude-settings=c:/data/ly/includes/myTestInit.ly test.ly
but not with
c:\program
copied to -Devel ..
- Original Message -
From: Trevor Daniels t.dani...@treda.co.uk
To: eluze elu...@gmail.com
Sent: Sunday, September 05, 2010 12:08 AM
Subject: Re: -dinclude-settings=INCLUDEFILE.ly
eluze wrote Saturday, September 04, 2010 10:36 PM
thanks Trevor - that works
Reinhold Kainhofer wrote Monday, September 06, 2010 8:29 PM
Am Montag, 30. August 2010, 01:48:46 schrieb Reinhold Kainhofer:
Am Montag, 30. August 2010, um 00:25:47 schrieben Sie:
I don't really see any other way to turn the input path to an
absolute path
than calling os.path.abspath, in
Graham Percival wrote Friday, August 27, 2010 9:54 PM
2.1.9 Chants psalms and hymns
I've just pushed these changes:
- To remove the stem set the transparent property of the Stem
grob to
#t... An alternative is set the length property to 0.
Please don't talk through the code. I'm a
Hi Graham
ref_check.py has been giving warnings for a couple of weeks now:
File Documentation/we-wrote.itexi referenced in WE but not found
File Documentation/others-did.itexi referenced in WE but not
found
WE is web.texi (and any @included files).
Are these files created during the
Graham Percival wrote Tuesday, September 07, 2010 8:14 PM
On Tue, Sep 07, 2010 at 05:50:54PM +0100, Trevor Daniels wrote:
File Documentation/we-wrote.itexi referenced in WE but not
found
File Documentation/others-did.itexi referenced in WE but not
found
Are these files created
Graham Percival wrote Tuesday, September 07, 2010 8:14 PM
On Wed, Sep 01, 2010 at 09:15:26AM +0100, Trevor Daniels wrote:
Graham Percival wrote Friday, August 27, 2010 9:54 PM
- do you absolutely need to use an @example rather than
@lilypond
for
the page-separator-markup ?
That said, we
Graham Percival wrote Wednesday, September 08, 2010 12:31 AM
On Wed, Sep 08, 2010 at 12:15:18AM +0100, Trevor Daniels wrote:
Graham Percival wrote Tuesday, September 07, 2010 8:14 PM
Hmm... I'm not certain about the paper-size and indent.
Happy to remove paper size and landscape, and book
Hi Phil
Could you add a staff tag to this snippet please:
Setting system separators
Thanks
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Graham Percival wrote Wednesday, September 08, 2010 12:15 PM
On Wed, Sep 08, 2010 at 10:02:24AM +0100, Trevor Daniels wrote:
The main problem is the full A4 page length, complete
with the standard lilypond footer. Landscape was
used to reduce this a bit.
I can get round the horizontal
James Bailey wrote Wednesday, September 08, 2010 5:34 PM
The current solution for lyrics independent of
notes is predicated on the idea that the lyrics
should be attached to some voice. Since \lyricmode
just tells lilypond that the entry will be text
rather than notes, why not simply use
Trevor Daniels wrote Wednesday, September 08, 2010 12:15 AM
Graham Percival wrote Tuesday, September 07, 2010 8:14 PM
On Wed, Sep 01, 2010 at 09:15:26AM +0100, Trevor Daniels wrote:
Graham Percival wrote Friday, August 27, 2010 9:54 PM
- can't you do \layout { \context { \dynamicsUp
Graham Percival wrote Friday, August 27, 2010 9:54 PM
Pointing a psalm
- I got a bit lost here. Could you add a @lilypond to illustrate
some
(or all) of those points (no pun intended)?
I've just pushed an expanded version of this section
with several illustrative examples.
Trevor
Trevor Daniels Thursday, August 26, 2010 10:41 PM
Trevor Daniels wrote Thursday, August 19, 2010 6:40 PM
I've finished and pushed the first pass through 2.1.7 Choral.
I'll begin work on 2.1.9 Chants hymns and psalms next.
First pass through 2.1.9 Chants etc done.
I'll look at 2.1.8 Opera
Graham Percival wrote Saturday, September 11, 2010 8:36 PM
Does anybody deal with lilypond source code on windows itself,
instead
of lilybuntu? Trevor?
I do _all_ my doc work on Windows, with a Windows
git repository. I have ubuntu available in a
VM, but it causes a significant slow-down
Graham Percival wrote Saturday, September 11, 2010 8:30 PM
On Sat, Sep 11, 2010 at 9:08 AM, Trevor Daniels
t.dani...@treda.co.uk wrote:
2.1.8 Opera and stage musicals ready for review
Err... 2.1.6 in today's current git? ok, doing so. I've
forgotten
anything else we've discussed about
Mark Polesky wrote Sunday, September 12, 2010 7:45 PM
Is there a way to bypass the automatic obscuring of email
addresses on any of the mailing list servers?
There may be, but I think the recent discussions about
the mailing lists have made it pretty clear that the
LilyPond lists are not
Damn! Hit the send key accidently before I'd finished.
Here's the full reply:
Mark Polesky wrote Sunday, September 12, 2010 7:45 PM
Is there a way to bypass the automatic obscuring of email
addresses on any of the mailing list servers?
There may be, but I think the recent discussions
Graham Percival wrote Tuesday, September 14, 2010 2:24 PM
On Tue, Sep 14, 2010 at 03:11:53PM +0200, Valentin Villenave
wrote:
It's not much, but since it does change quite a few lines (in a
such
critical source file, on top of that), there's no way I'm gonna
try
and push that myself :-)
Valentin Villenave wrote Wednesday, September 15, 2010 12:42 AM
On Tue, Sep 14, 2010 at 6:11 PM, Graham Percival
gra...@percival-music.ca wrote:
On Tue, Sep 14, 2010 at 4:27 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
You know, after rebuffs like this it's hardly
surprising you don't
percival.music...@gmail.com wrote Wednesday, September 15, 2010
3:05 PM
[snip the meat]
This breaks the doc build. *cough* grumpily glances around to
make
sure that David isn't lookingyou idiot/grumpy
fluffy
I implore you, oh kind and gentle contributor, to check a full
build,
from
Mark Polesky wrote Saturday, September 18, 2010 7:23 PM
This patch should prevent the type of confusion that
leads to bug #45:
http://code.google.com/p/lilypond/issues/detail?id=45
Comments/objections? Okay to push?
I like it; much improved! I (more or less[1]) agree
with Graham's
Mark Polesky wrote Sunday, September 19, 2010 7:51 AM
Carl Sorensen wrote:
Well, the Notation Reference is supposed to contain all
the information necessary to understand all the notation.
If the information on voices isn't in the Notation
Reference, then we'll need to have links from the
Keith E OHara wrote Monday, September 20, 2010 12:38 AM
I am suggesting a new @knownissues for the Notation Reference
2.2.1. The corresponding bug tracker issues are 1043, 439, and
36. If issue 1043 is solved, the second paragraph of my
suggestion will become obsolete.
I wrote the
Mark Polesky wrote Tuesday, September 21, 2010 6:35 AM
% Is there a way to target a specific context (eg. one of
% several Staff contexts) from within the \layout block?
I don't believe so. Modifying a single named context
is the only reason for the continued existence of the
ungainly
markpolesky wrote Thursday, September 23, 2010 3:51 PM
On 2010/09/22 14:53:15, Graham Percival wrote:
Documentation/notation/simultaneous.itely:392: @example
Can't this @example be removed, now that there's the
@lilypond just below it?
as I think more about visual-impairment accessibility,
James Lowe wrote Wednesday, September 29, 2010 10:57 PM
The current example I am having problems with is in 5.1.4
Modifying context plug-ins.
The example in the current document is:
---
@lilypond[quote,relative=1,ragged-right,verbatim,fragment]
This should be
@lilypond[quote,verbatim]
markpolesky wrote Saturday, October 02, 2010 5:09 PM
Okay, here we go...
Hooke's law: F=-kx
x is the displacement of the end of the spring
from its equilibrium position (in SI units: m);
F is the restoring force exerted by the material
(in SI units: N or kg·m/s^2); and
k is
David Kastrup wrote Sunday, October 03, 2010 3:22 PM
push = -\tweak #'side-axis #X ^\markup { \musicglyph
#accordion.push }
pull = -\tweak #'side-axis #X ^\markup { \musicglyph
#accordion.pull }
\score {
\repeat unfold 8 { c'-1\push c'-1\pull }
}
Why does this work nice with \push, and not
Mark Polesky wrote Monday, October 04, 2010 11:14 PM
Usually when I propose things like this, they're shot down
pretty fast, but here goes anyway.
It took me a while to mentally connect the names of the
vertical spacing variables with their specific domains. For
example, I think it's
Keith E OHara wrote Tuesday, October 05, 2010 7:18 AM
In the existing @knownissues for cadenzaOn, I suggest adding one
sentence (in context below) encouraging manual beams. Users might
*think* autobeaming works through cadenzas, and it does for a
while, but it will not through longer
Mark Polesky wrote Tuesday, October 05, 2010 7:09 PM
http://lists.gnu.org/archive/html/lilypond-devel/2010-10/msg00070.html
Let me know what you guys think; it would be nice to achieve
consensus on this one.
I'm with Carl on this. I agree with all his comments.
Further to my suggestion to
Arno Waschk wrote Wednesday, October 06, 2010 1:27 PM
why does the following:
[snip
give a small piano part (which i expected) but a normal sized
bassPart Staff?
It does give a small bassPart here (2.13.34).
What do you have in bassPart?
Trevor
Mark Polesky wrote Wednesday, October 06, 2010 4:46 PM
I also think the name 'space is misleading; I propose
'default-distance. Opinions?
I'd be happy with that change too.
Mark
Trevor
___
lilypond-devel mailing list
Graham
I've just pushed a patch to NR 2.1 Vocal music which provides a
first draft for the last of the blank sections marked TBC (To Be
Completed). I believe it's now in a much better shape than it was,
even though much of the chapter is in first draft state.
Next up are the 19 TODOs, and
James wrote Tuesday, October 12, 2010 1:27 PM
On 12/10/2010 12:54, David Kastrup wrote:
Jamesjames.l...@datacore.com writes:
Hello,
On 12/10/2010 10:13, Alexander Kobel wrote:
On 2010-10-09 17:46, Mark Polesky wrote:
CURRENT NAME PROPOSED NAME
-
top-system
Graham Percival
Yes, but I see some weaknesses in our docs.
- Glossary: staff should link to system
- Glossary: both staff and system could benefit from images
- Learning: add some link(s) to Glossary: system. Currently we
have none!
gperc...@futoi:~/src/lilypond/Documentation/learning$
Valentin Villenave wrote Wednesday, October 13, 2010 4:03 PM
Hi Trevor, here's a minor patch for Vocal music. Nothing too
extraordinary so far, I quite like what you've done!
I've done about a third of the file, I plan to work on the rest
later
(though it may have to wait for a while :)
David Kastrup wrote Thursday, October 14, 2010 8:42 AM
Carl Sorensen c_soren...@byu.edu writes:
On 10/13/10 2:40 PM, David Kastrup d...@gnu.org wrote:
The point is that we want a sane way of specifying document
layout
parameters. The current naming scheme resembles that desire.
The
David Kastrup wrote Thursday, October 14, 2010 10:05 AM
Trevor Daniels t.dani...@treda.co.uk writes:
Although this is a good point, the problem is not as
stark as this might suggest. There are many situations
when writing LilyPond code when score-wide settings are
inappropriate
Valentin Villenave wrote Sunday, October 17, 2010 4:57 PM
On Tue, Sep 7, 2010 at 1:01 AM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Looks good to me. I'll confirm when the GUB
2.13.33 for Windows is available.
sorry for bumping this discussion, but: where are we wrt this
problem
Valentin
There's a TODO in vocal.itely that I don't understand:
902 @c TODO: document \new Staff Voice \lyricsto bug
If it really is a bug then we shouldn't be documenting
it anyway, but I'd like to know what it means first.
Do you know which bug it is referring to?
Trevor
Valentin Villenave wrote Monday, October 18, 2010 1:47 PM
On Mon, Oct 18, 2010 at 12:03 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
There's a TODO in vocal.itely that I don't understand:
902 @c TODO: document \new Staff Voice \lyricsto bug
If it really is a bug then we shouldn't
Keith E OHara wrote Monday, October 18, 2010 11:40 PM
I suggest (diff attached) removing the part about
instrumentCueName in favor of a fuller example for \killCues. The
manual teaches markup elsewhere; the challenge with cue-note
labels is to let the label appear with the cue notes in
Keith E OHara wrote Tuesday, October 19, 2010 12:21 AM
One thing worth discussing is that I use the verb to cue
differently from the original author.
I believe that to cue is to *give* a signal for someone else to
begin action. So the instrument playing just before the singer
begins is
Trevor Daniels wrote Tuesday, October 19, 2010 9:35 PM
Keith E OHara wrote Tuesday, October 19, 2010 12:21 AM
Suggestions attached as a diff,
I'm happy to push this as is. Many thanks Keith.
Pushed to git pretty well as you suggested, Keith, and snippet
updated
in git.
Changed
Keith E OHara wrote Tuesday, October 19, 2010 10:34 PM
On Tue, 19 Oct 2010 13:34:05 -0700, Trevor Daniels wrote:
If no one objects soon I shall push it.
James Lowe made comments that you might not have seen yet. I see
where he is coming from, but I hope my answer explained the
purpose
down to 2.1.7.
Trevor
- Original Message -
From: James Bailey derhindem...@googlemail.com
To: lilypond-devel@gnu.org; Trevor Daniels
t.dani...@treda.co.uk
Sent: Wednesday, October 20, 2010 5:55 PM
Subject: NR 2.1 suggestions
These are just some things that I noticed.
2.1.1 Entering
Valentin Villenave wrote Wednesday, October 20, 2010 7:48 PM
On Wed, Oct 20, 2010 at 7:20 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Many thanks for your comments. At first glance they all seem
pertinent.
I'll have a look at fixing them up tomorrow.
I've taken the liberty to apply
James Lowe wrote Saturday, October 23, 2010 8:00 PM
While scanning through NR 1.2.2 the last section I came across the
line
When a multi-measure rest immediately follows a @code{\partial}
setting, resulting bar-check warnings may not be displayed.
Does anyone therefore know when I
Valentin Villenave wrote Saturday, October 23, 2010 9:54 PM
On Thu, Oct 21, 2010 at 4:53 AM, carl.d.soren...@gmail.com
wrote:
I like this idea as a way to get the functionality you want in
the short
term. But I don't like it for the long term. I think the
long-term
syntax needs to be
Mark Polesky wrote Friday, October 29, 2010 11:27 PM
Here are my proposals for renaming the properties related to
Vertical spacing inside systems.
* * * * * * * * * * * * * * *
I've thought about it, and I think I slightly favor the term
loose line over non-staff line; the word loose is
Mark Polesky wrote Tuesday, November 02, 2010 8:56 PM
Renaming proposals, round 2:
CURRENT NAME PROPOSED NAME
-
next-staff staff-staff
default-next-staff default-staff-staff
inter-staffnonstaff-staff
I'd go with Carl's suggestion of
Carl Sorensen wrote Wednesday, November 03, 2010 11:00 PM
On 11/3/10 2:49 PM, Mark Polesky markpole...@yahoo.com wrote:
Trevor wrote:
I wonder if affinity/nonaffinity are optimal. Are they
better than relatedstaff/unrelatedstaff?
Or target/opposite, reference/opposite,
Valentin Villenave wrote Thursday, November 04, 2010 12:10 AM
On Thu, Nov 4, 2010 at 12:58 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Renaming proposals, round 3:
CURRENT NAME PROPOSED NAMETD's PREFERENCE
Good work, Mark.
I'd prefer to see your image in the docs rather than text.
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: lilypond-devel lilypond-devel@gnu.org
Sent: Friday, November 05, 2010 11:17 PM
Subject: solved: reference points for non-staff lines
Valentin Villenave wrote Saturday, November 06, 2010 12:00 AM
On Sat, Nov 6, 2010 at 12:44 AM, David Kastrup d...@gnu.org
wrote:
Trevor Daniels t.dani...@treda.co.uk writes:
I'd prefer to see your image in the docs rather than text.
Just be sure you look your best.
ROTFL!
Me too
Mark Polesky wrote Saturday, November 06, 2010 5:32 PM
7 proposals for renaming the 'space alist-key have been
discussed, but a decision has not yet been made. And I just
added an 8th proposal (initial-distance).
To recap, I think the arguments *for* each of these are
mostly self-evident,
Keith E OHara wrote Sunday, November 07, 2010 2:54 AM
On Sat, 06 Nov 2010 18:20:08 -0700,
lilypond-devel-requ...@gnu.org wrote:
[...]
And lastly, I still think reference/opposite is better than
related/unrelated:
nonstaff-referencestaff
nonstaff-oppositestaff
But I won't protest. Any last
Mark Polesky wrote Sunday, November 07, 2010 12:46 AM
Carl Sorensen wrote:
9) initial-separation
* longer but describes the meaning more accurately now
we have an item-item-spacing format
I vote for 8 or 9.
9.
Does this entail changing 'minimum-distance to
'minimum-separation?
Keith E OHara wrote Sunday, November 07, 2010 1:19 AM
On Wed, 27 Oct 2010 00:24:33 -0700, Graham Percival
gra...@percival-music.ca wrote:
On Tue, 26 Oct 2010 00:47:01 -0700, Graham wrote:
This is directed at people saying I can't do anything to
help...
I need a committing, not
remain open and transparent to the end.
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: lilypond-devel lilypond-devel@gnu.org; Carl Sorensen
c_soren...@byu.edu; Trevor Daniels t.dani...@treda.co.uk
Cc: Joe Neeman joenee...@gmail.com
Sent: Sunday, November 07, 2010 8
Valentin Villenave wrote Sunday, November 07, 2010 10:35 AM
Greetings everybody, here's a patch that (hopefully) addresses the
low-priority issue 1365.
I'm not sure if we've ever used convert-ly to insert comments in
.ly
files, but I do think we should in this specific case: the
501 - 600 of 1527 matches
Mail list logo
