Re: Visual Index Manual where?

On 22.04.24 15:26, Werner LEMBERG wrote: I was reading through the Changes document for 2.25.15 and wanted to look at the Visual Index, which it says is now included as a manual. However, I couldn’t find it on the overview page for the manuals nor as appendix to any manual that it would fit in.

Visual Index Manual where?

Hi everyone, I was reading through the Changes document for 2.25.15 and wanted to look at the Visual Index, which it says is now included as a manual. However, I couldn’t find it on the overview page for the manuals nor as appendix to any manual that it would fit in. Am I missing something?

Re: Website Indices

On 23.03.24 03:20, Christopher Heckman wrote: The Lilypond website has two indices: a command index, and a (generic) index. From the descriptions, it seems like the generic index includes everything in the command index and then some. Would it be possible to combine them into one index? When I

Re: LilyPond Visual Index for forthcoming version 2.26

Hi Werner, the Index looks great, thanks a lot for your work on this! I have two minor points of feedback on the second page: There should IMO be some padding between the boxed (magenta) headings, and they should always be in the order *Score, *Staff, *Voice, *Lyrics. I hope this is a good

General appreciation

Hello development team, I can’t exactly see where my life is going and whether I might be able to contribute more to the project in the future. In the meantime, I want to say that I’m really happy to look at the progress that is happening and grateful for all of you that make it possible.

[WISH] ‘smart’ punctuation for Lyrics

Dear devs, when I use tags to differentiate lyrics in different parts, I often have to complicate the source file and duplicate code in order because of different punctuation that results from different repetitions and/or elisions. Very much boiled down: \lyricmode {   yes   \tag alto,bass

Issue with download link

Hello everyone, On 24/07/2022 19:44, Jonas Hahnfeld via LilyPond user discussion wrote: Please refer to the Installing section in the Learning Manual for instructions how to set up the provided binaries: https://lilypond.org/doc/v2.23/Documentation/learning/installing This link leads to a

Re: Slanted Beams thickness

Hi everyone, On 25/03/2022 01:44, Valentin Petzel wrote: Hello, Lilypond handles slanted Beams in a geometrically weird way, that is, the thickness is not measured as the shortest distance between the opposing sides of the boundary, but as vertical distance. This results in Beams getting

Alteration value in localAlterations can now be 'tied?

Hello everybody, I hope it is appropriate for me to post this here, I haven’t closely followed development for a long time. I have a custom accidental style following 18th century usage (example attached) which fails in 2.23.6 because the internals have changed. Namely, for the sixth note

Re: LilyPond 2.22.2 released

On 22/02/2022 14:07, Phil Holmes wrote: We are proud to announce the release of GNU LilyPond 2.22.2 on 2-22-22 (i.e. February the 22nd, 2022). Fabulous ;) Thanks to everyone involved!

Re: GS version conflict in packaged 2.20 and 2.21

On 19.04.20 20:27, Werner LEMBERG wrote: Do we have a warning somewhere in the LilyPond documentation that people must not use the binary directly but the wrapper? Simon, have you tried to find something in the docs? If yes, what keywords were you looking for? I have no idea from where I

Re: GS version conflict in packaged 2.20 and 2.21

On 19.04.20 16:56, Valentin Villenave wrote: Yes, a French user also had some gs issues that I think may be related to yours: https://lists.gnu.org/archive/html/lilypond-user-fr/2020-04/msg00164.html That seems to be the same usage issue—see my parallel reply or the -user thread. Best,

Re: GS version conflict in packaged 2.20 and 2.21

On 18.04.20 01:46, Simon Albrecht wrote: Hello everyone, it appears from this exchange <https://lists.gnu.org/archive/html/lilypond-user/2020-04/msg00294.html> that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known

GS version conflict in packaged 2.20 and 2.21

Hello everyone, it appears from this exchange that the packaged versions of 2.20.0 and 2.21.0 contain a mixture of GS 9.21 and 9.26. Is that correct/expected/a known issue? Best, Simon

Re: Re: An exciting new release… of Sibelius!!!

Let's be honest, they really had to get their stuff together to keep any ground all against Dorico. Best, Simon > On 27.03.2020 - 15:26, Shane Brandes wrote: > > > They are really on the ball on that one. > > > -Shane > > > On Fri, Mar 27, 2020 at 10:09 AM Valentin Villenave > wrote: >

2.20 announcements/publicity

Hello everybody, I’ve been more or less lurking on the lists for quite a while now and I’m sorry for not contributing myself these days. I’m thrilled about the boost to development efforts that could be seen and immensely grateful for all of you keeping up the good work, especially completing

Re: vim script for transpositions

Hello, thanks for your interest in sharing. LilyPond’s code base doesn’t contain any tools like this. There are of course LilyPond’s built-in music functions for transposing, but that’s a slightly different use case. What’s more comparable are the tools for manipulating input code

Re: What is holding up 2.20 release?

I would like to give whatever small contribution I can make to this without knowing so much on the technical levels; please do tell me whether I say below is considered helpful. On 18.11.19 18:10, Jonas Hahnfeld wrote: 965a607096 Fix #1367: NoteNames context in any language not sure, has

Re: Appearance of S-curves

Hi, I find the second one with crossing beziers mich more pleasant, but I'm sure the question is easily settled by looking at any good hand-engraved example (I'm travelling right now and don't have any at hand, sorry). Best, Simon > On 26.04.2019 - 13:10, Thomas Morley wrote: > > > Hi, > >

Re: melismaBusyProperties: scheme syntax vs. lily syntax

On 16.07.2018 02:51, Carl Sorensen wrote: On 7/15/18, 3:29 PM, "lilypond-devel on behalf of David Kastrup" wrote: Simon Albrecht writes: > Hello everybody, > > I just noticed that it’s possible to use the LilyPond symbol list/key > li

melismaBusyProperties: scheme syntax vs. lily syntax

Hello everybody, I just noticed that it’s possible to use the LilyPond symbol list/key list syntax when setting melismaBusyProperties. However, the doc string reads "A list of properties (symbols) to determine whether a melisma is playing. Setting this property will influence how lyrics are

Re: No hint on outdated translated docs

On 30.06.2018 21:33, Federico Bruni wrote: Hi Simon There's already an open issue about this request. Opened by me, IIRC. I also suggested to move the language selection from the footer to the header of each page. In another issue.. It's all in the tracker. We miss someone willing to work

No hint on outdated translated docs

Hello everybody, Bernhard Kleine has pointed out that while it has been problematic for years already to use e.g. the German version of the docs, because the translation hasn’t been updated in a long time and many new features are missing, the German docs do not make any hint of that

Re: fix CueEndClef with parenthesized ClefModifier (issue 353720043 by lilyp...@maltemeyn.de)

On 20.06.2018 21:04, lilyp...@maltemeyn.de wrote: https://codereview.appspot.com/353720043/diff/1/input/regression/cue-clef-transposition-optional.ly#newcode1 input/regression/cue-clef-transposition-optional.ly:1: \version "2.21.0" When should the version number be updated? Only if new

Re: Skylines and certain grob properties (rotation, extra-offset)

On 20.04.2018 15:43, Torsten Hämmerle wrote: What do you think about making skylines consider the grob properties rotation and extra-offset? (1) keep everything as it is (2) skylines should reflect both grob rotation and grob extra-offset (3) skylines should reflect grob rotation only (4)

Re: Issue 3128: add Haydn-style turns to Feta (issue 340660043 by lilyp...@maltemeyn.de)

On 08.04.2018 19:08, nine.fierce.ball...@gmail.com wrote: Is there a performance difference between these two scripts?  I read quickly through the thread referenced in the ticket, but I couldn't find the answer. I’m not sure what exactly the difference in performing is, but that’s not for us

Re: Problem with showing git status in bash

On 01.03.2018 20:59, Joram wrote: The git-part you want to add is just the '$(__git_ps1)' part. So you can use the original $PS1 and add that part if you don't want other changes. Thanks, that’s what I did, ending up with this monster: export PS1="\[\e]0;\u@\h:

Problem with showing git status in bash

Hello everybody, I just applied the suggestion from the CG to add export PS1="\u@\h \w\$(__git_ps1)$ " export GIT_PS1_SHOWDIRTYSTATE=true export GIT_PS1_SHOWUNTRACKEDFILES=true export GIT_PS1_SHOWUPSTREAM=auto to ~/.bashrc in order to show the status of a git repository in the command prompt.

Re: Web/Easier editing update

On 28.02.2018 19:05, Kieren MacMillan wrote: No commas at all: “Frescobaldi is a lightweight yet powerful music and text…” Thanks! Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Replacement for gmane to post bug reports

Hi, it seems that the functionality to report bugs without subscribing to the bug list is missed. (Gianmaria Lari just contacted me privately, and I told him that it’s possible to subscribe to the list and turn off mail delivery – probably one solution.) Is there anything similar to the

Re: Web/Easier editing update

On 28.02.2018 19:03, Kieren MacMillan wrote: Frescobaldi is a lightweight, yet powerful, music and text editor with many features added and enhanced particularly for LilyPond. Major features include point-and-click links between the code and music views, detailed score wizards, built in

Web/Easier editing update

Hi everybody, I noticed slight glitches when having a look at the ‘Easier editing’ page on the website. This is the text about Frescobaldi: > Frescobaldi is a lightweight, yet powerful, music and text editor with many features added and enhanced particularly for LilyPond. Major features

Re: Chromatic solfedge

On 14.02.2018 23:01, Joseph Austin wrote: Is it feasible to use the \language feature or some other facility to enter music with solfedge abbreviations for note-names, e.g. " d r m f s l t " (for Do Re Mi Fa Sol La Ti) instead of " c d e f g a b? It should be straightforward to define your

Re: Issue 5272: Add \depart (issue 337520043 by nine.fierce.ball...@gmail.com)

On 07.02.2018 10:37, Torsten Hämmerle wrote: So why not using something like *\repeatMark*, *\markRepeat* or *\markRepetition*, ...? Seen that way, even \repeatMark "Fine" feels natural to me, because - like an ordinary RehearsalMark, or a MetronomeMark, it's just a new kind of Mark, which is,

Re: Issue 5272: Add \depart (issue 337520043 by nine.fierce.ball...@gmail.com)

Brainstorming (NB, only brainstorming) on the name: Normal rehearsal marks refer to the beginning of a section, while these refer to the end of a section, so an input command might be \endMark "D.S.". You still have to complete it to ‘end-of-section mark’ in your head, but \depart seems far

Re: access to the issue tracker

On 06.12.2017 14:31, Phil Holmes wrote: - Original Message - From: "Семен Миргородский" To: Sent: Wednesday, December 06, 2017 5:23 AM Subject: access to the issue tracker Hi! My name is Semyon and I'm trying to translate documentation to

Octave check warning

Hello, here’s a kind of pet peeve of mine: With a warning like warning: octave check failed; expected "a", found: "a," I always have to look twice what the difference between the two is. It might be easier to read as warning: octave check failed; expected "a" and found "a," (or: ‘but

Re: Terminology of baseMoment, beats, groups

On 11.11.2017 12:30, David Kastrup wrote: I have a hard time seeing a "beat" as something that can have different lengths. Musical notation isn’t well-defined in a mathematical or programming sense, so there are no such strict rules as all beats of a measure having to be the same length. If

Re: Fwd: \tempo feature requests

On 10.10.2017 13:57, Malte Meyn wrote: I made a patch for this (only snippet 1008, not yet 574). Because that’s not a bugfix but an extension to LilyPond, should this first be discussed on this list or on the issue tracker? Or should I upload it right now to Rietveld and discuss then?

Re: How to locate all layout-property values for a particular LayoutObject in the source files?

On 24.09.2017 14:30, James wrote: Where would I go to see the 'complete list' of all possible NoteHead.style values – the description of the style property isn’t helpful (since it summarises the use of that

Re: New repeat type

On 30.08.2017 23:42, Dan Eble wrote: The disease is that Lilypond needs to see lyrics for multiple stanzas encoded as simultaneous music in order to set them one below another, and the right action is to cure that I find the metaphor slightly too strong, since I think the ‘cure’ is merely

Re: Should we have a from-barline property in analogy to to-barline ?

On 24.07.2017 15:30, David Kastrup wrote: Making a bar line an event would then place per-chord articulation marks of the following note on the bar line. You mean { c1 \bar "||" \fermata \bar "|." \fermata } would place both fermatas on the barlines? I don't think that this idea

Re: Should we have a from-barline property in analogy to to-barline ?

On 24.07.2017 13:58, David Kastrup wrote: Seems like an obvious addition. Would make stuff (like slurs, hairpins and so on) starting at the bar move backwards to the bar line. Probably also useful for non-spanners like a \fermata ? I have difficulty imagining use cases. Is to-barline really

Re: Any objections to branching off a stable branch for 2.20?

On 20.07.2017 00:45, Dan Eble wrote: On Jul 19, 2017, at 15:19, David Kastrup wrote: Paul > writes: It's usually `a = b` or `\a b` but not `\a = b` or `\a b = c`. You can only use markup functions when refered to in markup

Re: Some questions related to score video generation

On 07.07.2017 15:00, Knut Petersen wrote: I Fyrreskoven. Excellent! I love it. Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: PDF landscape issue

On 01.07.2017 18:44, Francisco Vila wrote: Hello, I'd like to know if something has changed recently about the way LilyPond creates landscape documents. In 2.19.58, a landscape document looks right in Evince and in Frescobaldi music PDF preview. In 2.19.62, the same document is rotated 90º

Re: True Hand-engraved Dashed Slurs

On 27.06.2017 22:15, tisimst wrote: How often are these split slurs used? I personally have never had a reason to use them, but I guess they must be used somewhere. They’re used in scientific editions e.g. if a slur is begun before the line break, but not continued after in the source. Any

Re: connecting lines (spanners?) between arbitrary grobs/locations

On 14.06.2017 22:53, Kieren MacMillan wrote: Here's a 71KB version. I can see it displayed below the footer in Thunderbird, though not as an ordinary attachment and it’s not a Schenker graph, but 7 staves of ordinary notation plus some annotations… Best, Simon

Re: connecting lines (spanners?) between arbitrary grobs/locations

On 14.06.2017 22:44, Kieren MacMillan wrote: Hi Simon, On 14.06.2017 19:51, Kieren MacMillan wrote: I've attached a screenshot of a Schenker graph That seems to have gone amiss… That's the second time I've posted a screenshot, and the second time it didn't make it to the list. Is there

Re: connecting lines (spanners?) between arbitrary grobs/locations

On 14.06.2017 19:51, Kieren MacMillan wrote: I've attached a screenshot of a Schenker graph That seems to have gone amiss… Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: VirtualBox error

On 07.06.2017 01:27, Kieren MacMillan wrote: Hello all, I'm trying to set up LilyDev. Running Mac OS X 10.12.5 on an iMac with 16GB RAM. 1. Downloaded the most recent VirtualBox — no problem. 2. Installed VirtualBox — no problem. 3. Launched VirtualBox — no problem. 4. Created my LilyDev

Re: ‘Know which branch we’re on’ on Ubuntu 16

On 04.06.2017 19:02, David Kastrup wrote: Simon Albrecht <simon.albre...@mail.de> writes: Hello, finally I’ve managed to get Ubuntu 16.04 working, and copied all of my previous home directory including .bashrc. However, the ‘export PS1’ trick suggested in <http://lilypond.org/

‘Know which branch we’re on’ on Ubuntu 16

Hello, finally I’ve managed to get Ubuntu 16.04 working, and copied all of my previous home directory including .bashrc. However, the ‘export PS1’ trick suggested in with the following line in .bashrc:

Re: Paper rotated in 2.19.60

Am 10.05.2017 um 10:56 schrieb Andrew Bernard: Ok, so now I see from ancient times that NR Section 4.1.2 distinguishes between: #(set-default-paper-size "a4" 'landscape) and #(set-default-paper-size "a4landscape") And yet, unaware of this distinction, I have been using the first form for a

Re: Superfluous # signs

Am 09.05.2017 um 17:22 schrieb Phil Holmes: For example, in http://lilypond.org/doc/v2.19/Documentation/notation/using-midi-instruments we have: \set Staff.midiInstrument = #"glockenspiel" Is the # prior to the quote marks now not needed and so this (and a number of others) could be tidied up?

Re: Allow 'staff-padding to work with MeasureCounter (issue 312580043 by david.nales...@gmail.com)

I’m not sure if a doc snippet is really necessary. Using staff-padding is explained in and , so maybe a verbal

Re: NR: Document \remove "Keep_alive_together_engraver" (issue 318580043 by g...@ursliska.de)

On 17.02.2017 16:29, Urs Liska wrote: Am 17.02.2017 um 09:21 schrieb David Kastrup: Urs Liska writes: Am 17.02.2017 um 08:34 schrieb d...@gnu.org: Ok, I'll bite. What kind of piano music is written like \score { \new PianoStaff << \new Staff = "up" <<

Re: NR: Document \remove "Keep_alive_together_engraver" (issue 318580043 by g...@ursliska.de)

On 17.02.2017 09:21, David Kastrup wrote: PianoStaff is explicitly for the case where you want staves to be frenched together. Its name does not mean "Piano inside" but rather "Use frenching conventions common in piano music". And you actually would still not want it to french out multiple

Re: Question about '\new Staff =' command

On 02.02.2017 21:25, SoundsFromSound wrote: Urs Liska wrote You can use the explicit staff name to access the context (or compare to some arbitrary value), and it's for example used in the \change Staff = "upper" command. Can you give an example of a simple score where you create a staff and

Re: Issue 3830: Document \offset command (issue 319150043 by david.nales...@gmail.com)

One typo did I spot :-) https://codereview.appspot.com/319150043/diff/80001/Documentation/notation/changing-defaults.itely File Documentation/notation/changing-defaults.itely (right): https://codereview.appspot.com/319150043/diff/80001/Documentation/notation/changing-defaults.itely#newcode2777

Re: GSoC project ideas

On 23.01.2017 22:47, Urs Liska wrote: So while it's perfectly possible to put OLL projects on the list and to apply for them (or others not listed there) in case of doubt projects working on LilyPond itself might be the preference of the developer community. […] What I would see as a better

Re: Issue 3830: Document \offset command (issue 319150043 by david.nales...@gmail.com)

LGTM. https://codereview.appspot.com/319150043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Back in the Pond

On 19.01.2017 14:01, David Kastrup wrote: it is an open question whether it makes sense to admit it into 2.20.0 (or was the first version 2.20.1) We had 2.18.0 and 2.18.2. Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: Is Anyone Working on a Better Tablature Algorithm?

On 16.01.2017 04:35, christopher-heckman wrote: \chTab { \new TabStaff { How about having \chTab create a TabStaff and TabVoice automatically? Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: How to create a Midi File out of Lilypond for Multi-voice Staff

On 13.01.2017 14:07, Mungo1981 wrote: Can I build a Multi-voice Midi File. Yes, you can. Please ask back on the lilypond-u...@gnu.org mailing list – this list is (as the name suggests) about development of LilyPond, not about usage. You might also want to read

Re: PATCHES - Countdown for January 8th

rom 0b6a08f55cf76682634b21b039004ebe9ba02eb4 Mon Sep 17 00:00:00 2001 From: Simon Albrecht <sinc...@my.mail.de> Date: Mon, 9 Jan 2017 03:13:29 +0100 Subject: [PATCH] NR 1.2.1.d: Split note more appropriately (issue 5027) Durations which have to be written with ties should be split at major sub

Re: PATCHES - Countdown for January 8th

On 09.01.2017 01:05, Thomas Morley wrote: I'm not sure what I should do. Push the counted down patch or do you want to have your new patch uploaded or ...? Well, James set it to Patch:push, so push it, unless you think the review wasn’t sound and it should get another one. OTOH, regardless

Re: NR 1.2.1.d: Split note correctly (issue 319940043 by thomasmorle...@gmail.com)

On 08.01.2017 17:48, thomasmorle...@gmail.com wrote: Not sure you can upload to _this_ Rietveld issue. Probably best you try and if not a new will be opened (and I close this one). Since the review is finished (James set it to Patch:push) just close it – that’s what I couldn’t do. Best,

Re: NR 1.2.1.d: Split note correctly (issue 319940043 by thomasmorle...@gmail.com)

On 04.01.2017 00:14, thomasmorle...@gmail.com wrote: (I shepherd this for Simon, as long as he has problems with his google account) For the record: Google prevented the login despite that I accessed the internet with the same machine as always, and only because I did so through a different

Re: PATCHES - Countdown for January 8th

On 08.01.2017 16:23, James wrote: 5027 NR 1.2.1.d: Split note correctly - Simon Albrecht https://sourceforge.net/p/testlilyissues/issues/5027 http://codereview.appspot.com/319940043 I do not think the Hindemith quote brought up by Hans Aberg is representative of common notational convention

Re: 5027: NR example with bad engraving practice

On 05.01.2017 23:42, Hans Aikema wrote: On 5 Jan 2017, at 23:16, Simon Albrecht <simon.albre...@mail.de> wrote: On 04.01.2017 15:01, Hans Åberg wrote: This is just a quirk of the 4/4 [meter], also mentioned in Hindemith, "Elementary Training", p. 30. In other words, the note

Re: 5027: NR example with bad engraving practice

On 04.01.2017 15:01, Hans Åberg wrote: This is just a quirk of the 4/4 [meter], also mentioned in Hindemith, "Elementary Training", p. 30. In other words, the note should not cross the 2nd and 4th metric accents, but it can cross the [3rd]. I’ve never heard of that and would assume it is a

Re: 5027: NR example with bad engraving practice

On 04.01.2017 15:01, Hans Åberg wrote: This is just a quirk of the 4/4 measure, also mentioned in Hindemith, "Elementary Training", p. 30. In other words, the note should not cross the 2nd and 4th metric accents, but it can cross the 2nd. You mean ‘can cross the 3rd’?

pdf size and point-and-click

On 04.01.2017 13:39, Thomas Morley wrote: point-and-click is disabled in the ly-file otherwise the size of the resulting pdf explodes from 60.4KB to 1.2MB. Why?? The magnitude seems extreme, but the sheer data of all the textedit:// links to each event usually makes the files a lot larger.

Re: NR 1.2.1.d: Split note correctly (issue 319940043 by thomasmorle...@gmail.com)

On 04.01.2017 00:14, thomasmorle...@gmail.com wrote: (I shepherd this for Simon, as long as he has problems with his google account) Thanks. ___ lilypond-devel mailing list lilypond-devel@gnu.org

5027: NR example with bad engraving practice

7 00:00:00 2001 From: Simon Albrecht <sinc...@my.mail.de> Date: Tue, 3 Jan 2017 23:41:00 +0100 Subject: [PATCH] NR 1.2.1.d: Split note correctly In 4/4 time, a note crossing the middle of the bar should be split at the middle of the bar. The current example displays bad engraving practic

Re: Arrow-glyphs in Feta

On 29.12.2016 22:04, James wrote: Is it simply for the same reason any font has a separate character that is a 'rotated' version of its counterpart? e.g. '<' and '>' or '/' and '\' Why*wouldn't* you make separate font 'objects' for fundamental glyphs? Those have semantically different,

Re: Free alternatives to Rietveld?

Thanks for the heads-up on previous discussions, now I know more about the pitfalls. Also I see now that the ultimate free alternative would likely be the one Jan N. brought up in that old discussion, namely exchanging patches via e-mail only. Which makes sense with git’s design, however the

Arrow-glyphs in Feta (was: \arrow markup command)

On 23.12.2016 22:34, Simon Albrecht wrote: Why does the Feta font have one glyph for each of the 4 directions in which an arrow head generated with \arrow-head can point? Why not simply rotate one glyph in the first place? (I’m sure the Metafont code does just that, though it would strike me

Re: Free alternatives to Rietveld?

On 27.12.2016 14:09, Urs Liska wrote: While we're at it: is there really no tool that integrates with Git directly? I find it pretty inconvenient and partly unreliable that the author is responsible himself that what is pushed actually is what has been reviewed. Well, I had a brief look at

Free alternatives to Rietveld?

Hello everybody, just now I tried to login with Google in order to close my two recent Rietveld reviews. However, Google decided that despite entering a verification code from e-mail it couldn’t confirm me being authorised to login. So I’m currently out. Maybe they want to force me to give a

Re: \arrow markup command

Hello again, I created a better preview image and on the way noticed that a small adjustment is necessary, so that the line doesn’t obstruct the finer tip of the filled arrow head. Best, Simon arrow.pdf Description: Adobe PDF document \version "2.19.53" \header { tagline = ##f } \paper

Re: [PATCH [uploaded to Rietveld]] Automatic lyric extenders

On 23.12.2016 22:36, Alexander Kobel wrote: The corresponding issue can be found at https://sourceforge.net/p/testlilyissues/issues/5018/ …which I took the liberty to merge with . Thanks for the work and happy holidays as well! Best,

\arrow markup command

Hello, I have just been annoyed by the fact that it takes four commands (\combine, \arrow-head, \override, and \draw-line) to draw an acceptable arrow-head (\override is to match the thickness of the line to the Feta glyph), so I proceeded to code an \arrow markup command simplifying the use.

Re: Delete new LSR-snippet?

On 23.12.2016 12:42, Thomas Morley wrote: with http://lsr.di.unimi.it/LSR/Item?u=1=1049 a new snippet arrived. Though, it only demonstrates how to use 'extra-offset, imho. And very poorly – how the staff lines resurface after the text script… This is definitely not showcase-able and I agree

Re: Two small amendments to Doc/web/community.itexi (issue 319880043 by simon.albre...@mail.de)

On 22.12.2016 23:21, gra...@percival-music.ca wrote: https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi File Documentation/web/community.itexi (right): https://codereview.appspot.com/319880043/diff/1/Documentation/web/community.itexi#newcode434

Re: [PATCH] Automatic lyric extenders

On 22.12.2016 02:17, Thomas Morley wrote: 2016-12-22 1:33 GMT+01:00 Knut Petersen: Hi everybody! Attached find a new version of the patch. Please test. Read the updated manuals. Feel free to provide corrections and translations! cu, Knut Hi Knut, how about

Re: music function to be included somewhere in scm/*

On 17.12.2016 00:23, Trevor Daniels wrote: How about "collapse-length", which would be analogous to "collapse-height"? +1 Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: music function to be included somewhere in scm/*

On 16.12.2016 08:30, Marc Hohl wrote: Am 16.12.2016 um 02:09 schrieb Alexander Kobel: Hi all. [...] What about hide-below-length or hide-if-shorter-than? minimum-visibility? We’re getting closer… I think ‘threshold’ describes the functionality well; maybe visibility-threshold?

Re: music function to be included somewhere in scm/*

On 15.12.2016 17:45, Alexander Kobel wrote: (1) You can put the lyrics to all voices, as extenders are only printed on melismata (unless explicitly enforced). (2) You don't have to add __ in your lyrics anymore - it's done automagically (unless explicitly disabled). (3) minimum-length (or some

Re: music function to be included somewhere in scm/*

On 15.12.2016 17:17, Francisco Vila wrote: I think lyrics extenders are meant only for the last syllable of a word. Of course they are. That’s why the proposed code checks for any hyphens before adding an extender. Any syllable which is not the last of a word must have a hyphen. Best,

Re: music function to be included somewhere in scm/*

On 15.12.2016 01:34, Alexander Kobel wrote: any use case for hyphen + extender? No. Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: music function to be included somewhere in scm/*

On 15.12.2016 13:34, Knut Petersen wrote: After a bit of thinking I'd say: go the radical route. Attached is a patch against current master that implements it that way. I like it, and I’d say: go ahead. Best, Simon ___ lilypond-devel mailing list

Re: music function to be included somewhere in scm/*

On 14.12.2016 14:54, Knut Petersen wrote: With a music function \autoextenders that adds extender events to every syllable you - can be sure never to forget extenders, - can be sure never to generate too short extenders - can use the same lyrics definition for voices that require extenders at

Re: unfoldRepeats can be restricted to certain repeat-types (issue 318890043 by thomasmorle...@gmail.com)

Hi Harm, thanks for the patch. As for the user-interface, I’d prefer something like \unfoldRepeats tremolo \m \unfoldRepeats volta,tremolo \m IIUC, that would require using predicate symbol-or-symbol-list? for the optional argument. (I hope that works… didn’t test TBH) Also, I think we

Re: Stepping up, contributor mentoring

On 30.11.2016 00:40, David Kastrup wrote: Graham Percival writes: Hi all, I'm back. Excellent news that could not have come at a better time. So, are there any vacancies on the Bug Squad? I vaguely fear so. In spite of the Bug Squad's importance I've been lousy

Re: Stepping down and moving on

Hi David, wow! Congratulations on the new job, and on having made that decision! Thanks a million for all the work and dedication you put into LilyPond and into the community. It was extremely valuable. All the best for your way ahead, cordially Simon On 09.11.2016 18:09, David Kastrup

Re: Whiteout / LyricHyphen

On 02.11.2016 21:36, Carl Sorensen wrote: So I don't know whether to say "include the code because we need the functionality" or "keep it out, because we don't want to break consistency". Consistency has already been broken in the 2.19 series, and for good reason. The precise form of the

Re: Akkordzither-tab in lilypond proper?

On 22.10.2016 10:00, Thomas Morley wrote: Hi, I recently mentioned my work to create the very special notation for Akkordzither. http://lists.gnu.org/archive/html/lilypond-user/2016-10/msg00349.html I consider to put it in the source, probably in the same way we have gregorian.ly. I think

Avoid a few trivial lambda function wrappers (issue 306710043 by d...@gnu.org)

Good call, thanks! https://codereview.appspot.com/306710043/diff/1/ly/music-functions-init.ly File ly/music-functions-init.ly (right): https://codereview.appspot.com/306710043/diff/1/ly/music-functions-init.ly#newcode1656 ly/music-functions-init.ly:1656: coords offsets))) Now the line-breaks

  1   2   3   >