lilypond-auto
[Top][All Lists]

## [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5032 Usin

 From: Auto mailings of changes to Lily Issues Subject: [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5032 Using \chords rather than \chordmode etc renders \with ineffective. Date: Sun, 15 Jan 2017 12:07:38 +0000

This is interesting in as much as my original analysis would have predicted case (1) having identical outcome.

However, `\displayLilyMusic` tells me that `\chords` is actually equivalent to `\new ChordNames` ... rather than `\context ChordNames` ... like I stated.

As a result, it will not hook into a preexisting `ChordNames` context. Probably the saner option anyway since people would not expect

```<<
\chords { ... }
\chords { ... }
>>
```

to mash up things into a single context.

[issues:#5032] Using \chords rather than \chordmode etc renders \with ineffective.

Status: New
Created: Sat Jan 14, 2017 09:16 PM UTC by Trevor Daniels
Last Updated: Sun Jan 15, 2017 06:44 AM UTC
Owner: Trevor Daniels

If the \chords command is used to set the input mode (rather than the more usual \chordmode command - see NR 5.4.1) context amendments within a \with command are ineffective. This is because the context has already been created implicitly by the \chords command - before the \with command is processed. The same applies to other short-hands for creating contexts such as \drums, \figures, etc. This should be documented.

(Thanks to Thomas Morley (Harm) for the explanation.)

Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.

```------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
```_______________________________________________