Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 30.09.2012 04:11, schrieb k-ohara5...@oco.net: Now looking at the log files, I do get "undead" errors for our regression test 'bar-line-define-bar-glyph.ly' but not from any other files that I tried. (I don't know why the scripts from `make check` did not flag it.) Keith, thanks for your work

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 30.09.2012 10:01, schrieb d...@gnu.org: http://codereview.appspot.com/6498052/diff/32001/scm/bar-line.scm File scm/bar-line.scm (right): http://codereview.appspot.com/6498052/diff/32001/scm/bar-line.scm#newcode225 scm/bar-line.scm:225: (define-public bar-glyph-alist '()) This interface de

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 30.09.2012 10:01, schrieb d...@gnu.org: http://codereview.appspot.com/6498052/diff/32001/scm/bar-line.scm File scm/bar-line.scm (right): http://codereview.appspot.com/6498052/diff/32001/scm/bar-line.scm#newcode225 scm/bar-line.scm:225: (define-public bar-glyph-alist '()) This interface de

verify regression tests

Hello list, I got strange results with the regression tests, and studying the CG more carefully, I spotted some differences: http://lilypond.org/doc/v2.17/Documentation/contributor/regtest-comparison says that you should do make test-baseline && make check [changed the code; if needed 'make']

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 30.09.2012 11:02, schrieb d...@gnu.org: [...] First, the define-public is asking for trouble. You are exposing an internal Scheme data structure to users and make it overwritable by the user. If the user follows this invitation, the effects will bleed over from session to session. Never do tha

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 30.09.2012 22:03, schrieb d...@gnu.org: On 2012/09/30 19:44:49, marc wrote: Am 30.09.2012 11:02, schrieb d...@gnu.org: > [...] > First, the define-public is asking for trouble. You are exposing an > internal Scheme data structure to users and make it overwritable by the > user. If the user

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 01.10.2012 11:00, schrieb d...@gnu.org: On 2012/10/01 08:46:09, marc wrote: Am 30.09.2012 22:03, schrieb d...@gnu.org: > On 2012/09/30 19:44:49, marc wrote: >> Am 30.09.2012 11:02, schrieb d...@gnu.org: >> > [...] >> > First, the define-public is asking for trouble. You are exposing an >> >

Re: Various clean-ups in stems and beams. (issue 6584045)

Am 02.10.2012 16:56, schrieb m...@mikesolomon.org: On 2 oct. 2012, at 16:42, aleksandr.andr...@gmail.com wrote: What I mean is that if something like { \override NoteHead #'style = #'kievan c'8 } produces a quarter note in the output, the user is likely to be thoroughly confused. Is this bec

Re: verify regression tests

Am 02.10.2012 23:24, schrieb Janek Warchoł: Hi Marc, On Sun, Sep 30, 2012 at 9:14 PM, Marc Hohl wrote: I got strange results with the regression tests, and studying the CG more carefully, I spotted some differences: http://lilypond.org/doc/v2.17/Documentation/contributor/regtest-comparison

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 06.10.2012 11:23, schrieb Janek Warchoł: On Fri, Oct 5, 2012 at 9:42 PM, Thomas Morley wrote: 2012/10/5 : It just occured to me: is there any way to specify different span bar lines (at the end of the line and at the beginning of the line)? Marc and me, we discussed this some time ago and

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 30.09.2012 22:03, schrieb d...@gnu.org: On 2012/09/30 19:44:49, marc wrote: Am 30.09.2012 11:02, schrieb d...@gnu.org: > [...] > First, the define-public is asking for trouble. You are exposing an > internal Scheme data structure to users and make it overwritable by the > user. If the user

Re: "unofficial GOP proposal" organization of GLISS discussions

Am 05.10.2012 18:34, schrieb Janek Warchoł: Hi all, i find it hard to keep up with our GLISS discussions. I've also heard that the amount of technical details, digressions and "multithreadedness" stops some people from participating, as they don't have enough time to read long conversations car

Re: User-poll about lily-syntax: results - [Was: [GLISS] basics]

Am 06.10.2012 22:27, schrieb Thomas Morley: Hi, attached are the alphabetic sorted complains/suggestions about LilyPond-syntax from german users. Hi Harm, thanks for your work – looks like you spent quite a lot of time collecting *and* presenting these issues! It looks like some issues coul

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 05.10.2012 21:42, schrieb Thomas Morley: 2012/10/5 : Marc wrote: (define-bar-line ...) or \defineBarLine allows for new definitions. These functions have four arguments, namely the bar line itself, the bar line used at the end of line, the bar line used at the begin of a new line and the sp

Re: Still alive

Am 09.10.2012 10:19, schrieb m...@mikesolomon.org: Hey list, Just a quick ping to let you know that I'm not dead - I've been swamped w/ work recently and just got engaged so I'm planning out a wedding (w00t!). Hey Mike, congratulations! All the best for both of you! Marc & Bettina I'll be

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 06.10.2012 11:23, schrieb Janek Warchoł: On Fri, Oct 5, 2012 at 9:42 PM, Thomas Morley wrote: 2012/10/5 : It just occured to me: is there any way to specify different span bar lines (at the end of the line and at the beginning of the line)? Marc and me, we discussed this some time ago and

Re: [GLISS] turning strings to symbols

Am 12.10.2012 16:48, schrieb David Kastrup: "Trevor Daniels" writes: I see really only two reasonably consistent solutions that both involve _not_ using \tweak for the grobbed variant: \tweakGrob Accidental color #red cis or \single \override Accidental color = #red cis since the latter is

Re: [GLISS] turning strings to symbols

Am 12.10.2012 21:01, schrieb Marc Hohl: Am 12.10.2012 16:48, schrieb David Kastrup: "Trevor Daniels" writes: I see really only two reasonably consistent solutions that both involve _not_ using \tweak for the grobbed variant: \tweakGrob Accidental color #red cis or \single

Re: stepping down as project manager

Am 12.10.2012 09:01, schrieb Graham Percival: I guess it's time to make it official: I'm stepping down as project manager. I'll stick around for a while to review patches on countdowns and participate in policy discussions, but don't be surprised if I'm gone for good in a few months. It's sad t

Re: explaining parser subtleties (was: Context.Grob considered as symbol list)

Am 12.10.2012 16:42, schrieb Janek Warchoł: Hi, i'm short on time so i'll try to be brief - hopefully this won't cause any misunderstanding. David, i understand that some comments and questions may look like the sender is questioning your knowledge in some area. I want to assure you that when i

Re: stepping down as project manager

Am 13.10.2012 21:48, schrieb David Kastrup: Janek Warchoł writes: On Sat, Oct 13, 2012 at 4:43 PM, David Kastrup wrote: Janek wrote: Unfortunately, David seems to be the only active developer that understands some parser subtleties - in other words, only he fully knows the whys. Well, ther

Re: stepping down as project manager

Am 13.10.2012 23:44, schrieb David Kastrup: Marc Hohl writes: Conclusion: I appreciate your latest work – it is just that I am not used to use \omit, \single, \undo and therefore bringing \temporary into line with the (yet unfamiliar) rest of the new stuff takes just some time. Perhaps I am

Re: stepping down as project manager

Am 14.10.2012 10:11, schrieb Marc Hohl: Am 13.10.2012 23:44, schrieb David Kastrup: Marc Hohl writes: Conclusion: I appreciate your latest work – it is just that I am not used to use \omit, \single, \undo and therefore bringing \temporary into line with the (yet unfamiliar) rest of the new

Re: bar-line interface part 2/2: New bar line definition standard (issue 6498052)

Am 14.10.2012 19:17, schrieb janek.lilyp...@gmail.com: I dedicate all my code reviews to Graham Percival. Marc, your change is so big that i have trouble grasping it and understanding everything, but i have a few specific comments. Janek http://codereview.appspot.com/6498052/diff/50001/Docume

Re: User-poll about lily-syntax: results - [Was: [GLISS] basics]

Am 15.10.2012 11:15, schrieb Janek Warchoł: Sorry for the delay :( On Sat, Oct 6, 2012 at 10:27 PM, Thomas Morley wrote: Hi, attached are the alphabetic sorted complains/suggestions about LilyPond-syntax from german users. Thanks! This is very valuable. Where should we store these results?

Re: PATCH: Countdown to 20121028

Am 26.10.2012 04:13, schrieb Colin Campbell: For 20:00 MDT Sunday October 28 Enhancement: Issue 2914 : Patch: prevent collision of ligatures and next note - R 6740046 Issue 2919

Re: Allow quoted identifiers like to be used like \"violin1", not just defined. (issue 6778055)

Am 28.10.2012 09:25, schrieb d...@gnu.org: Reviewers: lemzwerg, marc, Message: On 2012/10/28 07:46:36, marc wrote: On 2012/10/26 13:58:41, lemzwerg wrote: > LGTM. +1 Nice to have this feature available! It is more a pacifier than a feature since it does not actually add any functionalit

Re: Allow digits in identifiers (issue 6493072)

Am 29.10.2012 11:05, schrieb d...@gnu.org: [...] I can wave around my long-term plans which would allow for just writing \violin1 by allowing arrays of violins (I have something in a branch right now, but without further syntax changes I am working on it is not really fitting seamlessly into Lil

Re: Allow digits in identifiers (issue 6493072)

Am 29.10.2012 14:29, schrieb David Kastrup: Marc Hohl writes: Am 29.10.2012 11:05, schrieb d...@gnu.org: [...] I can wave around my long-term plans which would allow for just writing \violin1 by allowing arrays of violins (I have something in a branch right now, but without further syntax

What happened to staging?

Hello list, yesterday, I pushed my two outstanding patches to staging and IIRC Benkő Pál has pushed two patches just before me. Now it looks as if origin/staging is in the same state as master, that is, the patches are no longer visible. What happenend to staging? Marc ___

Scheme indentation

Hello list, several weeks ago, Graham was about to run the scheme indentation script on the sources – I asked him to wait until my bar line project has finished in order to make *my* life easier ;-) Now I'd like to do the reformatting work – should this go through Rietveld? It is an automatic ta

Re: What happened to staging?

Am 30.10.2012 09:06, schrieb David Kastrup: Marc Hohl writes: Hello list, yesterday, I pushed my two outstanding patches to staging and IIRC Benkő Pál has pushed two patches just before me. Now it looks as if origin/staging is in the same state as master, that is, the patches are no longer

Re: Allow quoted identifiers like to be used like \"violin1", not just defined. (issue 6778055)

Am 30.10.2012 12:54, schrieb Trevor Daniels: David wrote Tuesday, October 30, 2012 6:05 AM Actually, I would be perfectly fine with binning both \violin.1 as well as \"violin1". I am just afraid it would be a bit like taking candy from a baby. But if people are fine with the prospect of wait

Re: PATCH: Countdown to 20121101

Am 31.10.2012 03:33, schrieb Colin Campbell: For 20:00 MDT Thursday November 1 Enhancement: Issue 2933 : allow optional octavation signs for clefs - R 6813044 Hi Colin, please remove Issue 2933

Re: Allows optional octavation for clefs (issue 6813044)

Am 02.11.2012 09:58, schrieb janek.lilyp...@gmail.com: Hi Marc, the amount of comments is actually a compliment - it means that i understood almost everything! :) Ok, that great then ;-) Please reword the commit message along the lines of the first comment below. Also, i think it would be goo

Re: Allows optional octavation for clefs (issue 6813044)

Am 03.11.2012 23:20, schrieb Janek Warchoł: On Fri, Nov 2, 2012 at 10:20 PM, Marc Hohl wrote: Am 02.11.2012 09:58, schrieb janek.lilyp...@gmail.com: http://codereview.appspot.com/6813044/diff/6001/lily/clef-engraver.cc#newcode125 lily/clef-engraver.cc:125: if (ly_is_procedure (formatter)) it

Re: Scheme indentation

Am 30.10.2012 15:10, schrieb m...@mikesolomon.org: On 30 oct. 2012, at 08:53, Marc Hohl wrote: Hello list, several weeks ago, Graham was about to run the scheme indentation script on the sources – I asked him to wait until my bar line project has finished in order to make *my* life easier

Re: Adds documentation for optional octavation clef syntax (issue 6830043)

Hi Janek, Am 08.11.2012 09:22, schrieb janek.lilyp...@gmail.com: Marc, again i have some objections on wording. Let me assure you that i don't intend to pick on you! :-) Your patches receive so much of my attention because (a) i understand them (not always the case with David's patches for

Re: Adds documentation for optional octavation clef syntax (issue 6830043)

Am 08.11.2012 09:25, schrieb janek.lilyp...@gmail.com: PS please add the issue number and committish of the patch introducing this feature to the commit message of this doc patch. http://codereview.appspot.com/6830043/ Ok, will do. Marc ___ lilypon

Re: Adds documentation for optional octavation clef syntax (issue 6830043)

Am 08.11.2012 10:32, schrieb Marc Hohl: Hi Janek, Am 08.11.2012 09:22, schrieb janek.lilyp...@gmail.com: Marc, again i have some objections on wording. Let me assure you that i don't intend to pick on you! :-) Your patches receive so much of my attention because (a) i understand them

Re: Adds documentation for optional octavation clef syntax (issue 6830043)

Am 09.11.2012 11:12, schrieb Janek Warchoł: Hi Marc, On Thu, Nov 8, 2012 at 9:32 AM, Marc Hohl wrote: Am 08.11.2012 09:22, schrieb janek.lilyp...@gmail.com: I suppose that a parenthesized clef octavation doesn't mean that the octavation is optional (that is, it doesn't mean "

Re: Applies scheme indentation according to the GNU guidelines (issue 6814080)

Am 10.11.2012 14:59, schrieb janek.lilyp...@gmail.com: I've looked a bit at one random file. Looks mostly good to me. http://codereview.appspot.com/6814080/diff/1/scm/define-music-display-methods.scm File scm/define-music-display-methods.scm (right): http://codereview.appspot.com/6814080/d

Re: Applies scheme indentation according to the GNU guidelines (issue 6814080)

Am 11.11.2012 13:45, schrieb gra...@percival-music.ca: Some people (notably Jan) were quite vocal about wanting to use "whatever emacs does" literally, regardless of bugs. I support this view; the important thing is consistent indentation. However, I don't see any fixscm.sh in this patch. I do

Re: [talk] suggestion: redesign "sponsoring" page.

Am 10.11.2012 15:44, schrieb Phil Holmes: - Original Message - From: "Graham Percival" To: "David Kastrup" Cc: "Benjamin CL" ; "LilyPond Developmet Team" Sent: Friday, November 09, 2012 7:26 PM Subject: Re: [talk] suggestion: redesign "sponsoring" page. On Fri, Nov 09, 2012 at 07

Re: User-poll about lily-syntax: results - [Was: [GLISS] basics]

Am 15.10.2012 11:55, schrieb Francisco Vila: 2012/10/15 Marc Hohl : But anyway, are there results from user-polls on other lists? Yes, there are a few ones. They are mainly generic complaints, not specific syntax related. I will make a summary. I don't want to be too pushy, but Harm&#

Re: Applies scheme indentation according to the GNU guidelines (issue 6814080)

Am 11.11.2012 23:32, schrieb Graham Percival: On Sun, Nov 11, 2012 at 02:22:30PM +0100, Marc Hohl wrote: Am 11.11.2012 13:45, schrieb gra...@percival-music.ca: Some people (notably Jan) were quite vocal about wanting to use "whatever emacs does" literally, regardless of bugs. I su

Re: [Lilypond-auto] Issue 2948 in lilypond: Patch: Applies scheme indentation according to the GNU guidelines

Am 12.11.2012 10:39, schrieb lilyp...@googlecode.com: Comment #9 on issue 2948 by d...@gnu.org: Patch: Applies scheme indentation according to the GNU guidelines http://code.google.com/p/lilypond/issues/detail?id=2948 Regarding http://codereview.appspot.com/6814080#msg2>: I have tried lookin

Re: [Lilypond-auto] Issue 2948 in lilypond: Patch: Applies scheme indentation according to the GNU guidelines

Am 12.11.2012 10:39, schrieb lilyp...@googlecode.com: Comment #9 on issue 2948 by d...@gnu.org: Patch: Applies scheme indentation according to the GNU guidelines http://code.google.com/p/lilypond/issues/detail?id=2948 Regarding http://codereview.appspot.com/6814080#msg2>: I have tried lookin

Re: How to do proper indentation?

Am 30.11.2012 02:16, schrieb Thomas Morley: Hi, reviewing https://codereview.appspot.com/6850073/ Pál admonished to do better indentation on lists at different levels. Trying to minimize my lack of knowledge on this topic I searched the CG about It. CG 10.5.3 Indentation mentions possibilities

Re: Issue 2966 - Patch-push

Hi Harm, Am 11.12.2012 20:54, schrieb Thomas Morley: Hi, someone up to push it for me? http://code.google.com/p/lilypond/issues/detail?id=2966 https://codereview.appspot.com/6850073/ I don't know if your patch consists of a single commit or a series of commits, but in either case, you should

Re: Tablature: ignore minimumStretch to/from fret zero (issue 6944061)

Am 21.12.2012 08:01, schrieb gra...@percival-music.ca: Not really about this patch, but what happened to the plans for running scripts/auxiliar/fixscm.sh ? There were objections about the way emacs does the automatic formatting, and I am not sure how one can preformat stuff so that the script wi

Re: [Lilypond-auto] Issue 3150 in lilypond: oversight in repeats.itely with old bar-line-glyphs

[code.google.com doesn't let me use the html form to reply, I claims out that thomasmorle...@googlemail.com is an invalid owner username. Huh?] Am 01.02.2013 09:20, schrieb lilyp...@googlecode.com: Comment #2 on issue 3150 by d...@gnu.org: oversight in repeats.itely with old bar-line-glyphs

Re: [Lilypond-auto] Issue 3182 in lilypond: Patch: Defuse the obfuscated Scheme programming contest

Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com: Status: Started Owner: d...@gnu.org Labels: Type-Enhancement Patch-new New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme programming contest http://code.google.com/p/lilypond/issues/detail?id=3182 Defuse the obfuscated Sc

Re: [Lilypond-auto] Issue 3182 in lilypond: Patch: Defuse the obfuscated Scheme programming contest

Am 16.02.2013 09:29, schrieb David Kastrup: Marc Hohl writes: Am 15.02.2013 14:02, schrieb lilyp...@googlecode.com: Status: Started Owner: d...@gnu.org Labels: Type-Enhancement Patch-new New issue 3182 by d...@gnu.org: Patch: Defuse the obfuscated Scheme programming contest http

Re: strange rest positions in tablature?

Am 19.02.2013 09:43, schrieb Werner LEMBERG: Folks, have a look at bar 3 in regression file `tablature-full-notation.'ly'. The positioning of the rests in the lower tablature staff looks strange to my eyes... +1 Moreover, the slur position is not optimal in the lower tablature staff and the t

Re: bar-line.scm

Am 20.02.2013 13:20, schrieb David Kastrup: "m...@mikesolomon.org" writes: Hey all, Would it be OK to get rid of all the ly: prefixes in bar-line.scm? Sorry for not catching this before. I'd prefer if all native Scheme functions did not have the ly: prefix - it helps to know what things are

Re: Freezing for 2.18

Am 10.03.2013 18:32, schrieb David Kastrup: Ok folks, it is this time of the year again: I am trying to make myself unpopular. [...] So I want to see 2.18 soon. That means we need to stabilize work that has already been done and cut down on experiments in the master branch. Stabilizing means

Re: Freezing for 2.18

Am 10.03.2013 20:56, schrieb David Kastrup: Marc Hohl writes: Am 10.03.2013 18:32, schrieb David Kastrup: Ok folks, it is this time of the year again: I am trying to make myself unpopular. [...] So I want to see 2.18 soon. That means we need to stabilize work that has already been done

bar line interface / repat structure considerations

Hello list, after some discussions on -user (partly emotional - sorry for that!) I promised to think about improving the bar line interface. Well, hereare some preliminary results. The mail got a bit long, so make sure you sit comfortable and have a nice cup of coffee, tea or whatever around...

Re: bar line interface / repat structure considerations

Am 13.03.2013 10:09, schrieb Marc Hohl: [...] a) replace the current mechanism by a command (define-bar-line ( :prebreak :postbreak :span-bar :prebreak-span :postbreak-span )) where :prebreak, :postbreak, :spanbar, :prebreak-span and :postbreak-span arguments are optional,and we define

Re: bar line interface / repat structure considerations

Am 13.03.2013 10:27, schrieb David Kastrup: Marc Hohl writes: Hello list, after some discussions on -user (partly emotional - sorry for that!) I promised to think about improving the bar line interface. Well, hereare some preliminary results. The mail got a bit long, so make sure you sit

Re: bar line interface / repat structure considerations

Am 13.03.2013 12:18, schrieb David Kastrup: Marc Hohl writes: Am 13.03.2013 10:27, schrieb David Kastrup: One reason I am skeptical about this particular suggestion is that more often than not (like the typical multi-stanza pop song with a separate ending), D.S.a.C is _intertwined_ with

Re: alignment of unattached lyrics - opinions needed

Am 15.03.2013 09:00, schrieb Janek Warchoł: Hi, [...] On Fri, Mar 15, 2013 at 2:51 AM, Thomas Morley wrote: if neither \addlyrics nor \lyricsto or associatedVoice is used, why align the lyrics? This is a user-error or it is intended. I think usually this is just user sloppiness. In this c

Re: alignment of unattached lyrics - opinions needed

Am 15.03.2013 14:18, schrieb Janek Warchoł: Hi, [...] Just a thought. Would it make sense to handle unassociated Lyrics like a text markup, quite as David proposed? I could imagine that something like http://lsr.dsi.unimi.it/LSR/Item?id=744 would be quite cool. I'm not sure what you mean.

Re: bar line interface / repat structure considerations

Am 13.03.2013 17:05, schrieb Janek Warchoł: Hi Marc&all, On Wed, Mar 13, 2013 at 10:09 AM, Marc Hohl wrote: make sure you sit comfortable and have a nice cup of coffee, tea or whatever around... these words actually reminded me that i had a tea waiting, and thanks to you it didn&#

Re: Documents make-partial-ellipse-stencil (issue 7497046)

Am 17.03.2013 17:27, schrieb m...@mikesolomon.org: On 17 mars 2013, at 17:22, m...@hohlart.de wrote: Just one nitpick. https://codereview.appspot.com/7497046/diff/1/scm/stencil.scm File scm/stencil.scm (right): https://codereview.appspot.com/7497046/diff/1/scm/stencil.scm#newcode251 scm/ste

Re: R shorthand

Am 19.03.2013 20:41, schrieb David Kastrup: Kieren MacMillan writes: Hello all, While answering Helge's post about multi-measure rests, I had a couple of R-elated observations/thoughts: 1. We shouldn't be encouraging code like R4*3 in a 4/4 measure, right? So the duration ultimately makes no

Re: (almost-)freezing current master

Am 21.03.2013 19:19, schrieb m...@mikesolomon.org: Hey all, To prepare for 2.18, I think we can get it out fastish, but we need to more or less freeze current master aside from bug fixes and documentation. I have a lot of stuff on the countdown or on patch push that I'm notgonna push for a few m

Re: suggestion: change OctavateEight name to ClefTransposition - opinions?

Am 05.04.2013 23:02, schrieb Janek Warchoł: Hi, The name "OctavateEight" doesn't have any sense - it doesn't show that this grob is related to the clef, and anyway the clef can be "transposed" by any amount, not just an octave. I suggest to rename this grob to ClefTransposition or something simi

Re: suggestion: change OctavateEight name to ClefTransposition - opinions?

Am 06.04.2013 23:44, schrieb David Kastrup: Marc Hohl writes: Am 05.04.2013 23:02, schrieb Janek Warchoł: Hi, The name "OctavateEight" doesn't have any sense - it doesn't show that this grob is related to the clef, and anyway the clef can be "transposed" by any

triple flats/sharps?

Hello list, yesterday I stubled upon a problem with chord transposition. We had a jazz tune in c major with an a-flat:dim7 chord. When transposing this tune to e-flat major, lilypond complains about a missing triple flat and prints a c-flat minor 6/b5 instead (which is enharmonically correct, b

Re: triple flats/sharps?

Am 07.05.2013 11:33, schrieb Thomas Morley: 2013/5/7 Marc Hohl : Hello list, yesterday I stubled upon a problem with chord transposition. We had a jazz tune in c major with an a-flat:dim7 chord. When transposing this tune to e-flat major, lilypond complains about a missing triple flat and

engraver question: how to define an array to store events?

Hello list, while trying to get more insight into the engraver stuff, I encountered a problem. I hope I can explain it: I need some kind of a array of vectors: vector slot_[max]; where I can store events later on by calling slot_[i].push_back (event); The index i lies in a fixed range from 0

Re: pitch to string conversion in c++

Am 16.09.2011 10:43, schrieb David Kastrup: Marc Hohl writes: [...] Unnecessary copying. Better do Pitch *current_pitch = unsmob_pitch (event->get_property ("pitch")); string pitchstring = current_pitch->to_string (); Perfec

Re: engraver question: how to define an array to store events?

Am 20.09.2011 08:59, schrieb Marc Hohl: Hello list, while trying to get more insight into the engraver stuff, I encountered a problem. I hope I can explain it: I need some kind of a array of vectors: Nevermind - smells like the wrong way to go ;-) I think I found a more generic solution

Re: problems with user-defined command line options

> cc'ing to -devel, perhaps it is a bug? Am 24.12.2011 00:41, schrieb -Eluze: hi Marc Hohl wrote: Hello list, I have some files with songs where I want to switch the slurs on and off. After searching the docs, I came up with this: optional-

Re: (was) Some drum notation questions - (now) problem with noteheads in doc?

Am 04.01.2012 19:59, schrieb James: On 4 January 2012 18:55, James wrote: Hello, On 4 January 2012 18:32, Vaylor Trucks wrote: I have been using lilypond for years for my own projects and have recently introduced it to a friend of mine. He is a drum instructor and has been reading drum nota

Re: how to check clef type?

Am 07.01.2012 23:56, schrieb Janek Warchoł: 2012/1/7 m...@apollinemike.com: On Jan 7, 2012, at 1:49 AM, Janek Warchoł wrote: Hi, i'm inside Clef_engraver::create_clef () - line 130 of lily/clef-engraver.cc I'd like to do sth based on the clef type (G, F or C). What condition should i use? I

Re: 2.16 release candidate 3 imminent

Am 21.01.2012 18:44, schrieb Carl Sorensen: On 1/21/12 10:37 AM, "David Kastrup" wrote: I have actually found out that I promised too much about string numbers appearing on isolated notes: since the string number events _are_ listened to (likely by the tabstaff engraver team), the rhythmic mu

Re: 2.16 release candidate 3 imminent

Am 21.01.2012 19:41, schrieb David Kastrup: Marc Hohl writes: Am 21.01.2012 18:44, schrieb Carl Sorensen: On 1/21/12 10:37 AM, "David Kastrup" wrote: I have actually found out that I promised too much about string numbers appearing on isolated notes: since the string number ev

Re: 2.16 release candidate 3 imminent

Am 21.01.2012 20:17, schrieb Carl Sorensen: On 1/21/12 11:47 AM, "Marc Hohl" wrote: I must admit that I am lost here and do not quite understand what's going on, but will there be any difference between < c\3 e\2 g\1> and< c e g>\3\2\1 once these changes a

Re: Creates a MIDI note length formatter (issue 5576062)

Am 29.01.2012 10:35, schrieb mts...@gmail.com: Reviewers: , Message: The idea here is to create a generic framework that allows for modifications to note lengths (i.e. swing) in the MIDI without having a typographical impact on the score. Brilliant idea, from my rather amatheurish point of view

Re: Creates a MIDI note length formatter (issue 5576062)

Am 31.01.2012 08:52, schrieb m...@apollinemike.com: On Jan 31, 2012, at 8:48 AM, Marc Hohl wrote: Am 29.01.2012 10:35, schrieb mts...@gmail.com: Reviewers: , Message: The idea here is to create a generic framework that allows for modifications to note lengths (i.e. swing) in the MIDI without

Re: Creates a MIDI note length formatter (issue 5576062)

Am 31.01.2012 09:09, schrieb m...@apollinemike.com: On Jan 31, 2012, at 8:59 AM, Marc Hohl wrote: Am 31.01.2012 08:52, schrieb m...@apollinemike.com <mailto:m...@apollinemike.com>: On Jan 31, 2012, at 8:48 AM, Marc Hohl wrote: Am 29.01.2012 10:35, schrieb mts...@gmail.com <m

Re: Creates a MIDI note length formatter (issue 5576062)

Am 31.01.2012 09:28, schrieb David Kastrup: Marc Hohl writes: Am 31.01.2012 08:52, schrieb m...@apollinemike.com: On Jan 31, 2012, at 8:48 AM, Marc Hohl wrote: Am 29.01.2012 10:35, schrieb mts...@gmail.com: Reviewers: , Message: The idea here is to create a generic framework that allows

Re: Creates a MIDI note length formatter (issue 5576062)

Am 31.01.2012 10:57, schrieb David Kastrup: Marc Hohl writes: Am 31.01.2012 09:09, schrieb m...@apollinemike.com: Check out: http://crism.maden.org/music/swing.ly This is a function that takes music and returns two musics, one swung and one unswung, w/ appropriate tags for layout and midi

Re: Creates a MIDI note length formatter (issue 5576062)

Am 31.01.2012 10:56, schrieb m...@apollinemike.com: [...] I wrote my own set of Scheme functions based on this method that got all the swing I needed into a score. Would you mind to post these functions? I am currently working on a project that needs swing articulation, so I would be glad to

Re: OSX 10.7, fonts and fondu?

Am 01.02.2012 11:06, schrieb padovani: Em 2/1/12 6:34 AM, Marc Hohl escreveu: Am 31.01.2012 21:55, schrieb padovani: hello, I'm having troubles with 2.15.27 and OSX 10.7.2. In a simple piece of code using fonts like Texier's Controla (http://christian.texier.pagespro-orange.fr/mid

Re: Errors in examples

Am 05.02.2012 18:51, schrieb Thomas Morley: [...] I added \voiceOne near the end of the first voice. Of course this changes the stem-direction (which I'd prefer) but Graham told not to change the output. IIRC, the definition for calc-extra-dy is included in the source as glissando::calc-tab-ext

Re: Errors in examples

Am 05.02.2012 20:16, schrieb Marc Hohl: Am 05.02.2012 18:51, schrieb Thomas Morley: [...] I added \voiceOne near the end of the first voice. Of course this changes the stem-direction (which I'd prefer) but Graham told not to change the output. IIRC, the definition for calc-extra-

Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)

Hello all, while typesetting a piece for two guitars, I stumbled across the influence of the commit mentioned above. Before that, something like \set minimumFret = #2 dis'8 ( e' dis ) h fis2 worked smoothly out of the box, now I have to tell lilypond explicitly which string to use when I want

Re: Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)

Am 14.02.2012 09:58, schrieb Marc Hohl: Hello all, while typesetting a piece for two guitars, I stumbled across the influence of the commit mentioned above. Before that, something like \set minimumFret = #2 dis'8 ( e' dis ) h fis2 worked smoothly out of the box, now I have to tel

Re: Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)

Am 14.02.2012 21:01, schrieb David Kastrup: Marc Hohl writes: Am 14.02.2012 09:58, schrieb Marc Hohl: +\set TabStaff.handleOpenStrings = #'forbid +< g, d>1 + } +} diff --git a/ly/engraver-init.ly b/ly/engraver-init.ly index 6335ab6..11181d3 100644 --- a/ly/engraver-init.

Re: Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)

Am 14.02.2012 21:18, schrieb Marc Hohl: Am 14.02.2012 21:01, schrieb David Kastrup: Marc Hohl writes: Am 14.02.2012 09:58, schrieb Marc Hohl: +\set TabStaff.handleOpenStrings = #'forbid +< g, d>1 + } +} diff --git a/ly/engraver-init.ly b/ly/engraver-init.ly index 6335a

Re: Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)

Am 14.02.2012 21:31, schrieb David Kastrup: Marc Hohl writes: [...] Symbols 'allow and 'forbid are not a typical interface. You would rather use a boolean here. Yes, you are right, I changed it accordingly. Um, does allowOpenStrings = ##t sound better than handleOpenStrings =

Re: Using other NoteHeads with \harmonicByFret?

Am 16.02.2012 22:53, schrieb Thomas Morley: Hi Marc, 2012/2/14 Marc Hohl: Hi Harm, Do you want to bundle up your definitions in a patch so they get included future versions of lilypond? Thanks for your work on this! Regards, Marc I don't know what I'm expected to do here and

Re: Gets vertical skylines from grob stencils (issue 5626052)

Am 23.02.2012 14:35, schrieb d...@gnu.org: On 2012/02/23 12:37:04, MikeSol wrote: http://codereview.appspot.com/5626052/diff/40001/lily/stencil-integral.cc File lily/stencil-integral.cc (right): http://codereview.appspot.com/5626052/diff/40001/lily/stencil-integral.cc#newcode932 lily/sten

Re: Gets vertical skylines from grob stencils (issue 5626052)

Am 23.02.2012 15:59, schrieb David Kastrup: Marc Hohl writes: As the person who wrote a lot of stuff for tablature and removed the stems and stuff by default, "made them transparent" Yes, of course ;-) I second that it is an ugly workaround. Ideally, I had removed the stem/fla

Two patches

Hello list, there are two tiny patches concerning open strings and harmonics in tablature: http://lists.gnu.org/archive/html/lilypond-devel/2012-02/msg00541.html http://lists.gnu.org/archive/html/lilypond-devel/2012-02/msg00451.html I am not allowed to push to dev/staging, so what is the fo

Re: Two patches

Am 24.02.2012 09:30, schrieb David Kastrup: Marc Hohl writes: Hello list, there are two tiny patches concerning open strings and harmonics in tablature: http://lists.gnu.org/archive/html/lilypond-devel/2012-02/msg00541.html "touching the strings above fret" is misleading. Yo

<    1   2   3   4   5   6   7   >