Hi Junichi,
> GNU Emacs 21.4.1 (x86_64-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
> of 2005-10-04 on athlon, modified by Debian
This is more recent than mine 21.3.1.
I'll see if I can have access to a 21.4.1 version and if possible on Debian.
> > - Does the message disappears once the slice is correct?
>
> I think that is the case. It continues to beep and give me error until
> whizzytex has finished with updating the slice.
OK.
The problem you mention seems abnormal.
But I cannot localize it without beeing able to reproduce it.
Since when is this broken?
> > - Have you checked version whizzytex-xxx ?
>
> Not yet.
Maybe you could try that, since I really can't reproduce the bug nor on the
current version, nor on an older version.
> > - Does the bug persists if you enable whizzytex-mode in debug more the
> > second time? (whizzytex-mode 16): you should then have a better trace
> > that localize the error in the source code.
>
> Okay, that would be good.
>
> It seems to give me:
>
> Debugger entered--Lisp error: (wrong-type-argument integerp nil)
> whizzy-get(nil)
If whizzy-get is called with nil, this is really an error.
But, I don't see how we can get there.
Strangely, the trace does not show "whizzy-running-message" in the call
stack.
Even more strangely, I don't see how write-region called from
whizzy-filter-ouput can call back whizzy-get.
So I am a bit lost here.
> write-region(1 5844
> "/home/dancer/DEBIAN/whizzytex/whizzytex-1.2.3/debian/testfile/_whizzy_test1_d/output/initialization")
> whizzy-filter-output("<Initialization succeeded, entering loop>\n")
> run-hook-with-args(whizzy-filter-output "<Initialization succeeded,
> entering loop>\n")
> comint-output-filter(#<process test1.tex> "<Initialization succeeded,
> entering loop>\n")
> sleep-for(1)
> whizzy-mode-on(16)
> whizzytex-mode(16)
> eval((whizzytex-mode 16))
> eval-expression((whizzytex-mode 16) nil)
> call-interactively(eval-expression)
May you check that
whizzy-error-string
whizzy-speed-string
are both defined and integers (resp. 27 and 28, but the value does not
matter) in the buffer.
I don't know what more I can do as long as I cannot reproduce the problem.
Maybe waiting for others to report the same error and hope for additional
information...
Didier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
