10:58 p.m.
XEmacs 21.5.b18 (+CVS20050203)
The forward-paragraph and backward-paragraph commands now fail with the
error
Invalid byte code: variable reference to constant symbol, nil.
This just began since the recent mega patch that included paragraph.el
Other motion commands do seem to work and the companion sexp movements still
work.
I know how to get debug in a function I have displayed, but how do I debug a
funtion that only works in a non-lisp (text-mode) buffer?
--
rdr
11:08 p.m.
New subject: Problems with text-mode paragraph movement MORE INFO
I wrote the following a few minutes ago, then remembered how to get
debugging to work. When StackTrace on Error is set, the function does not
fail. So I think this is a ByteCompiler error.
Any suggestions for continued troubleshooting?
Mon, 7 Feb 2005 (17:58 -0500 UTC) robert delius royar wrote:
XEmacs 21.5.b18 (+CVS20050203)
The forward-paragraph and backward-paragraph commands now fail with the error
Invalid byte code: variable reference to constant symbol, nil.
This just began since the recent mega patch that included paragraph.el
Other motion commands do seem to work and the companion sexp movements still
work.
I know how to get debug in a function I have displayed, but how do I debug a
funtion that only works in a non-lisp (text-mode) buffer?
--
rdr
3:18 p.m.
New subject: Problems with text-mode paragraph movement MORE INFO
robert delius royar <xemacs(a)frinabulax.org> wrote:
I wrote the following a few minutes ago, then remembered how to get
debugging
to work. When StackTrace on Error is set, the function does not fail. So I
think this is a ByteCompiler error.
Any suggestions for continued troubleshooting?
It appears to be the let and let* forms that are being miscompiled. Try
byte-compiling this:
(defun some-function ()
"Docstring."
(let ((some-var 0))
t))
For me, this produces the following in *Compile-Log-Show*:
Compiling file /tmp/paragraphs.el at Tue Feb 8 09:15:20 2005
While compiling some-function:
** variable some-var bound but not referenced
While compiling some-function:
!! Invalid byte code (("variable reference to constant symbol" nil))
I'll try to look at this later today if nobody beats me to it.
--
Jerry James
http://www.ittc.ku.edu/~james/
3:30 p.m.
New subject: Problems with text-mode paragraph movement MORE INFO
It appears to be the let and let* forms that are being miscompiled.
Try byte-compiling this:
(defun some-function () "Docstring." (let ((some-var 0))
t))
For me, this produces the following in *Compile-Log-Show*:
Compiling file /tmp/paragraphs.el at Tue Feb 8 09:15:20 2005 While
compiling some-function: ** variable some-var bound but not referenced
While compiling some-function: !! Invalid byte code (("variable
reference to constant symbol" nil))
I'm using CVS-20050202, native win32. I don't see any of these problems.
Fabrice
4:23 p.m.
New subject: Problems with text-mode paragraph movement MORE INFO
Tue, 8 Feb 2005 (09:18 -0600 UTC) Jerry James wrote:
robert delius royar <xemacs(a)frinabulax.org> wrote:
> I wrote the following a few minutes ago, then remembered how to get debugging
> to work. When StackTrace on Error is set, the function does not fail. So I
> think this is a ByteCompiler error.
>
> Any suggestions for continued troubleshooting?
It appears to be the let and let* forms that are being miscompiled. Try
byte-compiling this:
(defun some-function ()
"Docstring."
(let ((some-var 0))
t))
For me, this produces the following in *Compile-Log-Show*:
Compiling file /tmp/paragraphs.el at Tue Feb 8 09:15:20 2005
While compiling some-function:
** variable some-var bound but not referenced
While compiling some-function:
!! Invalid byte code (("variable reference to constant symbol" nil))
I'll try to look at this later today if nobody beats me to it.
Compiling the *scratch* buffer (byte-compile-buffer) with your example gives
me the same error on Mac OSX. The problem may be related to a variable
multiple-lines which is no longer used but which is in the let statement at
line 241. I will try this patch:
diff -U0 -r1.10 paragraphs.el
--- lisp/paragraphs.el 2005/02/03 21:27:59 1.10
+++ lisp/paragraphs.el 2005/02/08 16:22:30
＠＠ -39,0 +40,2 ＠＠
+(require 'easy-mmode)
+
＠＠ -239 +241 ＠＠
- (let (multiple-lines)
+ ;; (let (multiple-lines)
＠＠ -244,2 +246,2 ＠＠
- (unless (= (point) start)
- (setq multiple-lines t))
+ ;; (unless (= (point) start)
+ ;; (setq multiple-lines t))
＠＠ -256 +258 ＠＠
- (not (bobp)))
+ (not (bobp)) ;;)
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
4:59 p.m.
New subject: Problems with text-mode paragraph movement MORE INFO
Tue, 8 Feb 2005 (11:23 -0500 UTC) robert delius royar wrote:
The problem may be related to a variable
multiple-lines which is no longer used but which is in the let statement at
line 241. I will try this patch:
diff -U0 -r1.10 paragraphs.el
--- lisp/paragraphs.el 2005/02/03 21:27:59 1.10
+++ lisp/paragraphs.el 2005/02/08 16:22:30
＠＠ -39,0 +40,2 ＠＠
+(require 'easy-mmode)
+
＠＠ -239 +241 ＠＠
- (let (multiple-lines)
+ ;; (let (multiple-lines)
＠＠ -244,2 +246,2 ＠＠
- (unless (= (point) start)
- (setq multiple-lines t))
+ ;; (unless (= (point) start)
+ ;; (setq multiple-lines t))
＠＠ -256 +258 ＠＠
- (not (bobp)))
+ (not (bobp)) ;;)
No dice, the error persists. Simply loading the source file fixes the
error as does "instrumenting the function for debugging."
--
Dr. Robert Delius Royar Associate Professor of English
Morehead State University Morehead, Kentucky
7038
days inactive
7039
days old
5 comments
3 participants
participants (3)
-
Fabrice Popineau -
Jerry James -
robert delius royar