Re: Multiple clefs in one Staff

David Kastrup ezt írta (időpont: 2023. okt. 27., P, 11:46): > > Werner LEMBERG writes: > > >> Inspired by > >> > >> > >> Should we be offering something like that? > > > > What exactly do you

Re: Explicit default duration?

Jean Abou Samra ezt írta (időpont: 2023. jan. 22., V, 23:45): > > On 22/01/2023 23:38, David Kastrup wrote: > > > > There are situations where sticking with the default duration may make > > sense when something looking like (or being) an explicit duration may > > follow. > > > > Like when

Re: pygment regex question,Re: pygment regex question

Jean Abou Samra ezt írta (időpont: 2022. nov. 25., P, 18:05): > > Le 25 nov. 2022 à 17:54, Werner LEMBERG a écrit : > > OK, but shouldn't this be rather > > (-?\d+|\\longa|\\breve)\.* > > then? > > Why not. If you want to be even more precise on what you want to match: > >

Re: SMuFL name mapping update, 17 March

Hi Owen, Owen Lamb ezt írta (időpont: 2022. márc. 19., Szo, 7:38): > > Hi Benkő, > > On 3/17/22 10:05, Benkő Pál wrote: > > re the longest rests: > 1. a perfect longa rest and a maxima rest are not the same; > 2. a perfect longa rest should take three spaces (l

Re: SMuFL name mapping update, 17 March

Hi Owen, first: thanks for this work. Owen Lamb ezt írta (időpont: 2022. márc. 17., Cs, 16:42): > > Hi all, > > I've finished mapping the last five glyph categories: Mensural, > Neomensural, Petrucci, Solesmes, and Kievan. Of those, only the Mensural > and Neomensural glyphs provided much

Re: Ancient repeat sign

Hi Dan, Dan Eble ezt írta (időpont: 2022. febr. 6., V, 21:32): > > https://www.pinterest.ca/pin/560909328587237881/ > > The sections of this work seem to be separated with a kind of repeat sign. > > A :|||: B :|||: C :||: D :|: > > Q. Do I understand correctly that this is performed

Re: 'blackpetrucci' stem attachment

blackpetrucci was introduced by me to support coloratio. the intent was to change just the noteheads; I just didn't know I had to do anything beyond defining new noteheads. I'm using it on a (sort of) daily basis, but didn't notice. p Werner LEMBERG ezt írta (időpont: 2022. jan. 15., Szo,

Re: Please review Pygments lexer and style

Jean Abou Samra ezt írta (időpont: 2021. jún. 24., Cs, 20:17): > I'll style \longa in bold too. \longa is a duration, like 2 in c2; on the other hand 3 in \repeat \unfold 3 or \time 3/4 is not a duration. now the 4 in \time 3/4 is arguably a duration, but... p

Re: guile libraries

There's a quick path for an underperforming lilypond: sudo apt install guile-2.2-dev. The slow path for good performance is installing guile-1.8 from its git repository, which I never did. Al Rice ezt írta (időpont: 2021. márc. 15., H, 18:36): > > Greetings, > > My name is Al. I am a retied

Re: tie over clef change

David Kastrup ezt írta (időpont: 2020. szept. 27., V, 22:01): > > Hans Åberg writes: > > >> On 27 Sep 2020, at 19:57, Lukas-Fabian Moser wrote: > >> > >>> I seem to remember that even in Bach's B minor mass (where E12 was not > >>> yet a thing) there is an enharmonic tie (or at least tonal

Re: ancient convert rules

Hi Jonas, > I think I found a solution that works equally well as it did when > running convert-ly with Python 2. Please see the second commit of > https://gitlab.com/lilypond/lilypond/-/merge_requests/365 for what I > tested. I tested this branch (my first try with GitLab, I hope I got it

Re: ancient convert rules

FWIW, I ran a grep on my files, and the oldest version is 2.4.4; there are also several 2.9, 2.10 and 2.11 ones. I admit I rarely touch old files, but sometimes that happens. James Lowe ezt írta (időpont: 2020. aug. 30., V, 16:32): > > On 30/08/2020 14:38, Jonas Hahnfeld wrote: > > To make the

Re: Repeat alternative count

\alternative volta 3 { ... } ? Dan Eble ezt írta (időpont: 2020. aug. 29., Szo, 15:37): > > Is there a use case for specifying the number of times to reuse a repeat > alternative in a way that \unfoldRepeats could honor? Right now, it reuses > the first alternative enough times to reach the

Re: GSoC 2020 update, July 18

> command once I'm done with GSoC. Otherwise, this would probably be a good > idea for a separate feature request. > > Hope this helps, > Owen > > On Tue, Jul 21, 2020 at 3:28 AM Benkő Pál wrote: >> >> Thanks. Lukas, that's what I looked for! On the next p

Re: GSoC 2020 update, July 18

Thanks. Lukas, that's what I looked for! On the next page there are dragmas with flags on both stem and ones with flags only on the down stem. Lukas-Fabian Moser ezt írta (időpont: 2020. júl. 21., K, 11:32): > > Hi Pál, > > > in ancient (ars subtilior) notation there actually are noteheads with

Re: GSoC 2020 update, July 18

in ancient (ars subtilior) notation there actually are noteheads with two stems (which may also be flagged differently), called "dragma". a picture search for "dragma ars subtilior" returned poor images; one not entirely useless is

Re: can a Scheme engraver "solve" Issue #34 (grace note bug)? [cross-posted]

Han-Wen Nienhuys ezt írta (időpont: 2020. febr. 8., Szo 21:44): > > > If we construct the grace note grobs in a > special pass, there is nothing to synchronize them across staves. You could > have two-handed piano music where the left and right hand do grace notes in > a synchronized way. I

Re: lilypond-2.19.84

the News section at lilypond.org dates 2.19.84 to 2019. can I (or anyone else) push a fix to staging? Jean-Charles Malahieude ezt írta (időpont: 2020. febr. 6., Cs, 18:46): > > Hi, > > Please find a new tarball for LilyPond at > >

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

David Kastrup ezt írta (időpont: 2020. febr. 6., Cs, 14:38): > > Benkő Pál writes: > > > Janek Warchoł ezt írta (időpont: 2020. > > febr. 6., Cs, 0:32): > >> > >> I'll try to speak only on the most pressing points to avoid bloating the > >&g

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Janek Warchoł ezt írta (időpont: 2020. febr. 6., Cs, 0:32): > > I'll try to speak only on the most pressing points to avoid bloating the > discussion unnecessarily. > > I stopped contributing to LilyPond about 6 years ago. One cause of that > change was that I got a job and suddenly had much less

Re: Clean up embedded scheme parsing/evaluation. (issue 577410045 by hanw...@gmail.com)

ezt írta (időpont: 2020. jan. 31., P, 11:55): > > > https://codereview.appspot.com/577410045/diff/581560047/lily/parse-scm.cc > File lily/parse-scm.cc (right): > > https://codereview.appspot.com/577410045/diff/581560047/lily/parse-scm.cc#newcode77 > lily/parse-scm.cc:77: const Input *hi =

Re: misplaced-note-head bug (issue 5303)

David Kastrup ezt írta (időpont: 2019. júl. 4., Cs, 18:16): > > "Phil Holmes" writes: > > > - Original Message - > > From: "Lukas-Fabian Moser" > >> > >> Questions: > >> > >> a) How to decide which fix is "better"? (My guess that using floats > >> might pose the danger of rounding

Re: stack smashing detected

Thomas Morley ezt írta (időpont: 2019. ápr. 28., V, 15:13): > > Am Fr., 26. Apr. 2019 um 20:06 Uhr schrieb Benkő Pál : > > the book I learned Bézier and B-splines from: > > http://www.cin.ufpe.br/~mdlm/files/Farin-5a_edicao.pdf > > Thanks for the hint. > More tha

Re: stack smashing detected

Hi Andrew, > That's a good book, but it is copyright 2002 Academic Press. So it is not > freely distributable. > > Generally speaking, since the lilypond community is strongly committed to > open source and its philosophy, suggesting violations of copyright are not > highly regarded. I am

Re: stack smashing detected

Thomas Morley ezt írta (időpont: 2019. ápr. 25., Cs, 18:57): > > > So usually your goals would be better served by > > > allowing _multiple_ cubic beziers in a row with suitable continuity of > > > derivatives (and thus some aspects of the control points) provided > > > automagically. > > > >

Re: stack smashing detected

David Kastrup ezt írta (időpont: 2019. ápr. 25., Cs, 16:46): > > Thomas Morley writes: > > > Background: I'm exploring whether it would be feasible to draw higher > > order bezier-curves, splitting them in cubic ones. you can't split a Bezier curve into lower order ones, only approximate. > So

Re: New LilyPond contributor: Basia Mroczek

Ubuntu 16.04 should be OK, I use that too. Though it's a lng time I tried a make check. p Carl Sorensen ezt írta (időpont: 2018. nov. 23., P, 19:10): > > I recommend that you start by building on LilyDev, rather than on your own > system. You can set up LilyDev in a VM, and make sure that

Re: vertical position of Rests and MMRs

2018-01-17 13:21 GMT+01:00 David Kastrup : > Malte Meyn writes: > >> Hi list, >> >> I need some advice on how to deal with breve and longer rests. While I >> tried to fix issue 3208 (correct choice of rest glyphs for MMRs) I >> also “fixed” vertical position

Re: issue 3208: MMRs for > 1 m. only count m. (issue 333340043 by lilyp...@maltemeyn.de)

2018-01-06 17:48 GMT+01:00 : > On 2018/01/04 19:48:36, benko.pal wrote: >> >> is there an example where a single measure rest looks different standing >> alone >> than one in an expanded multi-measure rest of odd measures? > > Not in Gould’s “Behind Bars”, neither in

Re: NR: Update Clef styles Appendix (issue 324420043 by pkx1...@gmail.com)

Hello James, > I took a bit of time to educate myself with Ancient notation and have, > hopefully, picked the correct note styles now. > > Should I use the red 4-line-staff for the rest of the examples or just > for the Gregorian clefs? Just for the Gregorian clefs. Mensural clefs, as the

Re: add some rarely used mensural clefs (issue 330120043 by benko....@gmail.com)

All, >> Phil, whatever you can offer to help. I know nothing about Ancient music >> typesetting and was just basing my additions on what was already in the >> NR. I had asked a few years ago for some help with the Ancient music NR >> section oh, sorry, I missed it. I'm glad to help (I guess

Re: add some rarely used mensural clefs (issue 330120043 by benko....@gmail.com)

> I am updating the doc to include these new clefs (and add all ancient > clefs to appendix A10 I wanted to look at it, but you beat me -- thanks a lot! p ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: add some rarely used mensural clefs (issue 330120043 by benko....@gmail.com)

> I saw that Phil gave you write access now. However to save you and > everyone time I created > > https://sourceforge.net/p/testlilyissues/issues/5184 > > for you and have tested the patch. Thank you, Phil and James! I could finish git-cl configuration, and hope that next time everything goes

Re: add some rarely used mensural clefs (issue 330120043 by benko....@gmail.com)

2017-09-05 22:17 GMT+02:00 Benkő Pál <benko@gmail.com>: >>> Please review this at https://codereview.appspot.com/330120043/ >> >> >> Does this have a tracker or do we need to create one? >> >> I couldn't see one immediately. > > no, I'm strug

Re: add some rarely used mensural clefs (issue 330120043 by benko....@gmail.com)

>> Please review this at https://codereview.appspot.com/330120043/ > > > Does this have a tracker or do we need to create one? > > I couldn't see one immediately. no, I'm struggling with it. seems this is my first contribution since leaving google code. (and I had the same regression you had

Re: Fix build failure on GNU Hurd (issue 319400043 by pkx1...@gmail.com)

2017-03-04 19:03 GMT+01:00 : > On 2017/02/25 15:19:47, felix.janda_posteo.de wrote: >> >> The fix probably breaks compilation on everything not using glibc: Is lilypond supposed to be built on anything outside GNU/Linux? ___

Re: Stepping down and moving on

2016-11-10 11:46 GMT+01:00 Andrew Bernard : > David, > > I wish you all the very best for your future endeavours. I thank you most > sincerely for your immensely significant and important contribution to > making lilypond the exceptional tool for engraving that it is.

Re: BUG: Lilypond forgets to draw barline spanner after \bar ""

sorry for the noise. 2016. szept. 19. 18:46 ezt írta ("David Kastrup" <d...@gnu.org>): > Benkő Pál <benko@gmail.com> writes: > > >> c2 \bar "" \break c2 c4 > >> > >> That should be two bars with a barline in the middle. >

Re: BUG: Lilypond forgets to draw barline spanner after \bar ""

> c2 \bar "" \break c2 c4 > > That should be two bars with a barline in the middle. I think not; \bar "" starts a new bar (after issuing a warning for the incomplete bar). p ___ lilypond-devel mailing list lilypond-devel@gnu.org

looking for Christian Mondrup

all, does anybody know a working e-mail address of his? perhaps do you still lurk here, Christian? thanks, p ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: pushing to a new branch on server

2016-05-31 8:15 GMT+02:00 Federico Bruni : > I could not push to a /dev/name/branch name. I had to use a short name > without slashes: > > git push origin translation:fedelibre-doc-it > > while the following did not work: > > git push origin translation:/dev/fede/doc-it > > Not

Re: New context modifier \CompletionRhythms?

> At the risk of being blunt: more generally, is there a legitimate use > case for completion heads? It never occurred to me that some people > (like Simon, it seems) might rely on it that regularly; I used to > regard it as one of those feature that seem nice at first but that > typically tend to

Re: modify coord-rotate to get exact values for (sin PI) etc (issue 269530043 by thomasmorle...@gmail.com)

> Just back home, noticing the discussion here. > > Current patch tries to solve (or better: workaround) the problem in > guile. > I have some other pending patches _needing_ exact values from > coord-rotate. > I'd suggest to push it as is (unless some serious defect would be > detected) after

Re: modify coord-rotate to get exact values for (sin PI) etc (issue 269530043 by thomasmorle...@gmail.com)

> And PostScript (and PDF and METAFONT) _do_ represent angles in degrees. > So it's sort of silly that we cannot get an angle of 180 degrees > straight into PostScript without change. now that convinced me. if we want to output angles in degrees, we don't want to switch back and forth neither

Re: modify coord-rotate to get exact values for (sin PI) etc (issue 269530043 by thomasmorle...@gmail.com)

2015-10-30 14:46 GMT+01:00 : > On 2015/10/30 13:20:35, benko.pal wrote: >> >> sorry to chime in that late, but: >> am I right that the problem is that we get the rotation matrix >> cos a -sin a >> sin acos a >> inexact? and if so, how the inexactness is present? one of the >

Re: List of Issues with 'patch_abandoned' assigned to them - as of September 2015

not exactly abandoned, just needs-work since more than three years: http://sourceforge.net/p/testlilyissues/issues/2474/ I forgot I was waiting for feedback, as I believe I answered all raised concerns. p ___ lilypond-devel mailing list

Re: Allura at SF is ready

2015-08-29 11:30 GMT+02:00 Trevor Daniels t.dani...@treda.co.uk: Pál, you wrote Saturday, August 29, 2015 8:21 AM I also noted that explicit links like https://code.google.com/p/lilypond/issues/detail?id=2249 are not converted. Again, not a big problem, just some inconvenience in reading

Re: Allura at SF is ready

The migration of the tracker from GC to Allura at SF has gone well. Attachments are present and searches work (in the Allura style, which takes some getting used to, but is pretty comprehensive.) I've set up some common searches to make things easier. You can view it here to inspect and

Re: Music glyph design choices

I don't have double flat examples from real music Das Wohltemperierte Klavier has some double flats, look at the E-flat and B-flat minor pieces. as far as I can see, 19th century scores use two identical flats for a double flat, while early 20th century ones are more like Feta. p

Re: CG manual, pushing to staging

2015-07-18 17:57 GMT+02:00 Federico Bruni f...@inventati.org: What do you think about these instructions? http://lilypond.org/doc/v2.19/Documentation/contributor/pushing-to-staging I have a few comments, but I'm not sure about any of them: 1. There's no real purpose in pulling and rebasing

Re: CG manual, pushing to staging

2015-07-18 19:05 GMT+02:00 Federico Bruni f...@inventati.org: $ git push origin HEAD:staging That's probably how I would like to work (so I don't need the patch file). `git fetch` fetches implicitly from a particular branch? What's the purpose of HEAD:staging? moves the branch on remote to

Re: How to edit Author in a patch ready to push

2015-06-12 22:20 GMT+02:00 Thomas Morley thomasmorle...@gmail.com: Though, the current patch for 4428 shows: Author: harm harm@debian.domain Is there any way to change it to: Author: Thomas Morley thomasmorle...@gmail.com ? my guess is git commit --amend --reset-author --no-edit p

Re: Strange make check error

I suspect that we got ourselves a problem with Ubuntu 15.04. I got the same assertion, on Lubuntu 15.04. p ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Fix issue 4355 -- broken beam subdivision (issue 226700043 by carl.d.soren...@gmail.com)

2015-04-25 10:20 GMT+02:00 lilyli...@googlemail.com: Thank you for picking this up. It is certainly an improvement already. However: In an example where 8 32th notes are subdivided by 16th notes ony the first and third subdivision should have two beams, the second one only one beam. Put

Re: [PATCH] support for flagged crotchets in mensural notation

hello Lukas, here's my next portion of patches for the extended mensural notation support I mentioned the other day. This bit is to get full support for the various options relating to black and hollow (unflagged and flagged) small note values (crotchets and below), as discussed in section

Re: [PATCH] support for flagged crotchets in mensural notation

as far as I know when flagged notes with hollow heads are used, they are used exclusively, i.e. there are no black notes at all (more precisely, all black notes count as notae coloratae, which is a separate notehead style anyway, and from duration point of view they behave just as their hollow

Re: Issue 3286: add single-C time signature style (issue 164830043 by nine.fierce.ballads at gmail.com)

I don’t recall that anybody so far has been able to explain how they know a piece is in 4/2 when it is denoted cut-C. Can you? as well as knowing whether a customary C (cut or uncut) signals 2/2 or 4/4 (or 1/1, see below). I maintain that the second Kyrie from Bach's Mass in B minor is in

Re: Adds incipit section to NR (issue 108270043 byphilehol...@googlemail.com)

Documentation/notation/ancient.itely:2651: an indication of how the initial rests and note of the original version notes https://codereview.appspot.com/108270043/ No - it should be note. A standard incipit has all the rests leading to the first note, but just the first note alone.

Re: Have git SHA1 ID's changed in the last 5 years?

Okay, so I'm not crazy. I happened to keep an old repo from four years ago, and as you can see from the attached image, the two histories are not the same, and neither are the commit SHA1 IDs... How did this happen, and could it happen again? could you track down the first divergence

Re: Have git SHA1 ID's changed in the last 5 years?

2014-07-27 9:54 GMT+02:00 David Kastrup d...@gnu.org: Benkő Pál benko@gmail.com writes: Okay, so I'm not crazy. I happened to keep an old repo from four years ago, and as you can see from the attached image, the two histories are not the same, and neither are the commit SHA1 IDs... How

Re: Re: Issue 3890 in lilypond: Patch: Add dodecaphonic-first accidental style

2014-04-01 18:05 GMT+02:00 Urs Liska lilyli...@googlemail.com: Would please someone push the attached patches? pushed to staging as $ git log --oneline -2 b03be2f Issue 3890: Add doc for dodecaphonic-first accidental style deb20df Issue 3890: Add dodecaphonic-first accidental style

Re: Submitted a patch and it was added to the wrong rietveld issue

hi Paul, I submitted a patch and I am sorry to say that somehow it was added to the wrong issue: https://codereview.appspot.com/54050043 And a new issue (with the wrong title and content) was created in the google code tracker: https://code.google.com/p/lilypond/issues/detail?id=3883 It

Re: access to all remote branches

hi, I've had to reinstall LilyDev, and I'm no longer able to see all of the remote branches. When I run git branch -a I simply see: dev/local_working master remotes/origin/master you may have cloned only the master branch. try git fetch --all p

Re: CG: basic cleanup (issue 46120044)

2014/1/1 k-ohara5...@oco.net: Janek, when people start with `git clone` do they also get a staging branch that tracks the one on savannah? I think we still want at least one mention of how to set up a 'staging' branch to track origin/staging, git checkout --track -b staging origin/staging

Re: splitting file movement and whitespace-only changes into separate commits (issue 42330044)

if requested, I can either update dev/janek/metafont-cleanup or push as a new branch. Please do so! pushed as dev/benko/metafont-cleanup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Metafont code cleanup (issue 38530043)

hi Janek, 2013/12/11 Janek Warchoł janek.lilyp...@gmail.com: 2013/12/10 benko@gmail.com: However, if you don't mind, i'd prefer to leave it as is - i have _already_ spent about 4 hours cleaning up and rebasing commits to make them somewhat ordered for review, and i'm quite tired. I do

Re: Repeats starting and ending in mid-bar?

I'm occasionally repondering the barline |: :| issue and I want to know if anybody's music typesetting theory text or private music library has examples of repeats starting and/or ending in mid-bar. I seem to remember that there is some weakened double bar in use for that, something like ||:

Re: Black mensural notehead bug

Well, I don't know without further digging. However, there is a notation style called black mensural, and it seems only logical that Lilypond should support this using the available glyphs. sorry for the confusion. I introduced black note heads to support coloratio in white mensural

Re: how to build lilypond in debug mode?

pass the debug flags to the configure call. CXXFLAGS=-ggdb3 ./configure possible args you can also build a profiling build throught the same mechanism. The --with-debug or like switches that a configure call supports should refer to extra debugging checks in the code switched on. even

Re: upgrade to c++11

hi David, The probability that some envelope-finding code dropped into LilyPond by a typical LilyPond contributor is close to the quality of somebody who wrote a Phd thesis focused around the topic is slim. I did write a Phd thesis not very far from that. the time I can spend on LilyPond is

Re: Ignoring note value when spacing notes and rests

2013/6/15 Phil Holmes em...@philholmes.net: I'm setting a piece of late 16th century music (it's in Musica Transalpina), and at this time notes and rests tended to occupy a space determined by their fitment on the page, rather than their note value. I've read the section of the NR on

Re: Bar lines on single staff line system

intended change by 6f4893fa86378aa4a637eedbde5efc4680efa5bf see http://code.google.com/p/lilypond/issues/detail?id=2762 2013/4/5 Phil Holmes em...@philholmes.net: Between 2.17.0 and 2.17.1 the behaviour of single staffline systems changed. The earlier behaviour had no barline; the latter has

Re: [gmane.comp.gnu.lilypond.general] Re: Transposing instruments

all, 2013/1/30 David Kastrup d...@gnu.org: Ok, sorry for the bottom quote, but I'd like to get the context into the developer list. Shouldn't we have a command \transposing f { ... } (better naming suggestions welcome) that does transposition and Midi correction in lockstep? Is anybody

Re: [gmane.comp.gnu.lilypond.general] Re: Transposing instruments

2013/1/30 David Kastrup d...@gnu.org: Benkő Pál benko@gmail.com writes: all, 2013/1/30 David Kastrup d...@gnu.org: Ok, sorry for the bottom quote, but I'd like to get the context into the developer list. Shouldn't we have a command \transposing f { ... } (better naming

Re: Make documentation reflect presence of \tuplet (issue 7220052)

2013/1/30 d...@gnu.org: On 2013/01/29 17:25:19, Keith wrote: https://codereview.appspot.com/7220052/diff/4001/Documentation/learning/common-notation.itely#newcode506 Documentation/learning/common-notation.itely:506: ratio of the number of notes to play in relation to the nominal ...

Re: vertical positioning of full measure rests

hi all, Hello, it seems, that the vertical positioning works great for rests (r) but bad for full measure rests (R). Please have a look on http://thread.gmane.org/gmane.comp.gnu.lilypond.general/78355 I'm working on this. p ___ lilypond-devel

Re: fix handling of grace notes to shorten preceding tied notes correctly (issue 7108043)

2013/1/15 k-ohara5...@oco.net: https://codereview.appspot.com/7108043/diff/1/lily/include/audio-item.hh#newcode90 lily/include/audio-item.hh:90: virtual string to_string () const; It seems fine to have the debug-output helper to_string(), but why make it a virtual member function? Unless the

Re: 2.17.10 regtests

2013/1/14 Phil Holmes em...@philholmes.net: Surely the bracket should not be visible by default if you're setting mensural notation? Should not the \remove Ligature_bracket_engraver be removed automatically for mensural notation? it is removed in MensuralVoice, but hey, this is just a

Re: 2.17.10 regtests

all, 2013/1/13 Phil Holmes em...@philholmes.net: I've just whiled away a happy few minutes looking at the regtests. There are quite a number of changes, I think mostly based on Mike's latest horizontal skylining. There are some that concern me in particular: ambitus-with-ligature.ly: I

Re: How should tupletSpannerDuration actually work?

2013/1/12 Phil Holmes m...@philholmes.net: - Original Message - From: David Kastrup d...@gnu.org To: lilypond-devel@gnu.org Sent: Saturday, January 12, 2013 10:25 AM Subject: How should tupletSpannerDuration actually work? I have a hard time considering the output of

Re: Issue 2966 - Patch-push

hi, someone up to push it for me? http://code.google.com/p/lilypond/issues/detail?id=2966 https://codereview.appspot.com/6850073/ happily; could you send me the patch(es)? p ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: What happened to staging?

2012/10/30 David Kastrup d...@gnu.org: Marc Hohl m...@hohlart.de 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

Re: fix representation switching from line-position to staff-space (issue 6778050)

2012/10/30 David Kastrup d...@gnu.org: Benkő Pál benko@gmail.com writes: 2012/10/27 d...@gnu.org: On 2012/10/27 20:34:35, benko.pal wrote: I want staves with line-positions like (-2 0 2 4) work. Why would somebody specify (-2 0 2 4) with the expectation that the results should

Re: fix representation switching from line-position to staff-space (issue 6778050)

2012/10/27 d...@gnu.org: On 2012/10/27 20:34:35, benko.pal wrote: I want staves with line-positions like (-2 0 2 4) work. Why would somebody specify (-2 0 2 4) with the expectation that the results should be identical to (-3 -1 1 3)? Why would he not specify (-3 -1 1 3) in the first place

Re: prevent collision of ligatures and next note (issue 6740046)

in C++ there should be a good reason to pass complex structures like std::vectorGrob_info by value, not by reference to const; in this case there's no such reason, pass-by-reference works perfectly. Ah, so this is a by-the-way fix. Can it be in a separate commit, please? it is; I meant to

Re: prevent collision of ligatures and next note (issue 6740046)

Ah, so this is a by-the-way fix. Can it be in a separate commit, please? it is; I meant to note it but forgot, sorry. is there interest in pushing such multi-commit patches to some dev branch? If there is, people should ask. Substructuring an issue into several logical commits is good

Re: Fix extra spacing in Kievan notation (issue 6684051)

The presence of a long syllable in the lyrics makes the left_col-extent larger than spring.min_distance(). Manipulating the SpacingSpanner properties has no effect -- the extraneous space is still there. long syllables are a general problem, see Janek's GSoC list, it shouldn't be solved this

Re: Naming _another_ lacking puzzle piece

2012/10/13 David Kastrup d...@gnu.org: In ly/music-functions-init.ly I see code like the following: crossStaff = #(define-music-function (parser location notes) (ly:music?) (_i Create cross-staff stems) #{ \override Stem #'cross-staff = #cross-staff-connect \override Flag #'style

Re: [GLISS] turning strings to symbols

2012/10/12 David Kastrup d...@gnu.org: Trevor Daniels t.dani...@treda.co.uk writes: I'm less concerned than Werner about the inconsistency of the tweak syntax. The context needs to be specified only rarely, and it is a small price to pay for the enormous gain. Well, strictly speaking we are

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 Francisco Vila paconet@gmail.com: When I learned how to read music, triplets were taught to me as always shrinking groups and you see a 3 but there is an implicit 2 so we have 3:2. Only the numerator is printed by convention. Thus, if you write \times 2/3 { b16 b b b b b }

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 David Kastrup d...@gnu.org: The concept used for printing/grouping tuplets is different than the concept used for scaling the time. That's what makes \times such a confusing interface. The pure scaling alone is available as \scaleDurations. I have no beef with it using 2/3 as

Re: [proposal] easy triplets and tuplets - Draft 3

2012/10/9 David Kastrup d...@gnu.org: Benkő Pál benko@gmail.com writes: 2012/10/9 David Kastrup d...@gnu.org: I don't really think that people consider \times and \scaleDurations as closely related (and their naming choice is also totally different), so I don't think

Re: [proposal] easy triplets and tuplets - Draft 2

The normal setting is to have four notes in a full 3/4 bar. That would be \times 3/4 rather than \times 6/4, right? Exactly. four quarters, yes; four eigths are 6/4, and that's what I've seen. regarding the \tuplet integer shorthand: I would hate \tuplet n meaning not \tuplet n/1 but

Re: [talk] easy tuplets

Well, music argument after left-out optional argument at the current point of time means closed music. It is likely a safe bet that we rarely need a single note for a tuplet, so it is not much of a problem, and I am chugging away at getting the closed music thing scrapped, but that's still a

Re: Feature request

2012/9/25 David Kastrup d...@gnu.org: But if I remember correctly, beam subdivision is a multi-level problem, not just two-level. yes, see the attachment to http://code.google.com/p/lilypond/issues/detail?id=2361 ___ lilypond-devel mailing list

Re: Doc: Improve documentation of \glissando. (issue 6529043)

This example shows a beam extending from a stem to the final note of the glissando. Is this correct, or would it be better to suppress the beam? I made some Bartók and Xenakis scans, see https://docs.google.com/folder/d/0B7AjGy5hUKtAeWtkdHdfN0l4bm8/edit such beams can be seen in 0162.jpeg and

Re: [GLISS] non-timed or non-musical events z y

2012/9/24 Keith OHara k-ohara5...@oco.net: Graham Percival graham at percival-music.ca writes: Although mathematicians and programmers are quite comfortable with contains with 0 items inside them, this is not a particularly intuitive concept (just look at the concept of zero in the history

Re: [GLISS] non-timed or non-musical events z y

2012/9/24 David Kastrup d...@gnu.org: Benkő Pál benko@gmail.com writes: does anybody has a similar way (not a function) of marking just the first note with a cautionary accidental? This is probably somewhat tongue-in-cheek, but try { \key fis\major dis4 \once\accidentalStyle

line_count issues

hi David, I saw you marked line_count related issues for backport. is that my task, yours or common? what should or can I do? at the moment there's one line_count related issue I know and want to work on: multimeasure rests in nonstandard staves, see

Re: line_count issues

2012/9/18 David Kastrup d...@gnu.org: Benkő Pál benko@gmail.com writes: hi David, I saw you marked line_count related issues for backport. is that my task, yours or common? Mine. what should or can I do? I was actually planning to contact you in private about this. I am

  1   2   3   >