Re: [Tex-music] check@staff ... specified range

2023-08-14 Thread Wilfried Lingenberg
21:24 > An: Werner Icking Music Archive > Betreff: Re: [Tex-music] check@staff ... specified range > > On Sat, 12 Aug 2023, Bob Tennent wrote: > > > Jean-Pierre: a better workaround is to add \toctfin before the > > \Changecontext and \ioctfinup q immediately after, thus

Re: [Tex-music] check@staff ... specified range

2023-08-12 Thread Bob Tennent
=== > > --Don > > > > From: Bob Tennent > Sent: Saturday, August 12, 2023 9:45 AM > To: Don Simons > Subject: Re: [Tex-music] check@staff ... specified range > > Don: Can you add octaviation to match Jean-Pierre's example? > > Bob > > On Fri, Aug

Re: [Tex-music] check@staff ... specified range

2023-08-12 Thread Jean-Pierre Coulon
On Sat, 12 Aug 2023, Bob Tennent wrote: Jean-Pierre: a better workaround is to add \toctfin before the \Changecontext and \ioctfinup q immediately after, thus avoiding the cutoctline code in musixtex.tex that seems to be problematical. Works, thanks. I just have to accept the small vertical

Re: [Tex-music] check@staff ... specified range

2023-08-12 Thread Bob Tennent
Jean-Pierre: a better workaround is to add \toctfin before the \Changecontext and \ioctfinup q immediately after, thus avoiding the cutoctline code in musixtex.tex that seems to be problematical. Bob On Fri, Aug 11, 2023 at 11:56 AM Jean-Pierre Coulon wrote: > On Fri, 11 Aug 2023, Bob Tennent

Re: [Tex-music] check@staff ... specified range

2023-08-12 Thread Bob Tennent
Thanks Jean-Pierre. I think I've found the location of the bug: % cutoctline \o@loop \ifdim\o@x<\maxdimen \let\T@ii\n@ii \C@TO \o@x\z@ \fi \repeat in the definition of \z@suspend. Confirm by commenting out those lines (or by removing the octaviation of the example code). But I don't

Re: [Tex-music] check@staff ... specified range

2023-08-12 Thread Jean-Pierre Coulon
it is interesting to compare the output message in my standard situation and when I intentionally do the mistake of saying &\qu j|\qu j for 2nd instrument at line 24. -- Jean-Pierre CoulonThis is TeX, Version 3.14159265 (MiKTeX 20.6.29) (pbstaff.tex (musixtex.tex MusiXTeX(c) 1.24 <2017-02-28>

Re: [Tex-music] check@staff ... specified range

2023-08-12 Thread Jean-Pierre Coulon
On Sat, 12 Aug 2023, Bob Tennent wrote: Jean-Pierre: Can you provide an example involving \leftrepeat or \rightrepeat (so that a change of context doesn't muddy the water)? Bob I have had similar cases with \leftrepeat or \rightrepeat. -- Jean-Pierre Coulon\input musixtex %\input

Re: [Tex-music] check@staff ... specified range

2023-08-12 Thread Bob Tennent
Jean-Pierre: Can you provide an example involving \leftrepeat or \rightrepeat (so that a change of context doesn't muddy the water)? Bob I have had similar cases with \leftrepeat or \rightrepeat. > --- TeX-music@tug.org mailing list If you want to unsubscribe or look

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread Jean-Pierre Coulon
On Fri, 11 Aug 2023, dsim...@roadrunner.com wrote: However, I still don’t know exactly what image Jean-Pierre was trying to create when he first generated the error, since he hasn’t yet provided such an image. I have already provided the image you obtain with \instrumentnumber1. Now suppose

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread Bob Tennent
asn’t yet provided such an image. > > > > --Don > > > > *From:* TeX-Music *On > Behalf Of *Bob Tennent > *Sent:* Friday, August 11, 2023 2:49 PM > *To:* Werner Icking Music Archive > *Subject:* Re: [Tex-music] check@staff ... specified range > > > > Th

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread dsimons
ner@tug.org> > > On Behalf Of Jean-Pierre Coulon > Sent: Friday, August 11, 2023 10:30 AM > To: Werner Icking Music Archive mailto:tex-music@tug.org> > > > Subject: Re: [Tex-music] check@staff ... specified range > > On Fri, 11 Aug 2023, dsim...@roadrunn

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread Bob Tennent
trying to do when you generated the error. > > --Don > > > -Original Message- > > From: TeX-Music > > On Behalf Of Jean-Pierre Coulon > > Sent: Friday, August 11, 2023 10:30 AM > > To: Werner Icking Music Archive > > Subject: Re: [Tex-music] check@staff

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread dsimons
were trying to do when you generated the error. --Don > -Original Message- > From: TeX-Music > On Behalf Of Jean-Pierre Coulon > Sent: Friday, August 11, 2023 10:30 AM > To: Werner Icking Music Archive > Subject: Re: [Tex-music] check@staff ... specified range >

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread Jean-Pierre Coulon
On Fri, 11 Aug 2023, dsim...@roadrunner.com wrote: Jean-Pierre, could you post a .tex file that works and shows exactly what you want? I'm trying to reproduce whatever your problem is with a PMX-generated file, and so far cannot recreate the problem. The following PMX file runs fine: If you

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread dsimons
Jean-Pierre, could you post a .tex file that works and shows exactly what you want? I'm trying to reproduce whatever your problem is with a PMX-generated file, and so far cannot recreate the problem. The following PMX file runs fine: == 3 2 3 4 3 4 0 0 1 2 20 0 ttt .\ AS0- gd24

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread Bob Tennent
And it may help a debugger to know that replacing \xbar by \bar or \zbar or \zzbar all fail. Good luck! Bob On Fri, Aug 11, 2023 at 11:56 AM Jean-Pierre Coulon wrote: > On Fri, 11 Aug 2023, Bob Tennent wrote: > > > The following is a workaround: > > > > \setdoublebar% > > \xbar% > >

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread Jean-Pierre Coulon
On Fri, 11 Aug 2023, Bob Tennent wrote: The following is a workaround: \setdoublebar% \xbar% \generalsignature3% \changesignature% This is a semi-workaround because with xbar you prenvent a linebreak where I have one :-) -- Jean-Pierre Coulon ---

Re: [Tex-music] check@staff ... specified range

2023-08-11 Thread Bob Tennent
The following is a workaround: \setdoublebar% \xbar% \generalsignature3% \changesignature% This might help someone find the bug which seems to be deep inside musixtex.tex and beyond my patience to track down. If you find it, let me know and I'll make the correction. Bob On Fri, Aug 11, 2023