Carl Sorensen wrote Wednesday, August 05, 2009 1:42 PM
On 8/5/09 2:44 AM, "Trevor Daniels" wrote:
Carl, Marc
After the long discussion about naming the
new cross-head function and associated predefs
I see you have retained deadNote as the base
name.
I thought the outcome of the
Trevor Daniels wrote Wednesday, August 05, 2009 9:09 AM
Trevor Daniels wrote Thursday, July 30, 2009 9:16 PM
Mark Polesky wrote Thursday, July 30, 2009 7:06 PM
It would be nice to have some central place that explains some
"internals" concepts.
...
It would be nice to have
Carl Sorensen wrote Wednesday, August 05, 2009 3:07 PM
On 8/5/09 7:22 AM, "Trevor Daniels" wrote:
I think it was a pity that the groundwork
for a more generic approach was not laid
down right away, so we could have easily
added the aliases for all the other uses
of crossheads
I
Mark Polesky wrote Wednesday, August 05, 2009 8:21 PM
I've not been able to connect to git via SSH since Saturday,
and nothing I've tried
has worked. I'd like to take care of
that first, but I'm out of ideas.
Can you remind us what you have tried
so far?
Re-boot (obviously yes?)
Obtain fre
Graham Percival wrote Thursday, August 06, 2009 7:51 AM
On Thu, Aug 06, 2009 at 12:12:59AM +0100, Ian Hulin wrote:
This is AU section 3.2.1
--
If ‘filename.ly’ contains more than one \score block, then the
rest of the
scores will be output in numbered files, starting with
‘filename-1.p
Graham
I've just pushed another fix for broken refs resulting from your doc
reorganisation. As there seems to be no replacement nodes all I can
do is comment them out with a FIXME. Any chance you could add
replacement nodes as you go so we can fix the links properly rather
than scattering F
John Mandereau wrote Wednesday, August 05, 2009 8:47 PM
At least one of the terms listed by Mark is introduced in the
Learning
Manual: "grob" in 4.1.2 Objects and interfaces. I see this
glossary
could be a quick reference that briefly defines each term and
gives
cross-references to document
Graham Percival wrote Thursday, August 06, 2009 10:06 AM
On Thu, Aug 06, 2009 at 09:50:56AM +0100, Trevor Daniels wrote:
I've just pushed another fix for broken refs resulting from your
doc
reorganisation.
Oops, I forgot that I need to "touch foo.tely" before testing.
That
John Mandereau wrote Thursday, August 06, 2009 12:06 PM
Le jeudi 06 ao=C3=BBt 2009 =C3=A0 11:35 +0100, Trevor Daniels a
=C3=A9crit =
:
Have you tried building docs inside the source tree?
No; I'm on Windows Vista, so building isn't an option, is it?
I generated my own script
John, you wrote Thursday, August 06, 2009 3:01 PM
No; I'm on Windows Vista, so building isn't an option, is it?
No, but you can still run check-xrefs and fix-xrefs, but it will
complain about missing files markup*.tely, internals.tely and so
on.
Good. In that case I'll leave them for som
Mark Polesky wrote Thursday, August 06, 2009 3:26 PM
Anything holding up 2.13.4? By now there are so
many new things that I'd like to try, but I'm a
non-compiler, so...
I'm stuck too. Neil updated the LSR today,
so now lots of snippets require 2.13.4 and
I can no longer compile the docs easi
Neil Puttock wrote Thursday, August 06, 2009 9:58 PM
2009/8/6 Trevor Daniels :
I'm stuck too. Neil updated the LSR today,
so now lots of snippets require 2.13.4 and
I can no longer compile the docs easily, so
can't check any edits I make.
I'm sorry as always when this
Kieren
I'm not sure I understand the need for this.
Maybe I'm missing something (it wouldn't be
unusual :)
I would not normally use a lyric extender
unless the syllable had an extended duration
over several notes or was sung to a long note.
This occurs far less frequently than a 2-note
melisma.
Graham wrote Thursday, August 06, 2009 11:53 PM
Sorry, not this time. The purpose of the unstable releases is to
aid the development effort; it doesn't make sense to hold Trevor
and Mark back just because the doc build is in flux.
The MinGW build that Neil made is fine, Graham, so
there's no
Carl Sorensen wrote Friday, August 07, 2009 2:49 PM
On 8/5/09 7:19 AM, "Trevor Daniels" wrote:
Carl Sorensen wrote Wednesday, August 05, 2009 1:42 PM
If we decide to use this same function for the general case of
switching to
a cross-shaped notehead, then we will redefine it
Hi Kieren,
I'm not sure I understand the need for this.
I would not normally use a lyric extender
unless the syllable had an extended duration
over several notes or was sung to a long note.
This occurs far less frequently than a 2-note melisma.
Do you attach lyric extenders unconditionally
to
Valentin Villenave wrote Friday, August 07, 2009 9:45 PM
So, I'm thinking that we'd better junk these pseudo-options, and
ask
Seba to make HTML formatting allowed in all snippet descriptions.
Thoughts?
Sounds reasonable. Do we make it clear anywhere what html
markup is permitted in snippet
Patrick McCarty wrote Saturday, August 08, 2009 5:00 AM
On Fri, Aug 07, 2009 at 08:39:16PM -0700, Mark Polesky wrote:
Patrick McCarty wrote:
> I've just tested git's shallow cloning feature. It's pretty
> neat.
> :-)
>
> From what I can see, shallow clones would be okay for *casual*
> co
Kieren MacMillan Sunday, August 09, 2009 4:47 AM
From my point of view the main use for smallStaff (or whatever it
gets called) is for ossia staves.
Except IIRC ossia staves and solo/cue staves are usually of
different sizes, yes?
In scores for a capella vocal music a piano
accompaniment
Mark Polesky wrote Sunday, August 09, 2009 7:31 PM
Well, that's not a functional barline, it's just printed. It's
similar to putting ":|" which prints a repeat sign, but doesn't
cause LilyPond to recognize the previous section as repeated. I
guess NR 1.2.5 could make this clearer.
original par
Patrick McCarty wrote Sunday, August 09, 2009 3:36 AM
On Sat, Aug 08, 2009 at 07:21:42PM -0700, Patrick McCarty wrote:
Hmm, I just realized that the inconsistency still exists, even
with my
patch. Here's an example:
\relative c'' {
a8 a a a
a8 a a a
a16 a a8 a a
a8 a16 a a
Patrick McCarty wrote Saturday, August 08, 2009 5:33 PM
On Sat, Aug 08, 2009 at 01:59:50AM -0700, Graham Percival wrote:
A few people talked about browsing the history, which surprised
me. Whenever I want to look at history, I use the web git
interface. But evidently other people don't sha
Carl Sorensen wrote Sunday, August 09, 2009 10:59 PM
Could the two of you please take some of these examples and beam
them
manually so that I can see what they *should* do? I'll then try
to figure
out why the autobeam engraver doesn't do it.
Some explanation as to *why* it should work the w
Graham Percival wrote Monday, August 10, 2009 12:48 AM
On Sun, Aug 09, 2009 at 11:45:05PM +0200, John Mandereau wrote:
Le samedi 08 août 2009 à 13:55 -0600, Carl Sorensen a écrit :
> As a practical matter, -r first applies the changes that were
> made on origin
> (since your branch was check
Neil Puttock wrote Monday, August 10, 2009 12:31 AM
2009/8/10 Patrick McCarty :
I wonder why we are seeing different beaming patterns? I think all
of
your manually-beamed patterns are correct though.
Trevor's using the MinGW build I posted a few days ago, so it's
missing Carl's last change
Graham Percival wrote Monday, August 10, 2009 9:18 AM
On Mon, Aug 10, 2009 at 08:45:22AM +0100, Trevor Daniels wrote:
Graham Percival wrote Monday, August 10, 2009 12:48 AM
I maoing hate git.
Git is fine; the complexity comes from the
baroque structures in LilyPond. Let's be
tha
Trevor Daniels wrote Monday, August 10, 2009 8:49 AM
Neil Puttock wrote Monday, August 10, 2009 12:31 AM
2009/8/10 Patrick McCarty :
I wonder why we are seeing different beaming patterns? I think
all of
your manually-beamed patterns are correct though.
Trevor's using the MinGW bu
Carl, you wrote Monday, August 10, 2009 10:58 PM
On 8/10/09 9:14 AM, "Trevor Daniels"
wrote:
With all Carl's mods applied just the expected two
inconsistencies
remain:
\relative c'' {
a8 a a16 a a8 a a a a16 a | % wrong, should be ...
a8 a a16[ a a8] a a a[
id earlier that this is a more fundamental problem.
Trevor
- Original Message -
From: "Carl Sorensen"
To: "Trevor Daniels" ; "Neil Puttock"
; "Patrick McCarty"
Cc: "lilypond-devel"
Sent: Monday, August 10, 2009 11:25 PM
Subject:
Mark Polesky wrote Tuesday, August 11, 2009 12:25 AM
I'm git-weary but still alive. Johannes spent *hours* debugging
my problem, and eventually traced it to an undiscovered bug
in gitk that only affects Microsoft Windows...
Nice to have you operational again. Thanks Johannes!
Can you say w
Carl Sorensen wrote Friday, August 07, 2009 2:49 PM
The generic approach has now been pushed to git
247f0b6d46fd8f3253a99f95a70ce14345daa5f9
There's a generic styledNoteHeads music function that applies a
note style
to music whether or not it's in a chord construct.
deadNotes and palmMute
Johannes Schindelin wrote Tuesday, August 11, 2009 12:51 PM
On Tue, 11 Aug 2009, Trevor Daniels wrote:
Mark Polesky wrote Tuesday, August 11, 2009 12:25 AM
>
> I'm git-weary but still alive. Johannes spent *hours* debugging
> my problem, and eventually traced it to an undisco
Mark Polesky wrote Tuesday, August 11, 2009 7:18 PM
My "concept glossary" idea is now called a "technical glossary".
I thought the name was fine when it was suggested, but now I'm
realizing something -- I'd also like it to list terms that are not
specifically dealing with LilyPond *internals*.
Hi Mark
Good to see you pushing again!
But could you preface commits which affect only docs with "Docs: "
please. It helps code developers with better things to do to skip
uninteresting commits.
Trevor
___
lilypond-devel mailing list
lilypond-d
Carl Sorensen Friday, August 07, 2009 2:49 PM
The generic approach has now been pushed to git
247f0b6d46fd8f3253a99f95a70ce14345daa5f9
There's a generic styledNoteHeads music function that applies a
note style
to music whether or not it's in a chord construct.
Carl, I am part-way through
Carl Sorensen wrote Wednesday, August 12, 2009 7:32 PM
And if we're ever going to move it to a postfix operator (which is
one of
the goals of the GLISS project), now is the time, before we get a
strong
codebase of music function applications.
I'm beginning to wonder whether this is a
desira
Andrew Hawryluk wrote Thursday, August 13, 2009 4:18 AM
Long ago I noticed that the text in our PDF manuals is fully
black,
which results in rough-looking text when printed:
http://lists.gnu.org/archive/html/lilypond-devel/2008-10/msg00059.html
Attached is a patch which corrects this, and th
Mark Polesky wrote Saturday, August 15, 2009 3:26 AM
3) Make the "command index" strictly a *command* index.
Add a separate "property index" strictly for properties. It
could even be on the same page -- just the existence of a menu
with the two different node names should be enough to hel
Mark
I'm top-posting as I'm not answering any of your specific questions.
If you really want to understand how data types are defined you will
need to understand how lexers and parsers work first. To help, I've
just added a few more clues to the Technical glossary. Then you
will find all th
Werner LEMBERG wrote Monday, August 17, 2009 6:42 PM
I've just seen this change in a recent commit:
+...@seealso
+
+Installed Files:
+...@file{lily/parser.yy}
IMHO, this is not correct: lily/parser.yy does *not* get installed
at
all! Either we introduce a special macro which points to t
Graham Percival wrote Monday, August 17, 2009 10:35 PM
On Mon, Aug 17, 2009 at 05:17:08PM +0200, Reinhold Kainhofer
wrote:
Am Montag, 17. August 2009 16:08:36 schrieb Michael Käppler:
>
> > (nobody checks the regression tests for each release, for
> > example
> > -- and that's trivially don
Mark Polesky wrote Tuesday, August 18, 2009 6:04 AM
Mark Polesky wrote:
> What does this mean?
>
> ly/music-functions-init.ly
>
> 476 %% Todo:
> 477 %% doing
> 478 %% define-music-function in a .scm causes crash.
Nevermind. I'm an idiot. I get it.
Actually, strike that. What does this c
Graham Percival wrote Wednesday, August 19, 2009 1:00 PM
I get the same thing even with "make". I've reverted Trevor's
commit, although I have no clue what's wrong. These errors
generally mean that the @menu wasn't updated, but he did that
perfectly (as far as I can see). I'm baffled, but d
Mark Polesky wrote Thursday, August 20, 2009 8:59 AM
I made an attempt at cleaning up property-init.ly. I
included my revised file (not a patch) Mostly I'm
curious to know if there's anything I'm doing here
that goes against coding conventions or anything like
that. Or if I'm making things wors
I'm trying to complete the 'prob' entry in the Technical glossary.
From a position of ignorance I've come up with this:
"PRoperty OBjects, or @strong{probs} for short, are instances of
the @code{Prob} class, a simple base class for objects which have
mutable and immutable property alists. The
Marc Hohl wrote Saturday, August 22, 2009 7:30 PM
Jay Anderson schrieb:
[...]
So what do you think? Should the "SmallStaff" just
be left as a snippet?
If it is a snippet ideally I'd want to do something like:
\include "small_staff.lyi"
\score {
\new SmallStaff {...}
}
How would one make
Werner LEMBERG wrote Saturday, August 22, 2009 7:23 AM
There is a horizontal offset bug if a markup is attached to a
skip.
Look at this small example:
\paper {
ragged-right = ##f
}
foo = {
s1
\time 7/8 s8*7^"foobar"
\time 10/8
}
bar = {
R1
R8*7
}
<<
\context St
Mark Polesky wrote Sunday, August 23, 2009 11:16 PM
Carl Sorensen wrote:
Here's what I recommend (I didn't used to do this, but it
seems to be a better way to work).
git branch newfeature
git checkout newfeature
git rebase -i master
git rebase -I SHA1-ID-of-the-parent-of-branch-newfeature
Carl Sorensen wrote Monday, August 24, 2009 1:25 AM
From: Trevor Daniels [t.dani...@treda.co.uk]
Not sure these rebases are necessary if
you are going to use cherrypick rather
than merge.
Yes, your method works OK.
I use the rebase to get all of my work into
a single commit, instead of
Werner LEMBERG wrote Monday, August 24, 2009 3:08 PM
This effect seems to be a consequence of ragged-right = ##f
together
with a second bar containing a single note (or space). When the
second bar is stretched to fill the line the note gets displaced
almost to the centre of the bar. This si
It seems there has been a change in the splitting of manuals on
kainhofer. They no longer split at numbered sections but only at
the second level. So the whole of Pitches, for example, comes as a
single html page. Is this deliberate or an error?
Trevor
__
Werner LEMBERG wrote Monday, August 24, 2009 9:52 PM
I would argue against introducing this complication. Positioning
spacer rests differently to notes of the same duration does not
seem
a good idea.
Well, my example shows that it actually uses a *different*
position
compared to the full
Werner LEMBERG wrote Tuesday, August 25, 2009 6:52 AM
Both the note and the spacer in the second bar are positioned in
roughly the centre of the bar, although interestingly not quite
in
identical positions. I don't know why they differ slightly, but
you
see my point.
Here's another examp
Werner LEMBERG wrote Tuesday, August 25, 2009 6:45 AM
I think you mean "added to the snippets" (via LSR).
No, I mean documentation, since the difference in behaviour
between
full rest skips and ordinary skips must be documented properly.
I'll wait for the response to the bug report
befor
Werner LEMBERG wrote Thursday, August 27, 2009 3:11 PM
After all, it is very easy to place the markup where you want it
by
simply using two spacer notes:
foo = {
s1
\time 7/8 s8^"foobar" s8*6
\time 10/8
}
OK, I haven't thought of that solution, thanks. This should
perhaps
be added to
Werner LEMBERG wrote Tuesday, September 01, 2009 6:44 AM
Hmm. I currently can't imagine a situation where a value > 0 is
needed, so I vote to remove the setting of
#'outside-staff-priority for MultiMeasureRestText -- however,
I'm
not sure whether this has any influence to issue #495 (this
lo
Werner LEMBERG wrote Tuesday, September 01, 2009 4:30 PM
It seems sensible to have a distinct, lower, value, but something
like 40 would place it below everything else while retaining some
future flexibility.
OK. Shall I commit this or will you do that?
Werner, I'll do it, but I've had se
Joe, you wrote Tuesday, September 01, 2009 8:49 PM
Attached is a patch to extend the NR documentation on Turkish
classical
music as defined in the file makam.ly.
Thanks for this, but I'm afraid the patch has whitespace errors
and also fails to apply.
The console output says:
Applying Exten
Carl Sorensen wrote Wednesday, September 02, 2009 1:06 PM
On 9/2/09 2:41 AM, "Trevor Daniels" wrote:
So instead I propose to change the definition
of \fermataMarkup to:
fermataMarkup =
#(make-music 'MultiMeasureTextEvent
'tweaks (list
; Set the 'tex
Joe, you wrote Wednesday, September 02, 2009 4:53 PM
Trevor Daniels wrote:
Thanks for this, but I'm afraid the patch has whitespace errors
and also fails to apply.
I don't understand what 'whitespace errors' are -- sorry, this is
my
first time using texinfo and git o
Francisco Vila wrote Wednesday, September 02, 2009 4:59 PM
Hello, here are some updates to the Spanish definitions of the
Music Glossary.
Thanks. Applied to origin/master.
I've found that church modes are not translated: there is no
reference
to Ionian, Dorian etc in other languages that
Joseph Wakeling wrote Wednesday, September 02, 2009 7:48 PM
I think the attached patches should work. They should lack
trailing
whitespace and I've used git format-patch origin which I hope will
generate the patch against the head of the master branch. (Still
getting the hang of git; I'm a
Joe, you wrote Thursday, September 03, 2009 7:20 AM
Trevor Daniels wrote:
Thanks Joe. Initially these patches didn't apply either, but I
traced the reason to their having DOS (CRLF) line endings
rather than Unix (LF) line endings. When I changed that they
applied fine. (This actually
Hi Joe, you wroteThursday, September 03, 2009 10:35 AM
Trevor Daniels wrote:
I then looked at the actual mail message. You're using
Thunderbird with inline attachments and quoted-printable
encoding. This is the problem. I seem to remember
Jonathan Kulp discovering that Thunderbird m
Joseph Wakeling wrote Thursday, September 03, 2009 7:22 PM
... if the previous patch doesn't work, I hope the one attached to
this
mail will. Let me know how it goes. :-)
Still has DOS line endings :( But it's really not a problem - I can
easily change them before applying.
I didn't appl
Hi Joe, you wrote Friday, September 04, 2009 12:42 AM
As discussed on the -user list, this is a patch to start a section
in
the Specialist Notation chapter on contemporary music.
I really hope that this patch (or rather, this email containing
the
patch:-) has avoided the DOS line endings.
Reinhold
The last doc update on your server was on
1 Sep - has something broken? I see there
are several broken links following Graham's
recent reorganisation. Let me know if this
is the problem and I'll fix them.
Trevor
___
lilypond-devel maili
Graham Percival wrote Friday, September 04, 2009 10:03 PM
On Fri, Sep 04, 2009 at 09:54:38PM +0100, Trevor Daniels wrote:
The last doc update on your server was on
1 Sep - has something broken? I see there
are several broken links following Graham's
recent reorganisation. Let me kn
Hi Joe, you wrote Friday, September 04, 2009 3:49 PM
Hope the previous message works. It's a small, incremental
change, just
to see if git-send-email will work where Thunderbird clearly
doesn't ... :-)
If this is an acceptable way to send patches, shall I add a
section to
the CG describi
Reinhold Kainhofer wrote Friday, September 04, 2009 10:51 PM
Am Freitag, 4. September 2009 23:12:00 schrieb Trevor Daniels:
Graham Percival wrote Friday, September 04, 2009 10:03 PM
> Oh, I see it now. Remember that we currently need to touch any
> docs we want updated. I've jus
Graham Percival wrote Saturday, September 05, 2009 12:43 AM
On Sat, Sep 05, 2009 at 12:35:06AM +0200, Reinhold Kainhofer
wrote:
Am Samstag, 5. September 2009 00:12:44 schrieb Trevor Daniels:
> Reinhold Kainhofer wrote Friday, September 04, 2009 10:51 PM
> > It seems that the NR w
Carl Sorensen wrote Sunday, September 06, 2009 3:46 AM
On 9/5/09 7:12 PM, "Graham Percival"
wrote:
Hmm. This could be a meaningless semantic quibble, or it could
be
something that's fundamental to the docs, GLISS, and development
in general. Is a change to the autobeaming, done via
\over
Carl Sorensen wrote Saturday, September 05, 2009 2:13 PM
On 9/5/09 1:13 AM, "Trevor Daniels" wrote:
No. It's much easier to write documentation
than it is to add commands. I would not want to
delay useful additions to the documentation or to
put off a keen documentatio
Thanks Joe - applied and pushed to origin/master.
The attached patch still had DOS endings, no problem with that,
but it lacked a commit message and your email address, so I
had to add those. Your previous method of creating patches
included these in the patch. Could you use that method in futu
I've finally got around to thinking about the introduction to
parallel voices in the Learning Manual - currently sections 3.2.1
and 3.2.2. You'll remember the many discussions about the two
constructs - explicit voices and the \\ construct, and the
final agreement to introduce explicit voices f
Joseph Wakeling wrote Sunday, September 06, 2009 10:36 PM
OK, I think I've cracked the problem of patches with Thunderbird.
The
problem is that Thunderbird takes .patch files to be of mime-type
text/x-diff. Renaming the file to end in .txt changes its opinion
of
the file type and allows th
Graham Percival wrote Monday, September 07, 2009 12:53 AM
On Sun, Sep 06, 2009 at 11:22:42PM +0100, Trevor Daniels wrote:
Joseph Wakeling wrote Sunday, September 06, 2009 10:36 PM
This probably _is_ something which should be in the docs as it's
not
something you would imagine would
Joseph Wakeling wrote Monday, September 07, 2009 12:41 AM
Joseph Wakeling wrote:
the duplication of two @nodes called 'Further reading' may break
the doc
build -- just checking that now.
Duplicate node names in the same manual do break the build.
... which the attached patch should fix.
Kieren MacMillan wrote Sunday, September 06, 2009 3:34 PM
\\ is quite more convenient than explicit voices and thus an
important
idiom that makes Lilypond friendlier to the user.
Yes, but as previously discussed, the confusion it (ultimately)
causes is a poor
trade-off. The whole problem w
Kieren MacMillan wrote Monday, September 07, 2009 7:40 PM
which works fine, if I understand what you want. So I was
wondering if Trevor was referring to something else...
Yes, I was thinking more of \lyricsto, which
needs a named context, and perhaps SATB on
two staves. I originally place
Kieren MacMillan wrote Tuesday, September 08, 2009 5:08 PM
Does this mean you don't need me to immediately rework how \\
voicifies?
I think I'll go ahead with the reordering anyway,
although it might take a while, as I have limited
time at present. So let's decouple the rewrite
of docs and
Joseph Wakeling wrote Thursday, September 10, 2009 2:10 PM
What would be good is if as many contributors as possible can
reply to
this email just to OK (i) my putting copyright/licensing notices
in the
files they have contributed to and (ii) their licensing
preferences for
their contribution
I've just noticed that the line-width, set in
the paper block in ly fragments in the docs,
has changed recently. The latest development
release on lilypond.org has
\paper {
#(define dump-extents #t)
line-width = 160\mm - 2.0 * 0.4\in
ragged-right = ##t
indent = 0\mm
force-assignment = #""
Graham Percival wrote Saturday, September 12, 2009 12:00 AM
On Fri, Sep 11, 2009 at 11:16:28PM +0100, Trevor Daniels wrote:
The change from 160\mm to 5\in shortens the line
by around 33\mm, which wrecks at least one
example
It was not deliberate to change the docs lnie-width.
I that
Graham Percival wrote Saturday, September 12, 2009 12:20 PM
On Sat, Sep 12, 2009 at 09:34:35AM +0100, Trevor Daniels wrote:
Graham Percival wrote Saturday, September 12, 2009 12:00 AM
It was not deliberate to change the docs lnie-width.
I that case I'd like to change it back.
Graham Percival wrote Sunday, September 13, 2009 2:49 PM
That said, I could have done the same mistake as you did a week
ago by
moving @afourpaper to macros.itexi :-P
Ok, I'll move them out.
Thanks Graham - that will fix it. I'd have spotted
this sooner if I'd looked at learning.tely :(
Neil Puttock wrote Sunday, September 13, 2009 7:45 PM
2009/9/13 Michael Käppler :
Btw. I don't understand, why lilypond-book inserts no line-width
value when
called with fragment.
What is the reason for this behaviour?
I'm not sure, to be honest.
I think lilypond-book inserts line-wid
Graham Percival wrote Thursday, September 17, 2009 9:27 AM
There's a test windows version at
http://lilypond.org/~graham/
Again, it's not the final one, blah blah.
Downloads, installs and compiles all the snippets
in tweaks.itely just fine using Vista home premium.
Trevor
___
Graham Percival wrote Thursday, September 17, 2009 9:27 AM
There's a test windows version at
http://lilypond.org/~graham/
Again, it's not the final one, blah blah.
The installation includes a hierarchy of
directories under /usr/docs, all of which
are empty. Presumably an error?
Trevor
_
Graham Percival wrote Sunday, September 20, 2009 8:26 PM
I was confused because Joseph keeps on talking about wanting to
copy "code" from the documentation, and Trevor Daniels recently
said "you know what? you guys are nutters. Do whatever you want
with my stuff, now shut
Neil Puttock wrote Monday, September 21, 2009 10:23 PM
Recently I've been getting loads of error messages when building
the
docs; they all relate to Texinfo macros which don't have
arguments.
Has the version of texinfo you are using changed? I use texi2html,
admittedly a very old version, f
Graham Percival wrote Monday, September 28, 2009 8:14 PM
On Sun, Sep 27, 2009 at 06:53:26PM -0600, Carl Sorensen wrote:
On 9/27/09 11:55 AM, "John Mandereau"
wrote:
> Le dimanche 27 septembre 2009 à 17:37 +0100, Graham Percival a
> écrit :
> Certainly. However, when we decide time has
I much prefer the Glossary page. It is much clearer. The space on
the left will accommodate a longer description easily and the
reading instructions are grouped neatly together on the right.
Trevor
- Original Message -
From: "Graham Percival"
To:
Sent: Sunday, October 04, 2009 12
Hi Andrew
Generally looking good. A few comments, mostly minor:
a) Page 2 has the phrase "Not let down, we created a font of musical
symbols"
"Not to be deterred," or "Undiscouraged," would be better.
b) Where you compare the shapes of the quarter rests on page 2 it
might be better to draw
Graham Percival wrote Monday, October 12, 2009 3:57 PM
Try another one.
Can you remind me where it is. The mingw binaries on
linuxaudio don't include it.
As an aside, I'm traumatized. Three people in the lab did a
double-take and exclaimed "you're running WINDOWS?!".
Lots of people hav
Installs and runs fine under Vista, at least with a couple of short
tests. I'll try something more substantial later ...
Trevor
- Original Message -
From: "Graham Percival"
To: "Trevor Daniels"
Cc:
Sent: Monday, October 12, 2009 4:42 PM
Subject: Re: 2.13.
Marc
Should not the \revert be limited to TabVoice to avoid reverting the
property in other contexts? The same could be said for some of the
other \reverts too.
Trevor
- Original Message -
From: "Marc Hohl"
To: "Lily-Devel List"
Sent: Thursday, October 15, 2009 7:14 AM
Subject:
Marc Hohl wrote Thursday, October 15, 2009 9:36 AM
Trevor Daniels schrieb:
Marc
Should not the \revert be limited to TabVoice to avoid reverting
the
property in other contexts? The same could be said for some of
the
other \reverts too.
Yes, of course. Attached is a reworked patch
Marc Hohl wrote Friday, October 16, 2009 7:30 AM
Trevor Daniels schrieb:
Marc Hohl wrote Thursday, October 15, 2009 9:36 AM
Trevor Daniels schrieb:
Marc
Should not the \revert be limited to TabVoice to avoid
reverting the
property in other contexts? The same could be said for some of
David
It would make a great snippet!
Adding
\textLengthOn
\override TextScript #'padding = #1.5
improves the layout.
If you could add it to the LSR I'll include it in the Notation
Reference.
Trevor
- Original Message -
From: "David Kastrup"
To:
Sent: Saturday, October 17, 2009
101 - 200 of 1243 matches
Mail list logo
