Re: [Tex-music] MusiXTeX or Tex bug or feature?
>|> Please do not send html mail to the list. >| >|Hum, but you're doing so! ;-) Sorry. I had to redirect the message to gmail to read it and gmail decided to use html. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
On Tue, 12 Jun 2018, Bob Tennent wrote: Please do not send html mail to the list. Hum, but you're doing so! ;-) -- Jean-Pierre --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
Please send us the source file and *exactly* how you compiled it; include the .log files. Please do not send html mail to the list. On Sunday, June 10, 2018, "Jörg Hudelmaier" wrote: > I have the same problem. I press RETURN every time the \inline= appears. > This may come multiple times in a row. But in the end the file compiles. > > Jörg Hudelmaier > > *Gesendet:* Samstag, 09. Juni 2018 um 21:15 Uhr > *Von:* "Jean-Pierre Coulon" > *An:* "Werner Icking Music Archive" > *Betreff:* [Tex-music] MusiXTeX or Tex bug or feature? > When I musixtex a file I obtain the message \inline= and I am unable to > enter any character. X gives nothing. All I can do is to kill the command > prompt window I was working with. Any other solution? Bye, Jean-Pierre > Coulon --- TeX-music@tug.org mailing list If > you want to unsubscribe or look at the archives, go to > http://tug.org/mailman/listinfo/tex-music > --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
I have the same problem. I press RETURN every time the \inline= appears. This may come multiple times in a row. But in the end the file compiles. Jörg Hudelmaier Gesendet: Samstag, 09. Juni 2018 um 21:15 Uhr Von: "Jean-Pierre Coulon" An: "Werner Icking Music Archive" Betreff: [Tex-music] MusiXTeX or Tex bug or feature? When I musixtex a file I obtain the message \inline= and I am unable to enter any character. X gives nothing. All I can do is to kill the command prompt window I was working with. Any other solution? Bye, Jean-Pierre Coulon --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
Bob Tennent wrote: > >|I've more commonly seen this using OpusTeX - it's usually >|a sign that > either the .mx2 file is out-of-sync with the > >|.mx1 file, as Bob noted. > > either ... or what? Oops - the "either" was from an earlier edit which I clearly forgot to delete! > >|Deleting the .mx1 *and* .mx2 > >|file should clear it, otherwise there's a bug. > >| > >|If memory serves, from writing TeX-based version of >|musixflx many years > ago, turning that case into an >|elegant error message is quite hard. > > Jean-Pierre, David: I've not been able to reproduce this "feature". If you > can give me a more detailed hint on how to reproduce it, I can try to have > musixtex.lua avoid the problem or produce a suitable message. The script > currently removes any existing basename.mx2 file before a first pass and > removes both mx1 and mx2 files after processing (unless intermediate files > are to be retained). I _think_ that you can make it happen if you've added extra music to a TeX file resulting in additional systems and attempt to do a first pass without deleting the .mx2 file first. As I say, I'm fairly sure I'd only seen it with OpusTeX (and so probably an older/diverged three-pass system). Best, David --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
CTRL-X is rarely the command exit anything - CTRL+C should terminate TeX, unless something's really broken. Yes. I typed this mail too fast! I've more commonly seen this using OpusTeX - it's usually a sign that either the .mx2 file is out-of-sync with the .mx1 file, as Bob noted. Deleting the .mx1 *and* .mx2 file should clear it, otherwise there's a bug. I am unable to reproduce the bug with the file I was using yesterday. Next time I will attach it with the .log and .mx? files. Can't say at which of the 3 passes this was. :-( Jean-Pierre Coulon --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
>|I've more commonly seen this using OpusTeX - it's usually >|a sign that either the .mx2 file is out-of-sync with the >|.mx1 file, as Bob noted. either ... or what? >|Deleting the .mx1 *and* .mx2 >|file should clear it, otherwise there's a bug. >| >|If memory serves, from writing TeX-based version of >|musixflx many years ago, turning that case into an >|elegant error message is quite hard. Jean-Pierre, David: I've not been able to reproduce this "feature". If you can give me a more detailed hint on how to reproduce it, I can try to have musixtex.lua avoid the problem or produce a suitable message. The script currently removes any existing basename.mx2 file before a first pass and removes both mx1 and mx2 files after processing (unless intermediate files are to be retained). Bob --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
Jean-Pierre Coulon wrote: > When I musixtex a file I obtain the message \inline= and I am unable to enter > any character. X gives nothing. All I can do is to kill the command > prompt window I was working with. CTRL-X is rarely the command exit anything - CTRL+C should terminate TeX, unless something's really broken. I've more commonly seen this using OpusTeX - it's usually a sign that either the .mx2 file is out-of-sync with the .mx1 file, as Bob noted. Deleting the .mx1 *and* .mx2 file should clear it, otherwise there's a bug. If memory serves, from writing TeX-based version of musixflx many years ago, turning that case into an elegant error message is quite hard. David --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
>|When I musixtex a file I obtain the message \inline= and I am unable to >|enter any character. X gives nothing. All I can do is to kill the >|command prompt window I was working with. >| >|Any other solution? Jean-Pierre: In musixtex.tex, the section that defines macros to set up the second pass has: % \inline expands to \lineset#1#2#3#4#5, so define the latter followed by a definition of \lineset. Is it possible that you haven't used musixflx properly? Bob T. --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
Re: [Tex-music] MusiXTeX or Tex bug or feature?
>|When I musixtex a file I obtain the message \inline= and I am unable to >|enter any character. X gives nothing. All I can do is to kill the >|command prompt window I was working with. Jean-Pierre: What file is "a file"? Does your musixtex work on the small examples available at http://icking-music-archive.org/software/htdocs/Introduction.html#SECTION00011000 If so, then you'll have to find the problem with your file. Bob --- TeX-music@tug.org mailing list If you want to unsubscribe or look at the archives, go to http://tug.org/mailman/listinfo/tex-music
