Re: [Doc] Organizing changes.tely

.20 was born, James arranged > changes.tely such that items don't get just stacked one over the other > but sort of reflect the organizing of the Notation Reference. I found it > very wise and useful for the reader, and kept that during the > development of 2.21

Re: [Doc] Organizing changes.tely

Am Samstag, dem 09.10.2021 um 19:28 +0200 schrieb Jean-Charles Malahieude: > Hello all, > > In the last days of 2017, just before 2.20 was born, James arranged > changes.tely such that items don't get just stacked one over the other > but sort of reflect the organizing of th

Re: [Doc] Organizing changes.tely

> Le 9 oct. 2021 à 19:28, Jean-Charles Malahieude a écrit : > > Hello all, > > In the last days of 2017, just before 2.20 was born, James arranged > changes.tely such that items don't get just stacked one over the other but > sort of reflect the organizing of

[Doc] Organizing changes.tely

Hello all, In the last days of 2017, just before 2.20 was born, James arranged changes.tely such that items don't get just stacked one over the other but sort of reflect the organizing of the Notation Reference. I found it very wise and useful for the reader, and kept that durin

Re: Doc: organize changes.tely

Le 09/03/2020 à 19:09, David Kastrup a écrit : Francisco Vila writes: El 9/3/20 a las 11:58, David Kastrup escribió: I think I was told to run the update script and forgot. I am not sure where to run it now in order to get the results somewhere. do make translation-status from Documen

Re: Doc: organize changes.tely

Francisco Vila writes: > El 9/3/20 a las 11:58, David Kastrup escribió: >> I think I was told to run the update script and forgot. I am not sure >> where to run it now in order to get the results somewhere. > > do > > make translation-status > > from Documentation/ . > > Then commit changes to

Re: Doc: organize changes.tely

El 9/3/20 a las 11:58, David Kastrup escribió: I think I was told to run the update script and forgot. I am not sure where to run it now in order to get the results somewhere. do make translation-status from Documentation/ . Then commit changes to contributor/doc-translation-list.itexi

Re: Doc: organize changes.tely

El 9/3/20 a las 10:35, Valentin Villenave escribió: I’m a bit uncomfortable with the hardcoded date in translations.itexi:-) translations.itexi is not meant to be manually edited; it is a generated file. I agree it _looks_ harcoded because it's old now. -- Francisco Vila, Ph.D. - Badajoz (S

Re: Doc: organize changes.tely

Valentin Villenave writes: > On 3/9/20, David Kastrup wrote: >> I think I was told to run the update script and forgot. I am not sure >> where to run it now in order to get the results somewhere. > > Oh, good. Perhaps we should mention it in the CG’s release-work.itexi > to make it less easy fo

Re: Doc: organize changes.tely

On 3/9/20, David Kastrup wrote: > I think I was told to run the update script and forgot. I am not sure > where to run it now in order to get the results somewhere. Oh, good. Perhaps we should mention it in the CG’s release-work.itexi to make it less easy for people to overlook in the future? I

Re: Doc: organize changes.tely

Valentin Villenave writes: > On 3/8/20, Francisco Vila wrote: >> Yes please, it was painful to re-organize a half-translated version. Now >> is soon enough, still. > > By the way (on a more-than-slightly unrelated note), how up-to-date is > the official translation status page? > http://lilypond

Re: Doc: organize changes.tely

On 3/8/20, Francisco Vila wrote: > Yes please, it was painful to re-organize a half-translated version. Now > is soon enough, still. By the way (on a more-than-slightly unrelated note), how up-to-date is the official translation status page? http://lilypond.org/translated.html I’m a bit uncomfort

Re: Doc: organize changes.tely

El 8/3/20 a las 17:43, Jean-Charles Malahieude escribió: Purging the French version of changes.tely, came to my mind it might be wise to avoid moving around and re-organize items like James did in late 2017 when preparing for a new major release (and translators afterwards) and have it

Re: Doc: organize changes.tely

Le 08/03/2020 à 18:34, pkx1...@posteo.net a écrit : The sectioning was done based on (sort of) how the NR is organized and I thought it would be more useful for users to search for something based on its type of enhancement/change than just in the order the changes were added. And it was a

Re: Doc: organize changes.tely

On 08/03/2020 16:43, Jean-Charles Malahieude wrote: Hi all, Purging the French version of changes.tely, came to my mind it might be wise to avoid moving around and re-organize items like James did in late 2017 when preparing for a new major release (and translators afterwards) and have it

Doc: organize changes.tely

Hi all, Purging the French version of changes.tely, came to my mind it might be wise to avoid moving around and re-organize items like James did in late 2017 when preparing for a new major release (and translators afterwards) and have it structured on the fly. This was the first time for

Changes.tely - Add \afterGrace optional argument (issue 551260043 by rietveld...@tutanota.com)

LGTM https://codereview.appspot.com/551260043/

Re: Changes.tely

ched notes' in book notation. > > Seems to be a wrong command in changes.tely -- lines 335 > > @noindent > with multiple exceptions separated by bar checks. Note that writing the > exception pattern without pitches is convenient but not mandatory (also > see the previous documente

Re: Changes.tely

ched notes' in book notation. > > Seems to be a wrong command in changes.tely -- lines 335 > > @noindent > with multiple exceptions separated by bar checks. Note that writing the > exception pattern without pitches is convenient but not mandatory (also > see the previous docume

Changes.tely

Hi James, I didn't review your patch, but Documentation/changes-splittexi.log contains WARNING: Unable to find node 'Isolated durations in music now stand for unpitched notes' in book notation. Seems to be a wrong command in changes.tely -- lines 335 @noindent with mult

Re: Changes.tely - reorganize entries for 2.20 release (issue 326400043 by pkx1...@gmail.com)

On 2017/10/01 17:11:41, pkx166h wrote: On 2017/10/01 10:57:31, dak wrote: > https://codereview.appspot.com/326400043/diff/60001/Documentation/changes.tely > File Documentation/changes.tely (right): > > https://codereview.appspot.com/326400043/diff/60001/Documentation/changes.te

Re: Changes.tely - reorganize entries for 2.20 release (issue 326400043 by pkx1...@gmail.com)

On 2017/10/01 10:57:31, dak wrote: https://codereview.appspot.com/326400043/diff/60001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/326400043/diff/60001/Documentation/changes.tely#newcode67 Documentation/changes.tely:67: hyphenated; A

Re: Changes.tely - reorganize entries for 2.20 release (issue 326400043 by pkx1...@gmail.com)

https://codereview.appspot.com/326400043/diff/60001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/326400043/diff/60001/Documentation/changes.tely#newcode67 Documentation/changes.tely:67: hyphenated; A few remarks after the fact (sorry for

Changes.tely - reorganize entries for 2.20 release (issue 326400043 by pkx1...@gmail.com)

ce the order has been reasonably approved, I'll start to make edits to the text where appropriate and include some more @lilypond examples. Thank you. Description: Changes.tely - reorganize entries for 2.20 release Issue 5176 Documents all changes to LilyPond since 2.18. The list is o

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

Thanks for your help. I made a test file and got it to compile without errors. https://codereview.appspot.com/275770043/diff/40001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/275770043/diff/40001/Documentation/changes.tely#newcode88

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

https://codereview.appspot.com/275770043/diff/40001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/275770043/diff/40001/Documentation/changes.tely#newcode88 Documentation/changes.tely:88: g1' This needs to be g'1 instead of g1&#x

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

doesn't compile doc https://codereview.appspot.com/275770043/diff/40001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/275770043/diff/40001/Documentation/changes.tely#newcode91 Documentation/changes.tely:91: This snippet doesn't

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

Patch set 3 to removes the double quotes after '@end lilypond' in changes.tely. Should be all good to go now. -Paul https://codereview.appspot.com/275770043/diff/20001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/275770043/

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

Thanks for the feedback. All fixed in patch set 2. -Paul https://codereview.appspot.com/275770043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/275770043/diff/1/Documentation/changes.tely#newcode72 Documentation/changes.tely:72

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

https://codereview.appspot.com/275770043/diff/20001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/275770043/diff/20001/Documentation/changes.tely#newcode90 Documentation/changes.tely:90: @end lilypond" Paul, sorry - I did comment on

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

I raise a couple of questions - maybe I'm not understanding something. https://codereview.appspot.com/275770043/diff/1/scm/define-grob-properties.scm File scm/define-grob-properties.scm (right): https://codereview.appspot.com/275770043/diff/1/scm/define-grob-properties.scm#newcode1143 scm/defin

Re: Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

This fails make/make doc (see comments inline) https://codereview.appspot.com/275770043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/275770043/diff/1/Documentation/changes.tely#newcode72 Documentation/changes.tely:72: \\markup { You

Issue 4504/5 update changes.tely (issue 275770043 by paulwmor...@gmail.com)

4504/ Thanks, -Paul Description: Issue 4504/5 update changes.tely Issue 4504/4 edits to tests and docs Issue 4504/3 run scripts/auxiliar/update-with-convert-ly.sh Issue 4504/2 convert-ly rule: whiteout-box --> whiteout Issue 4504/1 add whiteout-style, drop whiteout-box Introduce whiteout-st

Better changes.tely example; issue 4197 (issue 215790043 by k-ohara5...@oco.net)

Patch counted down - please push https://codereview.appspot.com/215790043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

https://codereview.appspot.com/147860043/diff/50001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/147860043/diff/50001/Documentation/changes.tely#newcode104 Documentation/changes.tely:104: @end example On 2014/09/22 18:19:52, ht wrote: Just

Re: Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

https://codereview.appspot.com/147860043/diff/50001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/147860043/diff/50001/Documentation/changes.tely#newcode104 Documentation/changes.tely:104: @end example Just a small note: While this example

Re: Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode106 Documentation/changes.tely:106: grob can now be aligned on the @q{center} of its parent. On

Re: Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

Thanks to those that checked. New patch uploaded https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode69 Documentation/changes.tely:69: \once

Re: Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

Just some minor nitpicks, as I cannot speak about the details of the recent changes. https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode105

Re: Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode127 Documentation/changes.tely:127: the existing @code{\keepWithTag} and @code{removeWithTag

Re: Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/147860043/diff/1/Documentation/changes.tely#newcode69 Documentation/changes.tely:69: \once \override ChorName.text = #"foo" ChordName.t

Changes.tely updated - 2.19.x up to September 2014 (issue 147860043 by pkx1...@gmail.com)

ancements and if you think I have missed any or some are not appropriate and needn't be listed let me know. Description: Changes.tely updated - 2.19.x up to September 2014 Since June 2014. Added Tracker issues 2245/4005, 2813/3966, 3186, 3734/3825/3834, 4015, 4022, 4038, 4042, 4047, 4056, 4

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely#newcode68 Documentation/changes.tely:68: Add support for @code{\once}@code{\unset} On 2014/07/04

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely#newcode143 Documentation/changes.tely:143: spaced using only its @emph{left-edge} as reference

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

> The arrows don't seem to show up in the PDF output (that may be my > viewer I haven't checked elsewhere) however if we did do this we would > have remove the @lilypond verbatim because you cannot really see the > 'words' clearly in the construction, it's just a 'bunch' of double quotes. > > I'll

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 bypkx1...@gmail.com)

The arrows don't seem to show up in the PDF output (that may be my viewer I haven't checked elsewhere) however if we did do this we would have remove the @lilypond verbatim because you cannot really see the 'words' clearly in the construction, it's just a 'bunch' of double quotes. I'll defer to

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

) } \markup \typewriter \fill-line \underline { "&down;" " &down; " " &down; " " &down; " "&down;" } \paper { #(include-special-characters) } \markup \typewriter \justify-line \underline { "&down;

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely#newcode68 Documentation/changes.tely:68: Add support for @code{\once}@code{\unset} @code{\once

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

On 2014/06/30 22:00:15, J_lowe wrote: Thanks https://codereview.appspot.com/108130043/diff/70001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/70001/Documentation/changes.tely#newcode141 Documentation/changes.tely:141: A

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

Thanks https://codereview.appspot.com/108130043/diff/70001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/70001/Documentation/changes.tely#newcode141 Documentation/changes.tely:141: A new markup command @code{\justify-line} has

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

https://codereview.appspot.com/108130043/diff/70001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/70001/Documentation/changes.tely#newcode141 Documentation/changes.tely:141: A new markup command @code{\justify-line} has been

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

Now added an example for the horizontal and parenthesis padding for fretted diagrams https://codereview.appspot.com/108130043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/1/Documentation/changes.tely#newcode90

Re: Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

Thanks https://codereview.appspot.com/108130043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/1/Documentation/changes.tely#newcode68 Documentation/changes.tely:68: Improved the automatic @q{x-extent} placement of

Changes.tely updated - 2.19.x up to June 2014 (issue 108130043 by pkx1...@gmail.com)

Thanks for scraping the reports for this! https://codereview.appspot.com/108130043/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/108130043/diff/1/Documentation/changes.tely#newcode68 Documentation/changes.tely:68: Improved the

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

2014-02-18 20:02 GMT+01:00 : > > I suggest that you just forget about it until you have the leisure to > read and contemplate the full comment #15 including its quoted material. > I don't see that we are getting anywhere in that manner. yes, it seems you're right. sorry... j _

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

On 2014/02/18 18:29:22, janek wrote: sorry, i don't understand what you mean :( I quoted the original description, I quoted the code you posted, I listed the code that one arrives at when actually following the description, and I gave an example of what works with that changed code. I suggest

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

sorry, i don't understand what you mean :( 2014-02-18 19:17 GMT+01:00 : > On 2014/02/18 18:09:08, janek wrote: > >> > I think that turning \coloredNotes into a context definition > > producer by >> >> > just removing the \layout { and matching } without any other change >> > would work fine and m

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

On 2014/02/18 18:09:08, janek wrote: > I think that turning \coloredNotes into a context definition producer by > just removing the \layout { and matching } without any other change > would work fine and make a nice example. You mean something like this? coloredNotes = #(define-scheme-fu

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

2014-02-18 18:06 GMT+01:00 : > That example is disturbing since it is not really about using a function > as an output definition, but rather about using a function as a > _context_ definition. You usually would not expect the above to work > but > \layout { indent = #0 \coloredNotes #blue } > to

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

On 2014/02/18 16:27:25, janek wrote: LGTM with a suggestion https://codereview.appspot.com/60490050/diff/90001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/60490050/diff/90001/Documentation/changes.tely#newcode122 Documentation

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

LGTM with a suggestion https://codereview.appspot.com/60490050/diff/90001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/60490050/diff/90001/Documentation/changes.tely#newcode122 Documentation/changes.tely:122: Scheme functions and

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

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

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

On 2014/02/08 19:38:38, J_lowe wrote: So this sounds like (and from my cursory experiments with lilypond-book compiling snippets) that bits of the NR http://lilypond.org/doc/v2.19/Documentation/notation/long-repeats are no longer needed now. --snip-- @lilypond[fragment,quote,relative=2] \

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

https://codereview.appspot.com/60490050/diff/20001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/60490050/diff/20001/Documentation/changes.tely#newcode64 Documentation/changes.tely:64: @code{Partcombiner}'s handing of repeated note dura

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

https://codereview.appspot.com/60490050/diff/20001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/60490050/diff/20001/Documentation/changes.tely#newcode64 Documentation/changes.tely:64: @code{Partcombiner}'s handing of repeated note dura

Re: Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

Reviewers: dak, Message: On 2014/02/08 12:45:33, dak wrote: https://codereview.appspot.com/60490050/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/60490050/diff/1/Documentation/changes.tely#newcode108 Documentation/changes.tely:108

Changes.tely updated - 2.19.x before Feb 4th 2014 (issue 60490050)

https://codereview.appspot.com/60490050/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/60490050/diff/1/Documentation/changes.tely#newcode108 Documentation/changes.tely:108: Chord change detection in @code{\repeat} alternatives now

Re: Doc: Changes.tely 2.18 release (issue 24180044)

LGTM thanks, James! https://codereview.appspot.com/24180044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: Changes.tely 2.18 release (issue 24180044)

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

Re: Doc: Changes.tely 2.18 release (issue 24180044)

https://codereview.appspot.com/24180044/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/24180044/diff/1/Documentation/changes.tely#newcode65 Documentation/changes.tely:65: There is now a new context called @code{NullVoice} which, while

Doc: Changes.tely 2.18 release (issue 24180044)

Weird, i thought that i've sent this comment before. https://codereview.appspot.com/24180044/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/24180044/diff/1/Documentation/changes.tely#newcode67 Documentation/changes.tely:67: al

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

On Sun, 03 Mar 2013 00:18:09 -0800, David Kastrup wrote: "Keith OHara" writes: The \oldTransposition you suggested in has the required trickery, and I just re-checked that it works fine. I'd prefer not giving it a name of its own, instead load a Sc

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

"Keith OHara" writes: > On Wed, 27 Feb 2013 00:47:21 -0800, wrote: > >> On 2013/02/27 07:40:59, Keith wrote: >> >>> Oops. It was \oldTransposition but it was not put into LilyPond. >> >> Since the sign of instrumentTransposition has been inverted, it would >> require serious trickery or a sepa

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

\oldTransposition with the previous semantics. The \oldTransposition you suggested in <https://codereview.appspot.com/7303057> has the required trickery, and I just re-checked that it works fine. If I have time I'll point to it in changes.tely, just in case someone used the old method fo

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

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

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

On 2013/02/27 07:40:59, Keith wrote: On 2013/02/27 05:58:58, Keith wrote: > (and @code{\whateverItWasCalled f'} is available Oops. It was \oldTransposition but it was not put into LilyPond. Since the sign of instrumentTransposition has been inverted, it would require serious trickery or

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

On 2013/02/27 05:58:58, Keith wrote: (and @code{\whateverItWasCalled f'} is available Oops. It was \oldTransposition but it was not put into LilyPond. On the one hand, any score that used \transposition p in music that goes through transpose will change its behavior. On the other hand, I

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

LGTM https://codereview.appspot.com/7404046/diff/4001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/7404046/diff/4001/Documentation/changes.tely#newcode71 Documentation/changes.tely:71: would have been the other way round. This and the

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

On 2013/02/25 16:02:41, Trevor Daniels wrote: Not quite, but it is hardly a point worth labouring over. Changes are listed with the most recent at the top, and 'previously' means 'earlier in time', so it ought to refer to items lower in the list. Our changes list is not really ordered in stri

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

On 2013/02/25 00:01:50, dak wrote: Hope I interpreted Trevor's comment correctly. Not quite, but it is hardly a point worth labouring over. Changes are listed with the most recent at the top, and 'previously' means 'earlier in time', so it ought to refer to items lower in the list. Perhaps it

Re: changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

iew.appspot.com/7404046/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/7404046/diff/1/Documentation/changes.tely#newcode83 Documentation/changes.tely:83: would have been the other way round. This and the previous change On 2013/02/24 1

changes.tely: deal with \transposition and instrumentTransposition changes (issue 7404046)

LGTM apart from the suggested change. https://codereview.appspot.com/7404046/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/7404046/diff/1/Documentation/changes.tely#newcode83 Documentation/changes.tely:83: would have been the other

[PATCH] Documentation/changes.tely: refer people to bug tracker for changes in 2.16.1

--- Documentation/changes.tely | 21 +++-- 1 file changed, 19 insertions(+), 2 deletions(-) diff --git a/Documentation/changes.tely b/Documentation/changes.tely index 83db4ea..b59ee7e 100644 --- a/Documentation/changes.tely +++ b/Documentation/changes.tely @@ -35,11 +35,28

changes.tely: declare MacOSX unsupported (issue 5694092)

Maybe add some encouragement for getting involved? http://codereview.appspot.com/5694092/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): http://codereview.appspot.com/5694092/diff/1/Documentation/changes.tely#newcode71 Documentation/changes.tely:71: provide timely

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

Pavel, I pushed for you. author Pavel Roskin Thu, 26 Jan 2012 21:17:13 + (21:17 +) committer James Lowe Thu, 26 Jan 2012 21:19:06 + (21:19 +) commit 224246365f67fb44799fee4eb00e5debea5a35ec Can you close this issue here? James http://codereview.appspot.com/5540058

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

On 2012/01/18 15:13:47, Neil Puttock wrote: http://codereview.appspot.com/5540058/diff/3003/Documentation/changes.tely Done http://codereview.appspot.com/5540058/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

http://codereview.appspot.com/5540058/diff/3003/Documentation/changes.tely File Documentation/changes.tely (right): http://codereview.appspot.com/5540058/diff/3003/Documentation/changes.tely#newcode67 Documentation/changes.tely:67: \override Flag #'color = #red g8 Please put the note on

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

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

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

lgtm http://codereview.appspot.com/5540058/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

. An example is added to show how the flag can be colored now. Also, there was a duplicate "does" in the section about grace notes. Description: changes.tely: mention Flag changes, remove duplicate "does" Please review this at http://codereview.appspot.com/5540058/ Affected

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

OK, my mistake, I didn't read the comments on top of changes.tely. The fixed patch is attached as patch set 2. http://codereview.appspot.com/5540058/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/lis

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

Well I'd say at the top. Many of the changes I have added in the last year have not necessarily gone in the correct 'order'; when someone mentioned that something needed to be added, it went in on the top of the pile. People do follow the changes, so the assumption is that it is current, if we ha

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

Looks good to me, but I wonder about the location. Thanks, Carl http://codereview.appspot.com/5540058/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: changes.tely: mention Flag changes, remove duplicate "does" (issue 5540058)

Looks good to me, but I wonder about the location. Thanks, Carl http://codereview.appspot.com/5540058/diff/1/Documentation/changes.tely File Documentation/changes.tely (right): http://codereview.appspot.com/5540058/diff/1/Documentation/changes.tely#newcode210 Documentation/changes.tely:210

Re: changes.tely for current master?

s.html file, without having to build > the whole documentation? Yes, but I don't know what it is. Try something like: touch Documentation/changes.tely make out=www Documentation/out-www/changes.html I've told people to "try something like xyz" about half a dozen ti

Re: changes.tely for current master?

On Fri, Jul 29, 2011 at 04:24:13PM +, James Lowe wrote: > Hello, > > )It's the right file, it just wasn't updated. I'll do this in a few hours. > > While we're on this file, would it be helpful if we (i.e. I ) > added @refs so that people looking at the changes list can jump > straight to th

Re: changes.tely for current master?

Am Freitag, 29. Juli 2011, 18:17:11 schrieb Graham Percival: > On Fri, Jul 29, 2011 at 11:43:10AM +0200, Reinhold Kainhofer wrote: > > Where is the correct spot to record new features in the 2.15 branch? The > > Documentation/changes.tely says it dispays cchanges between 2.12 a

RE: changes.tely for current master?

Hello, )-Original Message- )From: lilypond-devel-bounces+james.lowe=datacore@gnu.org )[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On )Behalf Of Graham Percival )Sent: 29 July 2011 17:17 )To: Reinhold Kainhofer )Cc: LilyPond Development )Subject: Re: changes.tely

Re: changes.tely for current master?

On Fri, Jul 29, 2011 at 11:43:10AM +0200, Reinhold Kainhofer wrote: > Where is the correct spot to record new features in the 2.15 branch? The > Documentation/changes.tely says it dispays cchanges between 2.12 and 2.14, so > judging from the title this is not the right spot. Or is it

changes.tely for current master?

Where is the correct spot to record new features in the 2.15 branch? The Documentation/changes.tely says it dispays cchanges between 2.12 and 2.14, so judging from the title this is not the right spot. Or is it the right file and the @top node just hastn't been updated when 2.14 was rel

  1   2   >