Hi Graham
With Vista Home Premium and 2.13.10-1.mingw.exe:
Downloaded - OK
Installed - OK
Lilypad - 2 issues
I don't run with administrator privileges
so can't save to /Public/Desktop. Saved in
my 'home' folder. Then OK, except that pdf
does not display the url (Never looked for
this
Reinhold Kainhofer wrote Thursday, December 31, 2009 11:26 AM
Am Donnerstag, 31. Dezember 2009 11:29:14 schrieb Trevor Daniels:
convert-ly - OK, except
Happened to try a file with \version 2.10
This causes a python index error.
Ouch, convert-ly assumed that all version strings always
Graham Percival wrote Friday, January 01, 2010 2:18 AM
The recent problem with end-of-line in mingw is (believed to be)
fixed;
It is. Thanks Patrick!
In testing I noticed another niggle. Clicking on
the url which now appears in the pdf causes Adobe
Reader to fire up a browser, as it
Carl Sorensen wrote Tuesday, December 29, 2009 6:27 PM
On 12/29/09 8:41 AM, Carl Sorensen c_soren...@byu.edu wrote:
I think I've got a consistent idea now. I think I can add a
property
(probably 'details to avoid namespace pollution, but maybe
timeSignatureDefaults) to the TimeSignature
Graham Percival wrote Saturday, January 02, 2010 6:47 AM
Grand LilyPond Input Syntax Stabilization (GLISS)
It's up, such as it is:
http://lilypond.org/~graham/gliss/
Looks promising. Nice overview of the issues.
I'll be happy to be part of the discussions when
they start.
Trevor
Mark Polesky wrote Tuesday, January 05, 2010 8:21 AM
Graham Percival wrote:
I think everybody liked the idea of the intro chapter,
even if there's slight uncertainty over one section of it
(i.e. lily-git). Let's get the part(s) that everybody
agrees with done.
Okay, I've attached a patch
Mark Polesky wrote Wednesday, January 06, 2010 4:18 AM
Trevor Daniels wrote:
The section headings need to make it clearer what audience
is being addressed. Perhaps
Summary for experienced Unix developers
Full details for new contributors
Then of course there is a lot more to add
Graham Percival wrote Sunday, January 10, 2010 1:35 PM
On Sun, Jan 10, 2010 at 09:36:05AM -, Trevor Daniels wrote:
Graham Percival wrote Saturday, January 09, 2010 10:19 AM
In the past few months, we've had a number of developers being
surprised at some of the build system changes
Graham Percival wrote Monday, January 11, 2010 11:30 AM
That said, a few more comments:
- if you're going to go to all this effort, please eliminate the
git
on windows section -- for each portion of the (unix-aimed) docs,
just
dump the relevant windows instructions on the bottom of the
Mark Polesky wrote Tuesday, January 12, 2010 4:03 AM
Graham Percival wrote:
I think a fair chunk of it will be wasted effort, but it's
*your* effort to waste.
Geez, Graham, sometimes I wish you *would* mince a few words
from time to time! I don't think it's a waste at all. I
remember
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 cut
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
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
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
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
Trevor Daniels wrote Wednesday, January 13, 2010 11:18 AM
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
Joseph Wakeling wrote Thursday, January 14, 2010 12:11 PM
Sometime soon I must get back onto the Contemporary Music docs.
That would be good! Happy to help when you're ready.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Reinhold Kainhofer wrote Friday, January 15, 2010 11:01 PM
Am Freitag, 15. Januar 2010 18:24:55 schrieb Joe Neeman:
On Fri, 2010-01-15 at 18:08 +0100, Reinhold Kainhofer wrote:
If you can send us an example of what it looks like (so that we
don't
have to guess which settings you will set
Reinhold Kainhofer wrote Saturday, January 16, 2010 11:32 AM
Here's a file with all different spacings from 2.0 to 4.0...
Looking at some scores with two lyrics lines (mostly oratorios
with two
different language), I would tend to choose 2.8 or 3.0.
2.8 looks good to me.
Trevor
Graham Percival wrote Saturday, January 16, 2010 10:26 PM
One idea that I've been considering for over a year is making a
social mailing list for lilypond developers.
Is there any interest in this?
Yeah - sounds fun. I miss the banter between
you and Valentin. And, more importantly,
Marc Hohl wrote Monday, January 18, 2010 8:13 PM
Marc Hohl schrieb:
Neil Puttock schrieb:
2010/1/8 Marc Hohl m...@hohlart.de:
Hmmm - you are right. Is it possible to whiteout this small part
of the barlines?
I found out how to define a whiteout stencil, but it seems that it
is placed
Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM
Trevor Daniels schrieb:
Marc Hohl wrote Monday, January 18, 2010 8:13 PM
Marc Hohl schrieb:
Neil Puttock schrieb:
2010/1/8 Marc Hohl m...@hohlart.de:
Hmmm - you are right. Is it possible to whiteout this small
part
of the barlines?
I
Marc Hohl wrote Tuesday, January 19, 2010 10:09 AM
Trevor Daniels schrieb:
Marc Hohl wrote Tuesday, January 19, 2010 9:04 AM
Trevor Daniels schrieb:
Marc Hohl wrote Monday, January 18, 2010 8:13 PM
Marc Hohl schrieb:
Neil Puttock schrieb:
2010/1/8 Marc Hohl m...@hohlart.de:
Hmmm
Marc Hohl wrote Wednesday, January 20, 2010 9:54 AM
Trevor Daniels schrieb:
[...]
I would not worry about this. As Alexander has pointed out,
examples showing the staff lines extending through the sign
and not extending through the sign can be found. It is easy
for a user to move
Eric Knapp wrote Thursday, January 21, 2010 2:36 AM
My goal is to determine the fingering
number and the string number
Is there a way to determine the digit
and string-number directly by name? It looks like the
articulations
are a list. Would it be possible to loop through the list and
Hi Eric
I'm a relative newcomer to Lily development too,
so it's best to keep these questions and answers
on the -devel list. That way others can chip in
to correct anything I say that is wrong and suggest
alternative and probably better ways of achieving
what you want to do.
I've tried to
Mark Polesky wrote Saturday, January 23, 2010 6:45 AM
Carl Sorensen wrote:
My cycle is to
[edit source files]
make (if needed)
You lost me there. How will I know if `make' is needed?
If you modify any source files that have to be
compiled, essentially the c++ files and their
includes
Carl Sorensen wrote Sunday, January 24, 2010 1:49 PM
On 1/23/10 11:10 PM, Mark Polesky markpole...@yahoo.com wrote:
I wrote a little shell script to rebase all my local git
branches at once.
So does the script rebase all branches in a repository? I'm sure
I wouldn't
like that; I have some
Neil Puttock wrote Wednesday, January 27, 2010 5:38 PM
There's nothing in the documentation policy for \context block
formatting, but since you've amended some examples in the LM, I
thought I'd check what the preferred style should be to prevent
any
confusion.
I much prefer the context name
Graham Percival wrote Wednesday, January 27, 2010 6:43 PM
On Wed, Jan 27, 2010 at 06:12:14PM -, Trevor Daniels wrote:
Neil Puttock wrote Wednesday, January 27, 2010 5:38 PM
There's nothing in the documentation policy for \context block
formatting,
The patch is being written by James
Francisco Vila wrote Wednesday, February 03, 2010 9:25 AM
Currently, notation/world.itely mixes 'maqam' / 'maqams' and
'makam' /
'makamlar'. Is this correct for Arabic/Turkish respectively, or
should
it be unified?
Seems like maqam is Arabic and makam is Turkish.
See
David Kastrup wrote Monday, February 08, 2010 1:02 PM
Han-Wen Nienhuys hanw...@gmail.com writes:
I think this is nitpicking; we don't release just the binary
files
separately; people'd have to go through contortions to do what
you
think is suggested.
Well, _I_ understood the wording
Werner LEMBERG Wednesday, February 10, 2010 8:01 AM
In define-markup-commands.scm, there are references to things
like
wordwrap-internal-markup-list and
make-wordwrap-internal-markup-list. For example, in the function
define-builtin-markup-list-command, there is the application
Graham Percival wrote Friday, February 12, 2010 6:57 PM
I've tweaked the list of dirs to remove from
share/ghostscript/Resources. The resulting files are (on average)
5
megs smaller. linux-x86 works here for me.
Could we get a few tests for various OSes?
On Vista:
Yes - the .exe is
Graham
While answering a user question I noticed that
some examples in the LM which were earlier on
a single line now spread undesirably over two
lines in both html and pdf versions. You can
see several examples in 4.5.3.
I'm happy to fix these, but I'm not sure what
I should change. Can
Graham Percival wrote Tuesday, February 16, 2010 4:12 AM
On Tue, Feb 16, 2010 at 12:34 AM, Trevor Daniels
t.dani...@treda.co.uk wrote:
While answering a user question I noticed that
some examples in the LM which were earlier on
a single line now spread undesirably over two
lines in both
Trevor Daniels wrote Tuesday, February 16, 2010 9:59 AM
Graham Percival wrote Tuesday, February 16, 2010 4:12 AM
On Tue, Feb 16, 2010 at 12:34 AM, Trevor Daniels
t.dani...@treda.co.uk wrote:
While answering a user question I noticed that
some examples in the LM which were earlier
I've not been able to push to Savannah this
afternoon. I get:
ssh: connect to host 199.232.41.69 port 22: Bad file number
fatal: The remote end hung up unexpectedly
Same error with pull.
Is this a problem at the Savannah end or mine?
Trevor
Mark Polesky wrote Tuesday, February 16, 2010 6:19 PM
Trevor Daniels wrote:
I've not been able to push to Savannah this afternoon. I
get:
ssh: connect to host 199.232.41.69 port 22: Bad file
number fatal: The remote end hung up unexpectedly
Same error with pull.
Is this a problem
John, you wrote
Unless the docs output caused by this issue is unbearable even
during
the two days it may take me to fix it from now, please don't
commit this
so-called fix.
It's not an urgent problem, and I can't push a fix anyway at
the moment, so I'm happy to leave it to you. Thanks.
lgtm
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: lilypond-devel lilypond-devel@gnu.org
Sent: Saturday, February 27, 2010 10:27 PM
Subject: CG chapter 3, second draft
...and hopefully the final draft.
Carl Sorensen wrote Tuesday, February 16, 2010 8:09 PM
On 2/16/10 10:46 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
ssh: connect to host 199.232.41.69 port 22: Bad file number
fatal: The remote end hung up unexpectedly
I got this problem when I had a bad ssh key.
Well, with help
Graham Percival wrote Sunday, February 28, 2010 11:16 AM
On Sun, Feb 28, 2010 at 09:21:17AM -, Trevor Daniels wrote:
The long explanation, mainly for the record in case
anyone else encounters this, follows.
Fascinating! I had no idea that MTU settings could actually
*break* some
Francisco Vila wrote Monday, March 01, 2010 11:29 PM
2010/3/1 Mark Polesky markpole...@yahoo.com:
Graham Percival wrote:
It should be @rcontrib. We can't use @ref inside
included/
Then why don't the 8 remaining instances of @ref (in
compile.itexi) prevent the docs from compiling?
I am
Mark Polesky wrote Tuesday, March 02, 2010 1:18 AM
Francisco Vila wrote:
Compile stopped there, then I removed the @ref and compile
succeeded; I even added a warning following Graham. An
extra point is: nobody told she could compile the docs
without the remove.
I just successfully
Graham Percival wrote Tuesday, March 02, 2010 9:30 AM
On Tue, Mar 02, 2010 at 09:25:55AM -, Trevor Daniels wrote:
Following Francisco's correction my local check
on reference validity now says
Warning: xref should be internal around line 231 in
included/compile.itexi
Warning: xref
Mark Polesky wrote Sunday, February 28, 2010 4:23 PM
Trevor Daniels wrote:
In short, the real source of the problem is out of my
control, but a work-around was to change the MTU setting
in my domestic router from 1458 to 1500.
The long explanation, mainly for the record in case anyone
else
David Kastrup wrote Tuesday, March 16, 2010 5:02 PM
Mark Polesky markpole...@yahoo.com writes:
Carl Sorensen wrote:
I'm OK with that, but I still have the concern of
documenting it. What do we need to do to make sure that
the documentation works properly?
I don't think it's worth it.
Arno Waschk wrote Sunday, March 21, 2010 2:59 PM
But is there really a difference - from user point of view -
between no bracket and an pretty much invisible one?
And is there a way to force the pretty much invisible bracket to
be visible without actual change to the score content - in
Arno Waschk wrote Sunday, March 21, 2010 3:59 PM
But should not lilypond define a default minimum-length that makes
it at least visible. Or if it does (what i would assume), why
does it not work?
Well, the bracket is small but perfectly visible in
2.13.14 (the version I happened to use to
Graham Percival wrote Tuesday, April 06, 2010 8:39 AM
On Tue, Apr 6, 2010 at 8:21 AM, Mats Bengtsson
mats.bengts...@ee.kth.se wrote:
Fine! My only concern is how easy it will be to find the Essay if
it's only
available under a section entitled Academia.
That _is_ a definite concern; I'm
Mark Polesky wrote Monday, April 26, 2010 7:33 AM
Both
LM 1.2.1 Simple notation and
NR 1.2.1 Writing rhythms
include these two sentences:
If the duration is omitted, it is set to the previously
entered duration. The default for the first note is a
quarter note.
I'd like to reword both
LGTM
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: Carl Sorensen c_soren...@byu.edu; Graham Percival
gra...@percival-music.ca
Cc: lilypond-devel lilypond-devel@gnu.org
Sent: Friday, April 30, 2010 5:46 PM
Subject: Re: PATCH: Doc: Clarify \relative inside
Hi Mark
The only rule I disagree with is
* Use `\clef treble' instead of `\clef treble', etc.
The quotes are required for G_8 so should be present
on all for consistency and to avoid confusion.
Also need to specify default indenting is 2 spaces.
Trevor
- Original Message -
From:
Carl Sorensen wrote Sunday, May 02, 2010 5:49 PM
On 5/2/10 4:45 AM, Mark Polesky markpole...@yahoo.com wrote:
* Use bar-checks (`|') only when barring is unclear.
I think we should always use bar-checks when the piece is more
than one bar
long. That's a good habit to get into; we ought
Mark Polesky wrote Tuesday, May 04, 2010 5:34 AM
Trevor Daniels wrote:
Carl Sorensen wrote:
I think we should always use bar-checks when the piece
is more than one bar long. That's a good habit to get
into; we ought to start it right from the first.
I would agree with this. In fact I put
James Lowe wrote Tuesday, May 04, 2010 11:19 AM
Trevor Daniels wrote:
Mark Polesky wrote Tuesday, May 04, 2010 5:34 AM
Trevor Daniels wrote:
Carl Sorensen wrote:
I think we should always use bar-checks when the piece
is more than one bar long. That's a good habit to get
into; we ought
I'd be happy with this too.
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: Carl Sorensen c_soren...@byu.edu; lilypond-devel
lilypond-devel@gnu.org; Trevor Daniels t.dani...@treda.co.uk
Cc: Graham Percival gra...@percival-music.ca; James Lowe
james.l
I guess not. Graham insisted on removing my two
bars of Over the Rainbow.
Trevor
- Original Message -
From: Mark Polesky markpole...@yahoo.com
To: lilypond-devel lilypond-devel@gnu.org
Sent: Wednesday, May 05, 2010 6:01 AM
Subject: copyright question
Are we allowed to quote Star
Graham Percival wrote Wednesday, May 05, 2010 3:51 PM
On Tue, May 04, 2010 at 10:19:52AM -0700, Mark Polesky wrote:
Trevor Daniels wrote:
A brief description of bar checks in 1.2.2 Working on
input files would be good. I think bar checks are at
least as important as a \version statement
Mark Polesky wrote Wednesday, May 05, 2010 7:16 AM
In the HTML docs, the context-example.eps image doesn't
get displayed in LM 3.3.1 Contexts explained, though it
does show up in the PDF.
http://kainhofer.com/~lilypond/Documentation/learning-big-page.html#Contexts-explained
Also, this
Mark Polesky wrote Saturday, May 08, 2010 3:01 AM
*** This refers to LM 3.2.3 Voices and vocals ***
Trevor Daniels wrote:
I put this in after several questions on -user about how
this should be done, but I wasn't very happy with it. If
you can come up with a better way of coding a solo
Mark Polesky wrote wrote Sunday, May 09, 2010 2:50 AM
Trevor Daniels wrote:
I suggest you dump this as a template in A.4 for now.
Let me make sure I'm doing this right.
1) commit the attached patch
2) run scripts/auxiliar/makelsr.py
3) commit that result as Doc: Update LSR.
4) make doc
Graham Percival wrote Monday, May 24, 2010 12:00 AM
On Fri, May 21, 2010 at 09:54:38AM -0700, Mark Polesky wrote:
Graham Percival wrote:
It must be exactly the same as the @node name, which
cannot have things like @code in it.
Yes and no. It must have exactly the same as the @node
name,
David Kastrup wrote Wednesday, June 02, 2010 7:37 AM
I was talking about programming midi stuff. That there is enough
material in the notation manual to get any output at all, and also
to
reassign midi instruments, I'll readily grant. But that's the
minimum
required to actually get midi
Carl
At first glance this looks like a major improvement!
I'm tied up today, but I'll give it a whirl within a
day or two.
Trevor
- Original Message -
From: carl.d.soren...@gmail.com
To: carl.d.soren...@gmail.com
Cc: re...@codereview.appspotmail.com; lilypond-devel@gnu.org
Sent:
Neil Puttock wrote 14 June 2010
On 14 June 2010 20:04, Carl Sorensen c_soren...@byu.edu wrote:
bin-clean should just clean up the binaries.
Yup, it saves having to rebuild fonts, so in this case shaves off
a
significant proportion of the total build time.
I saw this just after doing
Carl Sorensen wrote Tuesday, June 15, 2010 12:01 AM
On 6/14/10 4:00 PM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Neil Puttock wrote 14 June 2010
On 14 June 2010 20:04, Carl Sorensen c_soren...@byu.edu wrote:
bin-clean should just clean up the binaries.
Yup, it saves having
Carl.D.Sorensen wrote Tuesday, June 15, 2010 11:27 PM
Description:
Revised autobeam settings patch -- cleaned up debug comments
in code and eliminated the irrelevant changes in
Documentation/snippets just due to running makelsr.py
Please review this at
Carl, you wrote Monday, June 21, 2010 10:10 PM
Sorry for the delay - I've been away and it took
a while to catch up with my mail.
On 6/16/10 3:18 AM, Trevor Daniels t.dani...@treda.co.uk
wrote:
Carl.D.Sorensen wrote Tuesday, June 15, 2010 11:27 PM
Description:
Revised autobeam settings
Carl Sorensen wrote Friday, July 02, 2010 3:22 PM
Sounds a promising approach, although some of the details
remain unclear from your lucid but high-level description.
I'm trying to redo auto-beaming so that it matches
better with what I read in the literature. When I
get it done, I hope to
Carl Sorensen wrote Saturday, July 03, 2010 1:06 AM
On 7/2/10 5:19 PM, Trevor Daniels t.dani...@treda.co.uk wrote:
Carl Sorensen wrote Friday, July 02, 2010 3:22 PM
I've got mixed feelings about the following property:
3) beatCombinations: an alist with a key of beam type,
and a value
Carl Sorensen wrote Saturday, July 03, 2010 11:36 AM
On 7/3/10 3:11 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
As we discussed earlier, this rhythm, f4 r8 f f f, could be
handled by implementing a 'start' rule as well as an 'end' rule,
to be sure beams could be started only on beats
Michael m.mora...@fanofcomputers.com wrote Sunday, July 04,
2010 5:58 AM
Edited two entries.
Pushed - many thanks.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Graham, you wrote Saturday, July 03, 2010 10:28 PM
I'm leaving for LSM next Wednesday, and after that I'm going to
Vancouver for two weeks. I won't have access to a machine capable
of compiling lilypond in less than 4 hours, so I'd like somebody
else to handle testing+pushing doc patches,
I've just upgraded from 2.13.14 to 2.13.26 (mingw on Vista)
in preparation for checking doc patches while Graham is away
and I find that has introduced an error when I run lilypond-book
on the doc files. The same error occurs on the two files I've
tried and is, for example,
error: failed files:
Hi Carl
Download and applied to current git, but make fails:
make[1]: *** No rule to make target `include/beam-settings.hh',
needed by `out/beaming-pattern.o'. Stop.
make[1]: Leaving directory `/media/lilypond-git/lily'
make: *** [all] Error 2
Does this need to be applied over your previous
Carl, you wrote Monday, July 05, 2010 1:26 PM
I'm trying to build the documentation to make sure it works with
my new
autobeam code.
When I do make doc-clean make doc, I get the following error:
[snip error messages]
I get the same error. However, I did build the docs
successfully on
Michael m.mora...@fanofcomputers.com wrote Tuesday, July 06,
2010 3:07 AM
Added German name from alla breve and create consistency for
cut
time.
Thanks! Pushed to git.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Werner LEMBERG wrote Sunday, July 11, 2010 6:38 PM
The organ template given in `fundamental.itely' lacks an
important
property, namely the limited stretchability of the pedal staff.
Without this, the distance of the pedal staff w.r.t. the other
two
staves can become far too big.
Here's a
While checking the recent changes I made to the Learning
Manual I noticed the following fault in rendering texinfo
to html. I don't remember it being mentioned before, and
I can't see a reference to it in the Contributors Guide.
When a cross-reference in a .itely file is split across
two lines,
Thanks Michael. Pushed to git.
Trevor
- Original Message -
From: Michael m.mora...@fanofcomputers.com
To: LilyPond-devel lilypond-devel@gnu.org
Sent: Friday, July 16, 2010 7:57 PM
Subject: (no subject)
Edit to the glossary.
--
Michael
Carl,
Just to congratulate you on finally succeeding with this.
This will be a great improvement in the next release.
Trevor
- Original Message -
From: Carl Sorensen c_soren...@byu.edu
To: Lily devel lilypond-devel@gnu.org
Sent: Sunday, July 18, 2010 5:39 AM
Subject: Autobeaming code
Carl Sorensen wrote Thursday, July 29, 2010 10:24 PM
On 7/29/10 12:07 PM, James james.l...@datacore.com wrote:
On 29/07/2010 18:19, Mike Solomon wrote:
Hey Bernardo,
The woodwind fingering is chugging along. All of the code
is in the
current development version of lilypond, along
Dan Wilckens wrote Thursday, July 29, 2010 2:47 PM
Hi James,
I mainly thought the tempo command was too hard to find in the
documentation--too illogically placed for me to track down easily
navigating the notation reference headings (just tried it in the
2.13 doc's, had similar problems
Ralf Wildenhues wrote Saturday, July 31, 2010 4:25 PM
* James Lowe wrote on Sat, Jul 31, 2010 at 02:19:41PM CEST:
- Do you prefer 'e.g.' over 'eg.' and 'i.e.' over 'ie.', and
what
about 'with respect to' over 'wrt.' or 'w.r.t.' or 'wrt'?
FWIW, I
prefer the first alternative in each
Carl Sorensen wrote Sunday, August 01, 2010 1:54 AM
On 7/31/10 5:51 PM, Wols Lists antli...@youngman.org.uk wrote:
Do you put a comma after that is? Either way, it feels right.
I'd be
inclined to say don't stick a comma after a full stop, and yes
I know
that the dot isn't really a full stop
Graham Percival wrote Tuesday, August 03, 2010 3:31 AM
As you might recall, I gave a talk at RMLL 2010
about sustainable development in F/OSS.
Nice talk. It prompted me to think about my own involvement
with LilyPond. I volunteered for doc development due to
the guilt pressure at the start
Graham Percival wrote Wednesday, August 04, 2010 9:41 AM
On Wed, Aug 04, 2010 at 09:10:25AM +0100, Trevor Daniels wrote:
1) There is no architectural overview and no program logic manual
to
guide new developers through the early stages.
This has the advantage that
No; there's
David Kastrup wrote Wednesday, August 04, 2010 11:27 AM
Trevor Daniels t.dani...@treda.co.uk writes:
1) There is no architectural overview and no program logic manual
to
guide new developers through the early stages.
This has the advantage that only experienced and expert
coders able
Graham
While looking into the @help in download.itexi
(the font size used for smallexample) I
noticed that the css file currently being used to
build the web is css/lilypond-web.css. Is this
correct? The css title is Patrick McCarty's design
and there is a beautifully-laid out css file
Graham
I don't understand what is meant by this TODO in
/download.itexi:
@item
@c TODO: duplicate to avoid underlined refs in HTML? icky.
@ref{Unix, @sourceimage{logo-linux,,,}
@sourceimage{logo-freebsd,,,}}
@ref{Unix, Unix (Linux and FreeBSD)}
I presume the comment is yours.
I don't myself
Hi Graham
I've just pushed a fix for another TODO in web/manuals.itexi
@c TODO: do we want these links to be in larger text / bold ?
CSS.
The fix makes the links bold, and they certainly look better, IMO,
but the fix is very messy due to the the way @spanClass has been
implemented - it
Graham Percival wrote Sunday, August 08, 2010 3:44 AM
On Sat, Aug 7, 2010 at 10:59 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
The images don't look like links - nothing happens with hover,
for instance.
Really? I get a standard link hover mouse cursor with firefox
3.6.8
Graham Percival wrote Saturday, August 07, 2010 2:29 AM
On Fri, Aug 06, 2010 at 05:31:31PM +0100, Trevor Daniels wrote:
I don't understand what is meant by this TODO in
/download.itexi:
@item
@c TODO: duplicate to avoid underlined refs in HTML? icky.
@ref{Unix, @sourceimage{logo-linux
Hi Graham
When I build the website I find the footer section
on all the main pages is not right, and differs from the
same pages on http://lilypond.org/website/manuals.html,
even with the same git. The ordering of various tags
when I look at the html source is wrong, resulting in
the wrong list
Thanks Eluze. Edited in and pushed to git.
Trevor
- Original Message -
From: -Eluze elu...@gmail.com
To: lilypond-devel@gnu.org
Sent: Monday, August 09, 2010 5:43 PM
Subject: doc-addition for -I / --include
in AU, chapter 1.2 Command-line usage, Invoking Lilypond
Graham Percival wrote Monday, August 09, 2010 9:02 AM
(actually, if you follow the scripts in CG 5.2, then you don't
even need to bother cleaning out scripts/ or doing a make )
Thanks. I think I see now why I have a problem. My git repo
is not in ~/lilypond/lilypond-git because I ran out
401 - 500 of 1527 matches
Mail list logo
