Dan Eble <d...@faithful.be> writes: > Back to the bug: I appreciate that it’s not obvious what to do with > Change_iterator, but is there anything obvious that could be done to > NullVoice that (without defeating its purpose) would cause \change Staff to > pass over it?
Current branch: contextchange Tracker issue: 5116 (https://sourceforge.net/p/testlilyissues/issues/5116/) Rietveld issue: 322820043 (https://codereview.appspot.com/322820043) Issue description: Allow \change to same context type The \change command no longer refuses to change the parent of a context when the context itself would be of the proper type to change to. This allows changing the parent of a context that could be nested, like StaffGroup in StaffGroup or NullVoice in Staff (since NullVoice is also aliased to Staff). Could you rework your almost minimal example into a regtest? Those give me much more of a headache than most code changes since there is no "obviously best" regtest to aim for. Thanks -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
