On Thu, Jul 29, 2010 at 12:59:46AM +0800, Ambrose Bonnaire-Sergeant wrote:
In scm/define-music-types.scm there is a comment:
;; TODO: should link back into the user manual.
I'm assuming it's referring to the elements of music-description.
Where are these located?
I have no
I'm not top-posting.
Hello LilyPonders! (or is it ponderers? ;-)
I was just introduced to your nice piece of software art, so thanks!
I don't like typos, so find attached a patch (against git master) to fix
them in the English manual. Tried to omit all controversial bits, but
just in case,
I don't like typos, so find attached a patch (against git master) to
fix them in the English manual. Tried to omit all controversial
bits, but just in case, I'd be happy to redo.
Applied, thanks!
If you are interested in more: There are typos in the English part
of translated manuals; and
* Werner LEMBERG wrote on Sat, Jul 31, 2010 at 11:34:25AM CEST:
I don't like typos, so find attached a patch (against git master) to
fix them in the English manual.
Applied, thanks!
Hi Werner, and wow, quick feedback!
If you are interested in more: There are typos in the English part
On 2010/07/23 21:49:50, Neil Puttock wrote:
Hi Joe,
I haven't been able to replicate the problems I had running `make
check', even
with the hash table default set to 1000; I guess that means LGTM. :)
Cheers,
Neil
http://codereview.appspot.com/1817045/diff/10001/11001
File
Hello,
-Original Message-
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org on behalf of
Werner LEMBERG
Sent: Sat 31/07/2010 12:52
To: ralf.wildenh...@gmx.de
Cc: lilypond-devel@gnu.org
Subject: Re: Typos in English manual
- Do you prefer 'e.g.' over 'eg.' and 'i.e.' over
Hello LilyPonders! (or is it ponderers? ;-)
I was just introduced to your nice piece of software art, so thanks!
I don't like typos, so find attached a patch (against git master) to fix
them in the English manual. Tried to omit all controversial bits, but
just in case, I'd be happy to redo the
Hello,
Commits fc1946c290e5f253769a306efff1b0224178aaa5 and
9e1b534c81e101c449acfa176f923be57cbcaea5 have added a patch in to the Learning
Manual.
The NR still needs to be done.
Tracker opened http://code.google.com/p/lilypond/issues/detail?id=1197 (thanks
Phil)
James
-Original
Actually I am not sure that 'i.e.,' is necessary. 'i.e,' is not
correct, so 'i.e.' without a comma is fine as far as I know.
Well, `i.e.' is a shorthand for the Latin `id est' which translates to
`that is', and for the latter, you always need a comma after the `is'
if you continue with a
* 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 case, but can adjust as
requested.
Always the first
On 2010/07/31 10:59:28, arnonokia6230 wrote:
Hm, i am seeing huge memory problems here. What is the trick finally?
I don't know; following my initial `make check' run which swallowed all
the memory, I haven't had any problems, even with large files.
Can you post a test file which still shows
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
On 31 July 2010 14:15, Werner LEMBERG w...@gnu.org wrote:
Well, `i.e.' is a shorthand for the Latin `id est' which translates to
`that is', and for the latter, you always need a comma after the `is'
if you continue with a sentence, right? So I think `i.e.' needs a
comma.
I had a vague
On 7/31/2010 10:31 AM, Neil Puttock wrote:
I had a vague recollection that this was part of the doc policy, and
it's certainly listed here:
http://lists.gnu.org/archive/html/lilypond-user/2007-09/msg00486.html
* Do not use abbreviations (don't, won't, etc.). If you do, use a
comma after
On 31/07/10 22:50, Michael S. Morales wrote:
On 7/31/2010 10:31 AM, Neil Puttock wrote:
I had a vague recollection that this was part of the doc policy, and
it's certainly listed here:
http://lists.gnu.org/archive/html/lilypond-user/2007-09/msg00486.html
* Do not use abbreviations (don't,
Hi Patrick, Neil and all,
On 29/07/10 20:24, n.putt...@gmail.com wrote:
On 2010/07/29 00:55:35, Patrick McCarty wrote:
With your patchset, I am getting a compile failure with the regression
test
`profile-property-access.ly':
Same here.
How did you guys track it down to this module? I
On 7/31/10 5:51 PM, Wols Lists antli...@youngman.org.uk wrote:
On 31/07/10 22:50, Michael S. Morales wrote:
On 7/31/2010 10:31 AM, Neil Puttock wrote:
I had a vague recollection that this was part of the doc policy, and
it's certainly listed here:
17 matches
Mail list logo
