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

Am 24.07.2017 um 13:58 schrieb David Kastrup: 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 ? +1 ___

Re: [Issue #3947] fixing \huge et al.

Hi Kieren, Am 25.06.2017 um 17:11 schrieb Kieren MacMillan: Hi, Another ten days has passed… I guess I don't understand how the Lilypond development process works. I keep hearing we need people to jump in and learn how to develop/improve Lilypond. I took the initiative, found an issue I tho

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

Am 16.12.2016 um 02:09 schrieb Alexander Kobel: Hi all. [...] What about hide-below-length or hide-if-shorter-than? minimum-visibility? Just my 2ct, Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listin

Re: Akkordzither-tab in lilypond proper?

Am 22.10.2016 um 16:29 schrieb Simon Albrecht: 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

Re: Akkordzither-tab in lilypond proper?

Am 22.10.2016 um 10:00 schrieb Thomas Morley: 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. What do

Re: Error in Documentation/de/web/introduction.html

Am 20.07.2016 um 15:41 schrieb Federico Bruni: [...] Who updated the german translation probably overlooked that change. If we could use gettext, this problem would not occur... I've pushed the fix directly to translation branch (work on translated manuals do not need a review process). Thanks

Error in Documentation/de/web/introduction.html

Hi list, currently, my whole git/patch-workflow environment is not working properly at the moment. Nevertheless, it seems to me that in line 616 of Documentation/de/web/introduction.html, @divClass{column-left-top} has to be replaced by @divClass{column-center-top} see http://lilypond.org/

Re: additional entry in lilypond.org/productions.html?

Am 10.07.2016 um 19:11 schrieb Federico Bruni: Il giorno ven 8 lug 2016 alle 12:36, Marc Hohl ha scritto: I have written some musicals for children and adolescents in the past and have two more musicals in the pipeline, to be released at the end of 2016. The sheets are done with LilyPond and

additional entry in lilypond.org/productions.html?

Hi list, I have written some musicals for children and adolescents in the past and have two more musicals in the pipeline, to be released at the end of 2016. The sheets are done with LilyPond and LaTeX and available for free, but the musicals are only available in German language. You can

Re: compiling lilypond fails

Am 25.06.2016 um 10:36 schrieb David Kastrup: David Kastrup writes: David Kastrup writes: autogen.sh --noconfigure configure --prefix=/home/knut/sources/lilybisect/ make -k -j 1 CPU_COUNT=1 all Logfile attached. I see a single error. That's ... curious. Have to go to rehearsal now, wil

Re: compiling lilypond fails

Am 24.06.2016 um 10:33 schrieb David Kastrup: [...] Well, it got through patchy-staging. So obviously something is different with your setup, and you don't give any information about your setup. What does g++ --version say? $ g++ --version g++ (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4 Copyright

compiling lilypond fails

Hi list, after a recent "git pull", the call "make -j3" fails with --- In file included from slur-engraver.cc:32:0: slur-engraver.cc: In static member function 'static void Slur_engraver::boot()': ./include/translator.icc:115:40: error: '&Slur_proto_engraver::listen_slur' is not a valid templ

Re: New context modifier \CompletionRhythms?

Am 01.04.2016 um 23:59 schrieb Simon Albrecht: Hello, using Completion_heads_engraver and Completion_rests_engraver means a lot of typing, and yet it is a pretty stereotypical action. So I thought about introducing a context modification identifier (like \RemoveEmptyStaves) for this task. Do you

Re: LilyPond boolean syntax? \true and \false

Am 05.01.2016 um 21:22 schrieb Thomas Morley: [...] To illustrate. Look at the output from the following compiled in a ly-file: true = ##t false = ##f #(define v1 (vector true false true)) #(define v2 #(true false true)) #(newline) #(write-me "v1 " v1) #(write-me "v2 " v2) #(write-me "(vector

Re: LilyPond boolean syntax? \true and \false

Am 05.01.2016 um 18:06 schrieb Abraham Lee: On Tuesday, January 5, 2016, Paul Morris wrote: Thanks to David Kastrup’s work there’s now much less need to use scheme syntax in overrides etc. (e.g. the dot syntax instead of #' and no longer needing # for numbers). This has really simplified thin

Re: Improve wording for an NR paragraph (issue 259710043 by simon.albre...@mail.de)

LGTM, Marc Am 02.09.2015 um 21:26 schrieb simon.albre...@mail.de: Reviewers: , Message: I came across this rather mishapen wording in NR 4.6.2 – so I changed it. Description: Improve wording for an NR paragraph The paragraph from "Avoid (or reduce)" in spacing.itely used 'for example' twice

Re: Remove old "News" entry from home page

Am 10.07.2015 um 20:49 schrieb Paul Morris: On Jul 9, 2015, at 5:39 AM, James wrote: Perhaps we can tweak the 'website' slightly (i.e. make small changes to the TexInfo code) to perhaps do something like moving some/all of the text from here http://lilypond.org/introduction.html to the front

Re: [Lilypond-auto] Issue 4460 in lilypond: Parentheses in ChordNames should have the same size as the chord symbols

Am 23.06.2015 um 11:31 schrieb lilyp...@googlecode.com: Comment #5 on issue 4460 by thomasmo...@gmail.com: Parentheses in ChordNames should have the same size as the chord symbols https://code.google.com/p/lilypond/issues/detail?id=4460 Is this issue a duplicate of https://code.google.com/p/lil

Re: [Lilypond-auto] Issue 4460 in lilypond: Parentheses in ChordNames should have the same size as the chord symbols

Am 23.06.2015 um 11:03 schrieb James: Marc On 23/06/15 09:25, Marc Hohl wrote: Am 23.06.2015 um 10:15 schrieb lilyp...@googlecode.com: Updates: Labels: -Patch-review Patch-needs_work Comment #3 on issue 4460 by pkx1...@gmail.com: Parentheses in ChordNames should have the same size as

Re: [Lilypond-auto] Issue 4460 in lilypond: Parentheses in ChordNames should have the same size as the chord symbols

Am 23.06.2015 um 10:15 schrieb lilyp...@googlecode.com: Updates: Labels: -Patch-review Patch-needs_work Comment #3 on issue 4460 by pkx1...@gmail.com: Parentheses in ChordNames should have the same size as the chord symbols https://code.google.com/p/lilypond/issues/detail?id=4460 This look

Re: Parentheses in ChordNames have the same size as the Chord symbols. (issue 245430043 by m...@hohlart.de)

Am 21.06.2015 um 10:43 schrieb d...@gnu.org: https://codereview.appspot.com/245430043/diff/1/ly/engraver-init.ly File ly/engraver-init.ly (right): https://codereview.appspot.com/245430043/diff/1/ly/engraver-init.ly#newcode517 ly/engraver-init.ly:517: \override ParenthesesItem.font-size = #1.5

Re: Parentheses in ChordNames

Am 20.06.2015 um 19:47 schrieb David Kastrup: Marc Hohl writes: Hi list, in my latest project, I found out that \score { \new ChordNames { \chordmode { \parenthesize c } } } yields in way too tiny parentheses. The following patch resolves that problem. I recall vaguely that 'g

Parentheses in ChordNames

o Rietveld? Cheers, Marc From 360d89c13713be692db3a6fc557eda0f7557a288 Mon Sep 17 00:00:00 2001 From: Marc Hohl Date: Sat, 20 Jun 2015 19:19:03 +0200 Subject: [PATCH] Parentheses in ChordNames have the same size as the Chord symbols. --- ly/engraver-init.ly | 1 + 1 file changed, 1 insertio

Re: [PATCH 1/5] Remove parser/location global variable setup

Am 31.05.2015 um 07:47 schrieb David Kastrup: [...] Well, that was actually more what I considered strange: the lack of comment on the result/merits rather than on the particular implementation. I can just speak for myself, but the actual benefit of this patch was not obviously clear for me, b

Re: Google Code shutting down

Am 19.05.2015 um 09:04 schrieb James Lowe: [...] Oh if someone could look at the script that Mark Hohl (I think) created a while back called 'make-countdown-announcement.sh' No, it was Mark Polesky who added it. Cheers, Marc ___ lilypond-devel m

Re: Just some short feedback

Am 28.04.2015 um 00:20 schrieb Trevor Daniels: I'd like to second everything that Carl writes below, and add my thanks to you, David. +1 Marc Trevor Carl Sorensen wrote Monday, April 27, 2015 11:07 PM On 4/27/15 3:09 AM, "David Kastrup" wrote: As things currently stand, I suspect that

Re: Sans-serif free Unicode font (was Re: Ghostscript 9.15)

Am 25.03.2015 um 18:58 schrieb Carl Sorensen: On 3/25/15 6:54 AM, "u...@openlilylib.org" wrote: I think the fonts we're looking for should have a similarly classic or old-fashioned look as Century. Maybe we should look for fonts that (optionally) ship with texlive. Hunting around for sans

Re: Guitar right-hand fingering

Am 17.03.2015 um 11:24 schrieb Thomas Morley: 2015-03-17 11:00 GMT+01:00 Peter Bjuhr : Hi, I just noticed that in the documentation about right-hand fingerings in the common notation for fretted strings: http://www.lilypond.org/doc/ v2.19/Documentation/notation/common-notation-for-fretted- str

Re: Reduce size of PDF files when inc. in *TeX docs (issue 194090043 by pkx1...@gmail.com)

Am 30.01.2015 um 09:57 schrieb Werner LEMBERG: Die erzeugten PDF-Dateien sind sehr viel größer als normal (aufgrund der schwachen oder fehlenden Schriftartenoptimierung). Wenn jedoch zwei oder mehr PDF-Dateien mittels pdftex, xetex oder luatex eingebunden werden, können sie mit Ghostscript nach

Re: Reduce size of PDF files when inc. in *TeX docs (issue 194090043 by pkx1...@gmail.com)

Am 29.01.2015 um 19:44 schrieb pkx1...@gmail.com: Can someone give me the translation in German for: "PDF files generated will be much larger than normal (due to little or no font optimization). However, if two or more PDF files are included within pdftex, xetex or luatex documents they can then

Re: parentheses in tablature

Am 19.01.2015 um 19:23 schrieb James: On 19/01/15 17:43, David Kastrup wrote: Marc Hohl writes: Am 19.01.2015 um 14:51 schrieb James: On 09/01/15 09:25, Marc Hohl wrote: Hi list, the appearance of cautionary tab note heads differs from parenthesized ones, see the output of \version

Re: parentheses in tablature

Am 19.01.2015 um 14:51 schrieb James: On 09/01/15 09:25, Marc Hohl wrote: Hi list, the appearance of cautionary tab note heads differs from parenthesized ones, see the output of \version "2.19.0" \new TabStaff { \parenthesize c4 c~ \bar "" \break c2 } I think this is a

parentheses in tablature

Hi list, the appearance of cautionary tab note heads differs from parenthesized ones, see the output of \version "2.19.0" \new TabStaff { \parenthesize c4 c~ \bar "" \break c2 } I think this is a bug. Should I raise an issue for that? Marc ___ li

Re: scheme engraver for StaffTab notation

Am 07.01.2015 um 22:27 schrieb Ricardo Wurmus: Hi, a while ago I wrote a scheme engraver that outputs something close to StaffTab notation. StaffTab notation is a mix of standard two staff notation with a few elements of tabulature tailored to the free hands methods of playing the Chapman Stick

Re: Compound time signature style

Am 04.11.2014 um 12:55 schrieb Dan Eble: 2 + 32 + 3 4 - + C vs.- + - 44 4 Undesirable in my book. I overlooked the fact that the denominators are the same, so either […] I'd rather not use the C symbol in these cases.

Re: Compound time signature style

Am 04.11.2014 um 15:18 schrieb Hans Aberg: On 4 Nov 2014, at 10:49, Marc Hohl wrote: Am 04.11.2014 um 07:48 schrieb David Kastrup: Dan Eble writes: If the simple-fraction components of a compound time signature respected the time signature style, would that qualify as useful or as

Re: Compound time signature style

Am 04.11.2014 um 07:48 schrieb David Kastrup: Dan Eble writes: If the simple-fraction components of a compound time signature respected the time signature style, would that qualify as useful or as undesirable? For example, 2 + 32 + 3 4 - + C vs.- +

Re: Compound time signature style

Am 03.11.2014 um 19:26 schrieb Dan Eble: If the simple-fraction components of a compound time signature respected the time signature style, would that qualify as useful or as undesirable? For example, 2 + 32 + 3 4 - + C vs.- + - 4

Re: Phase two of pruning snippets/new (issue 113670043 by philehol...@googlemail.com)

Am 30.07.2014 um 17:34 schrieb Phil Holmes: - Original Message - From: To: Cc: ; Sent: Wednesday, July 30, 2014 3:57 PM Subject: Re: Phase two of pruning snippets/new (issue 113670043 by philehol...@googlemail.com) https://codereview.appspot.com/113670043/diff/20001/Documentation/s

Re: Issue 4015: Add \magnifyStaff. (issue 117830043 by markpole...@gmail.com)

Am 18.07.2014 01:59, schrieb David Nalesnik: Hi Mark, On Thu, Jul 17, 2014 at 2:34 PM, mailto:markpole...@gmail.com>> wrote: While I have your attention, there was some discussion on the mailing list about changing \magnifyMusic and \magnifyStaff to \resizeMusic and \resizeStaff.

Re: Issue 4015: Add \magnifyStaff. (issue 117830043 by markpole...@gmail.com)

Am 16.07.2014 21:18, schrieb Mark Polesky: On Wed, Jul 16, 2014 at 12:01 PM, Paul Morris wrote: The best ideas I've come up with would be either "resize" or "scale". Since scale could be confused with the musical meaning of scale, I think resize is the better option of these two. \resizeSta

Re: LilyPond meeting 2014?

Am 12.07.2014 19:58, schrieb Mike Solomon: On Jul 12, 2014, at 3:48 PM, Marc Hohl wrote: [...] I’d love to meet up but I am in gig mode as well towards the end of the summer and we have a newborn in the house. Hey, congratulations! The nights are quiet, yes? ;-) All the best for all of

Re: LilyPond meeting 2014?

Am 12.07.2014 14:44, schrieb Janek Warchoł: Hi all, [...] Unfortunately i'm busy on that weekend :( Is there noone else interested? Basically, I am interested as well, but I have a concert on August 30th :-( Marc Janek ___ lilypond-devel mailing

Re: Remove thin-kern property. (issue 105560044 by markpole...@gmail.com)

Am 08.07.2014 20:20, schrieb markpole...@gmail.com: marc wrote: OK, but 'thin-kern does not seem to be an appropriate name for this property anymore IMHO. How about 'segno-kern? (patch updated accordingly) Much better! ___ lilypond-devel mailin

Re: Remove thin-kern property. (issue 105560044 by markpole...@gmail.com)

Am 08.07.2014 02:17, schrieb Paul Morris: Thomas Morley-2 wrote But *do* we need two different variables which then are used with exactly the same value? Do we need the option to change the distance of the segno double bar line? I'd say yes. I'm always against loosing functionality, and dele

Re: Remove thin-kern property. (issue 105560044 by markpole...@gmail.com)

Am 06.07.2014 13:52, schrieb thomasmorle...@gmail.com: On 2014/07/06 06:46:53, Mark Polesky wrote: Hi, I'm proposing to get rid of the BarLine.thin-kern property with this patch, so if you're opposed, let me know. You can see my comments/rationale here: http://code.google.com/p/lilypond/iss

Re: FretBoards aligned to bar lines

Am 04.07.2014 09:46, schrieb Marc Hohl: Hi list, sorry, wrong list ... I re-posted this question on -user, sorry for the noise. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

FretBoards aligned to bar lines

Hi list, in the following example, I want to align the FretBoards to the bar lines. Now they are centered over the first beat in each measure. TIA, Marc --- \version "2.19.0" \paper { indent = 0 ragged-right = ##f } frets = { < d'\3 g'\2 b'\1 >1 | < g\4 cis'\3 e'\2 > | < cis'\3 fis'\2

Re: Issue 3254: align unassociated lyrics using NoteColumn extent. (issue 108110044 by janek.lilyp...@gmail.com)

Am 22.06.2014 16:00, schrieb David Kastrup: Marc Hohl writes: Am 22.06.2014 14:57, schrieb d...@gnu.org: Start of the coffee canon? https://www.youtube.com/watch?v=8PN23MIqoLY> Though somewhat boring rhythmically. I was about to propose capital letters like 'A' &#

Re: Issue 3254: align unassociated lyrics using NoteColumn extent. (issue 108110044 by janek.lilyp...@gmail.com)

Am 22.06.2014 14:57, schrieb d...@gnu.org: On 2014/06/22 12:45:47, janek wrote: https://codereview.appspot.com/108110044/diff/60001/Documentation/notation/vocal.itely File Documentation/notation/vocal.itely (right): https://codereview.appspot.com/108110044/diff/60001/Documentation/notation/

Re: varC clefs in 2.19

Am 01.06.2014 08:54, schrieb James: On 31/05/14 22:44, bobr...@centrum.is wrote: - Original Message - From: "James" To: bobr...@centrum.is Cc: "lilypond-devel" Sent: Friday, May 30, 2014 3:16:53 PM Subject: Re: varC clefs in 2.19 On 30/05/14 14:12, bobr...@centrum.is wrote: - Or

Re: Issue 3926: Add \magnifyMusic; clarify fontSize in docs. (issue 96570043)

Am 24.05.2014 08:33, schrieb d...@gnu.org: https://codereview.appspot.com/96570043/diff/1/ly/music-functions-init.ly File ly/music-functions-init.ly (right): https://codereview.appspot.com/96570043/diff/1/ly/music-functions-init.ly#newcode646 ly/music-functions-init.ly:646: \override Beam.beam

Re: corrects typo in bar-line.scm (issue 96790048)

LGTM Thanks for this patch! Marc Am 28.04.2014 11:35, schrieb thomasmorle...@gmail.com: Reviewers: , Message: Please review Description: corrects typo in bar-line.scm issue 3908 Missing space in (define-bar-line ":|]" ":|]" #f " |") caused bad visual output of VoltaBracket. Changed to (defi

Re: Version guard comments

Am 05.03.2014 19:34, schrieb David Kastrup: Just now I wrote in a file intended for Mutopia [...] We just need to come up with a good, clean comment convention and then teach convert-ly about it. How about some sed-like tag? { \set Timing.measurePosition = #(ly:make-moment 0) % >= 2.19.0

Re: PATCHES: Countdown for Feb 11 - 06:00 GMT

Am 08.02.2014 16:50, schrieb James: On 08/02/14 15:03, Marc Hohl wrote: Am 08.02.2014 11:10, schrieb James: Hello, 3833 <http://code.google.com/p/lilypond/issues/detail?id=3833&q=label%3APatch-countdown%20OR%20label%3APatch-waiting%20OR%20label%3APatch-review%20OR%20label%3APatch-n

Re: PATCHES: Countdown for Feb 11 - 06:00 GMT

Am 08.02.2014 11:10, schrieb James: Hello, 3833

Re: Add "Editing" page/node (issue 60530047)

Am 07.02.2014 23:32, schrieb Urs Liska: Am 07.02.2014 22:24, schrieb Janek Warchoł: Hi, 2014-02-07 Urs Liska : At http://www.openlilylib.org/lilyweb/editing.html you can see the actual page _with_ the new image (in order to compile locally you'd have to pull from lilypond-extra). My com

Re: Issue 693?

Am 05.02.2014 14:45, schrieb Werner LEMBERG: As the patch contained more new glyphs, a separate issue was created. Now I wonder whether 693 can be closed, or is the yet alternate glyph described in http://code.google.com/p/lilypond/issues/detail?id=693#c3 reason enough to let this issue stay

Re: How to remove a changed clef glyph from the end of staff line

Am 04.02.2014 21:43, schrieb James: Hello, Perhaps I am misunderstanding the break-visibility option but how do I stop the bass clef glyph (in my example below) from printing at the end of the line and only print on the next line? \version "2.19.2" { c'1 \break \override Staff.Clef #'

Issue 693?

Hello list, Recently I pushed a patch providing an alternate C clef clyph, according to http://code.google.com/p/lilypond/issues/detail?id=693 As the patch contained more new glyphs, a separate issue was created. Now I wonder whether 693 can be closed, or is the yet alternate glyph described in

Re: Tempo placement

Am 03.02.2014 15:15, schrieb Robin Bannister: Marc Hohl wrote: Try \once \override Score.LeftEdge.break-visibility = #all-visible Thanks, sounds plausible, but it doesn't work either: Umm ... and with MetronomeMark ? D'Oh... Works significantly better ;-) Sorry for

Re: Tempo placement

Am 03.02.2014 10:45, schrieb Robin Bannister: Marc Hohl wrote: But why does LilyPond seem to ignore '(left-edge)? It seems it is not "visible". The first left edge doesn't arise via a line break, so for pedantic Lilypond the _unbroken_ case applies. Try \once \override

Re: Tempo placement

[CC'ing to -devel] Am 03.02.2014 00:44, schrieb Eluze: Marc Hohl wrote Hi list, I want the tempo indication to appear at the leftmost edge of the piece (I know that Gould has a different opinion about this, but I am using LilyJAZZ, and the Realbook style does not care about these typogr

Re: TabNoteHead Style

Am 02.02.2014 07:28, schrieb James: Hello, I don't know much about Tabular notation but Marc Hohl added "support for 'slash" recently http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=e2561c80134f16663c1a05e081d3719d80f3114f Does this need an example in

Re: Double G clef, tenor G clef, varpercussion clef and varC clef (issue 47840043)

Am 18.01.2014 07:12, schrieb lemzw...@googlemail.com: First of all: Looking at clefs.tenorG, patch set 5 compared to patch set 4 has a side effect: It reduces the height of the glyph's top. Is this intentional? I guess it's not, so please fix this. Done. I don't fully understand why (yet), b

Metafont/Fontforge problems (Issue 3772)

Hi list, it seems that there are some incopatibilities with my current setup (Ubuntu 12.04, fontforge 20110222) and the environment where Patchy runs. http://code.google.com/p/lilypond/issues/detail?id=3772#c22 shows the current mangled output, but my machine at home compiles the file clefs.ly

Re: Pre-review questions about image(s) and translations

Am 16.01.2014 09:08, schrieb Urs Liska: Am 16.01.2014 08:58, schrieb Graham Percival: On Wed, Jan 15, 2014 at 08:33:37AM -0500, Carl Peterson wrote: My first instinct is to prepare an SVG file that could be processed with inkscape or another program as part of the make process. That i

Re: how close are we to having an "addAt" or "insertAt" feature?

Am 16.01.2014 06:35, schrieb David Kastrup: Alex Loomis writes: How much sense would it make for there to be a separate \mark-style command that functioned identically but didn't mess with the counter? What do you mean? Neither \mark #4 nor \mark "G" mess with the counter. Perhaps some ki

Re: Double G clef, tenor G clef, varpercussion clef and varC clef (issue 47840043)

Am 06.01.2014 13:54, schrieb Ian Hulin: Hi Marc and all, I've attached a scan of a fragment using some 18C alto and tenor clefs (Handel, Acis and Galatea, 1718). I'm not suggesting you use these as the altC clef as they are rather ugly, but rather to inform some suggestions for the varC clef.

Re: Double G clef, tenor G clef, varpercussion clef and varC clef (issue 47840043)

Am 05.01.2014 11:40, schrieb Werner LEMBERG: [...] Well, you *should* use tabs, so this deserves a new patch set anyway. [...] Done. Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Regtest enhanced for the new clefs (issue 47840043)

Am 04.01.2014 17:59, schrieb d...@gnu.org: https://codereview.appspot.com/47840043/diff/1/input/regression/clefs.ly File input/regression/clefs.ly (right): https://codereview.appspot.com/47840043/diff/1/input/regression/clefs.ly#newcode1 input/regression/clefs.ly:1: \version "2.19.1" This vers

Re: regtest for new glyphs necessary?

Am 03.01.2014 08:03, schrieb Keith OHara: Marc Hohl hohlart.de> writes: I am about to upload a patch for these four glyphs within the next days, but I wanted to ask whether a new (or enhanced existing) regtest is necessary for this type of enhancement? They could conceivably be bro

regtest for new glyphs necessary?

Hello list, happy new year to you all! I have drawn some new glyphs for LilyPond, namely 1) the double G clef, mentioned in http://lists.gnu.org/archive/html/lilypond-user/2010-02/msg00029.html 2) the varpercussion clef, mentiaoned in the same message 3) the tenor G clef, mentioned in http:/

unsubscribing from -devel

Hi all, after a lot of considering pros and cons and being realistic about the amount of time left to spend on development, I decided to unsubscribe from this list :-( My last remarkable contribution is about 9 months ago, and all attempts to getting into lilypond again (not only visible on -dev

Re: Reformat some files to let emacs do its work correctly. (issue 9863047)

Am 07.06.2013 14:53, schrieb James: [...] For some reason it wasn't being picked up by Patchy, so I had to 'turn-it-off-and-turn-it-on-again' so that Patch-New was detected for testing. In case you wondered. I wondered in fact, but thanks for clarification. Marc james __

Re: Reformat some files to let emacs do its work correctly. (issue 9863047)

Am 07.06.2013 09:07, schrieb Keith OHara: On Thu, 06 Jun 2013 23:04:29 -0700, wrote: I think I'll draw a patch that corrects the minor faults; ideally, running fixscm again should lead in no changes at all. That makes good sense. It is hard to spot unwanted changes among the good changes f

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

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: 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

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: (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: 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: 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: 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: 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: 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: 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: 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 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

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: 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

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: 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: 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: [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: [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 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: 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: 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: 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

  1   2   3   4   5   6   7   >