Hi,
I shall release a new major version 1.3.0 to clean up this and other things,
as soon as possible.
Version 1.3.0 is now available.
Thanks! it's working pretty much perfectly :)
regards,
junichi
--
[EMAIL PROTECTED],netfort.gr.jp} Debian Project
--
To UNSUBSCRIBE, email
The error is in that initially whizzy-error-string is '27' and
whizzytex works. After doing kill-buffer, and revisiting that file,
and reenabling whizzytex-mode, whizzy-error-string is nil.
I suspect there's something fishy going on here with buffer-local
variables.
Thanks for the test.
At Thu, 12 Jan 2006 09:25:53 +0900,
Junichi Uekawa wrote:
Hi,
This must certainly be the problem.
Then, there seems to be an inconsistency on the emacs-version decision
made
at compile time and the one made at load time.
If you look at line 350 of file whizzytex.el
I've looked into the source, and whizzytex.el has the following:
;; More variables
(defconst whizzy-file-prefix _whizzy_)
;; (defvar whizzy-speed-string ?)
;; (defvar whizzy-error-string nil)
(defvar whizzytex-mode-line-string
(list Whizzy
'(:eval (whizzy-get
I shall release a new major version 1.3.0 to clean up this and other things,
as soon as possible.
Version 1.3.0 is now available.
Didier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi,
This must certainly be the problem.
Then, there seems to be an inconsistency on the emacs-version decision made
at compile time and the one made at load time.
If you look at line 350 of file whizzytex.el there are two identical tests,
but one is done at compile time (because
Dear Junichi,
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've verified that they are both nil.
This must certainly be the problem.
Then, there seems
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've verified that they are both nil.
This must certainly be the problem.
Then, there seems
Hi,
This doesn't happen the first time, but seems to happen with the following
sequence:
1. visit a tex buffer
2. enable whizzytex-mode
3. close the tex buffer
4. re-visit a tex buffer
5. enable whizzytex-mode
I'm not sure if this is a debian specific problem.
I cannot
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
Hi,
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)
Package: whizzytex
Version: 1.2.3-4
I'm getting lots of:
error in process filter: Wrong type argument: integerp, nil
with every move within whizzytex-mode.
This doesn't happen the first time, but seems to happen with the following
sequence:
1. visit a tex buffer
2. enable
Package: whizzytex
Version: 1.2.3-4
I'm getting lots of:
error in process filter: Wrong type argument: integerp, nil
with every move within whizzytex-mode.
This doesn't happen the first time, but seems to happen with the following
sequence:
1. visit a tex buffer
2. enable
13 matches
Mail list logo
