Re: Substitute for s1*0

Le 6 mai 2012 à 23:54, Trevor Daniels a écrit : >> I'm ok with using <> as a quick hack for things like convert-ly >> rules, so I'm not arguing against David's patch. But I wouldn't >> want to see <> becoming part of our basic vocabulary. I still >> think that a "n" or "z" or "\null" would be m

Re: Substitute for s1*0

Trevor Daniels treda.co.uk> writes: > My point really is that <> exists now, so there ought to > be a short note in the section where chords are introduced > to say that an empty chord takes no time, whatever the > current duration happens to be. I agree with Trevor. And with David in liking

Re: Substitute for s1*0

Warning! This is an off-topic e-mail. > I think it leads to the "perlization" of lilypond, where we end up > looking like a ridiculous language like Haskell. What exactly is `ridiculous' in Haskell? Personally, I find this language quite fascinating. Werner _

PATCH: Countdown to 20120508

For 20:00 MDT Tuesday May 8 Enhancement: Issue 2513 : Patch: Build: add -fno-tree-vrp to CXXFLAGS for gcc 4.7.0 - R6191048 (s/b reviewed, pushed before 2514) Issue 2514

Re: Intregrating lilypond.pot update to 'make release'

Hi Jean-Charles, I spotted a typo in your README text, On 06/05/12 17:19, Jean-Charles Malahieude wrote: > +2) updating lilypond.pot: run 'make po-replace' at toplevel, > commit +lilypond.pot to Git, roll a tarball with 'make dist', > upload it +somewhere on the web (or wait for the release), and s

Re: Substitute for s1*0

Graham Percival wrote Sunday, May 06, 2012 10:24 PM I'm still not happy with an empty chord, especially in the Learning Manual. I think it leads to the "perlization" of lilypond, where we end up looking like a ridiculous language like Haskell. My point really is that <> exists now, so there

Re: Substitute for s1*0

Graham Percival writes: > On Sun, May 06, 2012 at 10:17:05PM +0100, Trevor Daniels wrote: >> >> I've no objection to the docs being changed to use an empty chord >> but its semantics will need to be introduced somewhere. The best place >> is probably the LM, in 2.2.4 Combining notes into chords

Re: Substitute for s1*0

On Sun, May 06, 2012 at 10:17:05PM +0100, Trevor Daniels wrote: > > I've no objection to the docs being changed to use an empty chord > but its semantics will need to be introduced somewhere. The best place > is probably the LM, in 2.2.4 Combining notes into chords. I'm still not happy with an e

Re: Substitute for s1*0

David Kastrup wrote Sunday, May 06, 2012 4:44 PM "Trevor Daniels" writes: Actually, I don't think s1*0 appears in the docs. Documentation/notation/vocal.itely: s1*0^\markup { \right-align { \tiny "Flute" } } Documentation/notation/vocal.itely: s1*0_\markup { \right-align { \tiny "Clar."

Re: translators: fix your "open source" mistranslations

On Sun, May 06, 2012 at 09:36:38PM +0200, Francisco Vila wrote: > 2012/5/6 Graham Percival : > > So I guess those shouldn't be changed, and if that's it in the > > French translation then I guess you're fine. > > We have in English > > http://lilypond.org/freedom.html > “Gift culture”: the Free S

Re: translators: fix your "open source" mistranslations

2012/5/6 Graham Percival : > On Sun, May 06, 2012 at 07:02:20PM +0200, Jean-Charles Malahieude wrote: >> >> Just two instances in GSoC node that I'm not sure they should be >> transformed: >> >> fr (translation)]$ git grep -n 'open source' >> web/community.itexi:930:étudiants pour écrire du code au

Re: [translations] Re: how to remove a file

2012/5/6 Federico Bruni : > I'm putting -devel in CC. > Sorry for pushing, I'm in a hurry: I'd like to send the patches within > tonight. > > Il 06/05/2012 15:53, Federico Bruni ha scritto: > >> Hi, >> >> I have to remove the .texidoc file of a snippet which has been removed: >> >> diff --git >> a/

Re: translators: fix your "open source" mistranslations

On Sun, May 06, 2012 at 07:02:20PM +0200, Jean-Charles Malahieude wrote: > > Just two instances in GSoC node that I'm not sure they should be > transformed: > > fr (translation)]$ git grep -n 'open source' > web/community.itexi:930:étudiants pour écrire du code au bénéfice de > projets @emph{open

Re: staff_radius fixes (issue 6202048)

this patch makes staff_radius work in cases when line-positions is overridden. so long staff_radius assumed overriding at most line-count. sorry, I forgot to mention that - staff-radius behaved incorrectly also when staff-space is overridden - there's one slight difference in the regression te

Re: translators: fix your "open source" mistranslations

Le 06/05/2012 18:31, Graham Percival disait : I have a bit more information about the terminology problems. Although the English website is relatively ok (I remember specifically thinking about "free software vs. open source" while writing it -- but Janek should still fix the little bits I missed

Re: Intregrating lilypond.pot update to 'make release'

On Sun, May 06, 2012 at 06:19:42PM +0200, Jean-Charles Malahieude wrote: > What you'll find in the enclosed patch is an attempt to adapt > 'make po-replace' in order to have an automatically well-formed .pot > included in 'make dist'. Please upload patches to rietveld with git-cl, as specified her

translators: fix your "open source" mistranslations

I have a bit more information about the terminology problems. Although the English website is relatively ok (I remember specifically thinking about "free software vs. open source" while writing it -- but Janek should still fix the little bits I missed), some translations are wrong. For example, O

Re: how to remove a file

On Sun, May 06, 2012 at 05:32:08PM +0200, Federico Bruni wrote: > I made a try: > > $ git rm > Documentation/it/texidocs/piano-template-with-centered-dynamics.texidoc > error: > 'Documentation/it/texidocs/piano-template-with-centered-dynamics.texidoc' > has local modifications > (use --cached to

Intregrating lilypond.pot update to 'make release'

Hi Jan and Graham, Since I got a problem the last time I notified the Free Translation Project of a new lilypond.pot, I'd like to have it updated during the releasing process. What you'll find in the enclosed patch is an attempt to adapt 'make po-replace' in order to have an automatically wel

Re: Substitute for s1*0

Janek Warchoł writes: > On Sun, May 6, 2012 at 6:56 AM, Werner LEMBERG wrote: In fact, isn't <> generally prettier than s1*0?  Should we be using it in code and documentation rather than s1*0? >>> >>> What a great idea!  No notes generated; the duration doesn't >>> change. >> >> Indeed

Re: Substitute for s1*0

"Trevor Daniels" writes: > David Kastrup wrote Sunday, May 06, 2012 9:34 AM > >> Quick: tell me what you would expect without too much thinking (imagine >> you are a naive user) from the following: >> >> \new Staff << >> \relative c'' { c4 d e f s1*0-\markup Oops c d e f g1 } \\ >> \relative c'

Re: Substitute for s1*0

"Trevor Daniels" writes: > David Kastrup wrote Sunday, May 06, 2012 9:34 AM > >> Quick: tell me what you would expect without too much thinking (imagine >> you are a naive user) from the following: >> >> \new Staff << >> \relative c'' { c4 d e f s1*0-\markup Oops c d e f g1 } \\ >> \relative c'

Re: Substitute for s1*0

David Kastrup wrote Sunday, May 06, 2012 9:34 AM Quick: tell me what you would expect without too much thinking (imagine you are a naive user) from the following: \new Staff << \relative c'' { c4 d e f s1*0-\markup Oops c d e f g1 } \\ \relative c' { c4 d e f <>-\markup Wow c d e f g1 } Tha

Re: how to remove a file

I'm putting -devel in CC. Sorry for pushing, I'm in a hurry: I'd like to send the patches within tonight. Il 06/05/2012 15:53, Federico Bruni ha scritto: Hi, I have to remove the .texidoc file of a snippet which has been removed: diff --git a/Documentation/snippets/piano-template-with-center

Re: Your Gnu package lilypond

On Sun, May 06, 2012 at 05:15:59AM -0400, John Darrington wrote: > Thank you for your very comprehensive reply, which inspired me to > look at the lilypond website. It is indeed very elaborate and > certainly gives a very professional impression. (There are however > a few terminology issues whic

Re: Substitute for s1*0

On Sun, May 6, 2012 at 6:56 AM, Werner LEMBERG wrote: >>> In fact, isn't <> generally prettier than s1*0?  Should we be using >>> it in code and documentation rather than s1*0? >> >> What a great idea!  No notes generated; the duration doesn't >> change. > > Indeed!  I wasn't aware that <> is vali

Re: Substitute for s1*0

Pavel Roskin writes: > Quoting Graham Percival : > >> On Sun, May 06, 2012 at 08:58:11AM +0100, Trevor Daniels wrote: >>> >>> David Kastrup wrote Sunday, May 06, 2012 2:57 AM >>> >>> >In fact, isn't <> generally prettier than s1*0? Should we be using it >>> >in code and documentation rather than

Re: CG guide to building GUB (issue 6199045)

On 2012/05/06 13:06:09, PhilEHolmes wrote: The filesystem I created was 64 Gigs, and it shows 36.8 free - so 30 gigs is the bare minimum. My GUB directory is about 12 Gigs, and my total file size is around 17 Gigs, ah, that makes sense. I was only looking at the directory, but of course t

Re: CG guide to building GUB (issue 6199045)

On 2012/05/06 11:27:47, Graham Percival wrote: great start; a few notes for you or James to investigate. http://codereview.appspot.com/6199045/diff/1/Documentation/contributor/build-notes.itexi File Documentation/contributor/build-notes.itexi (right): http://codereview.appspot.com/6199045/

Re: Substitute for s1*0

Quoting Graham Percival : On Sun, May 06, 2012 at 08:58:11AM +0100, Trevor Daniels wrote: David Kastrup wrote Sunday, May 06, 2012 2:57 AM >In fact, isn't <> generally prettier than s1*0? Should we be using it >in code and documentation rather than s1*0? Definitely prettier, but maybe not s

Re: Substitute for s1*0

Francisco Vila writes: > Is s*0 valid? No. *0 is part of the duration, not some magical repeat count. > It would not change default duration of next note. It should, if it were allowed. -- David Kastrup ___ lilypond-devel mailing list lilypond-de

Re: CG guide to building GUB (issue 6199045)

great start; a few notes for you or James to investigate. http://codereview.appspot.com/6199045/diff/1/Documentation/contributor/build-notes.itexi File Documentation/contributor/build-notes.itexi (right): http://codereview.appspot.com/6199045/diff/1/Documentation/contributor/build-notes.itexi#n

CG guide to building GUB (issue 6199045)

Reviewers: Graham Percival, J_lowe, Message: Please review Description: Some notes on how to set up a GUB build environment. Please review this at http://codereview.appspot.com/6199045/ Affected files: M Documentation/contributor/build-notes.itexi Index: Documentation/contributor/build-not

Re: Substitute for s1*0

Is s*0 valid? It would not change default duration of next note. Cannot test right now, sorry. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Substitute for s1*0

David Kastrup writes: > Graham Percival writes: > >> On Sun, May 06, 2012 at 08:58:11AM +0100, Trevor Daniels wrote: >>> >>> David Kastrup wrote Sunday, May 06, 2012 2:57 AM >>> >>> >In fact, isn't <> generally prettier than s1*0? Should we be using it >>> >in code and documentation rather th

Re: Substitute for s1*0

Graham Percival writes: > On Sun, May 06, 2012 at 08:58:11AM +0100, Trevor Daniels wrote: >> >> David Kastrup wrote Sunday, May 06, 2012 2:57 AM >> >> >In fact, isn't <> generally prettier than s1*0? Should we be using it >> >in code and documentation rather than s1*0? >> >> Definitely pretti

Re: Substitute for s1*0

"Trevor Daniels" writes: > David Kastrup wrote Sunday, May 06, 2012 2:57 AM > >> In fact, isn't <> generally prettier than s1*0? Should we be using it >> in code and documentation rather than s1*0? > > Definitely prettier, but maybe not so transparent as s1*0. I disagree. Quick: tell me what y

Re: Substitute for s1*0

On Sun, May 06, 2012 at 08:58:11AM +0100, Trevor Daniels wrote: > > David Kastrup wrote Sunday, May 06, 2012 2:57 AM > > >In fact, isn't <> generally prettier than s1*0? Should we be using it > >in code and documentation rather than s1*0? > > Definitely prettier, but maybe not so transparent as

Re: Substitute for s1*0

David Kastrup wrote Sunday, May 06, 2012 2:57 AM In fact, isn't <> generally prettier than s1*0? Should we be using it in code and documentation rather than s1*0? Definitely prettier, but maybe not so transparent as s1*0. It is not intuitively obvious that an empty chord takes no time and do

Re: Lilypond miscompiled on Fedora 17

Pavel Roskin writes: > Quoting David Kastrup : > >> We can probably use yes:400600[0-2]) here: 4.6.3 is supposed to contain >> the fix. > > Thank you for opening a separate ticket for it (2514) and reviewing my > ticket (2513)! Well, it means that my ticket goes through earlier, you will have to

Re: Substitute for s1*0

> There is a drawback, though. q is changed. Now q is implemented as > <> but with the current duration on it. Which would mean that the > total moment of > > { c4 <> q } > > would likely change when q gets expanded. While _is_ considered > for q for consistency's sake, perhaps <> should be