* elisp byte compilation problem
@ 2003-05-22 15:39 Javier Oviedo
2003-05-22 18:00 ` Javier Oviedo
0 siblings, 1 reply; 9+ messages in thread
From: Javier Oviedo @ 2003-05-22 15:39 UTC (permalink / raw)
Hello all.
I have found some strange behavior when I compile certain elisp files and
then load them...
=============================
One example is clearcase.el. I have (require 'clearcase) in my .emacs file.
Without byte compiling everything works fine...meaning that I in the menubar
there is a clearcase menu that I can access without problem. As soon as I
byte compile, the clearcase menu disappears from the menu bar. I can't
explain this. I know very little about elisp and therefore need some help.
ctypes.el size is 260598
ctypes.elc size if 632 ==> something is wrong here.
=============================
Another example is with ctype.el. I have the following in my .emacs file:
(require 'ctypes)
(setq ctypes-write-types-at-exit t)
(ctypes-read-file "C:/data/joviedo/Emacs/site-lisp_21_2/_ctypes" nil t t)
(ctypes-auto-parse-mode 1)
When ctypes in not byte compiled, everything works fine. With ctypes byte
compiled I get the following error when I load a file...
File mode specification error: (void-function ctypes-read-file)
run-hooks: Symbol's function definition is void: ctypes-find-file-hook
ctypes.el size is 62607
ctypes.elc size if 814 ==> something is wrong here.
=============================
I am using Emacs 21.2 on WinXP
Thanks In Advance!
--
Javier
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-22 15:39 elisp byte compilation problem Javier Oviedo
@ 2003-05-22 18:00 ` Javier Oviedo
2003-05-23 6:09 ` Kai Großjohann
0 siblings, 1 reply; 9+ messages in thread
From: Javier Oviedo @ 2003-05-22 18:00 UTC (permalink / raw)
I just discovered that for almost any .el I compile I see problems. Since I
hardly change things outside of my .emacs most of my .elc files have been
around for some time...I am just noticing this problem now.
I had to re-byte compile folding.el(I have had byte compiled for the last
year and had no problems) after making a one line change. The .elc size
dropped from 84,072 bytes to 607 bytes. Obviously, something is wrong with
the byte compilation itself.
What could be going on here? Thanks!!
--
=======
Javier
"Javier Oviedo" <email_joviedo@yahoo.com> wrote in message
news:baiqrs$3ot$1@home.itg.ti.com...
> Hello all.
>
> I have found some strange behavior when I compile certain elisp files and
> then load them...
>
> =============================
> One example is clearcase.el. I have (require 'clearcase) in my .emacs
file.
> Without byte compiling everything works fine...meaning that I in the
menubar
> there is a clearcase menu that I can access without problem. As soon as I
> byte compile, the clearcase menu disappears from the menu bar. I can't
> explain this. I know very little about elisp and therefore need some help.
>
> ctypes.el size is 260598
> ctypes.elc size if 632 ==> something is wrong here.
> =============================
> Another example is with ctype.el. I have the following in my .emacs file:
> (require 'ctypes)
> (setq ctypes-write-types-at-exit t)
> (ctypes-read-file "C:/data/joviedo/Emacs/site-lisp_21_2/_ctypes" nil t
t)
> (ctypes-auto-parse-mode 1)
>
> When ctypes in not byte compiled, everything works fine. With ctypes byte
> compiled I get the following error when I load a file...
>
> File mode specification error: (void-function ctypes-read-file)
> run-hooks: Symbol's function definition is void: ctypes-find-file-hook
>
> ctypes.el size is 62607
> ctypes.elc size if 814 ==> something is wrong here.
> =============================
>
> I am using Emacs 21.2 on WinXP
>
> Thanks In Advance!
>
> --
> Javier
>
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-22 18:00 ` Javier Oviedo
@ 2003-05-23 6:09 ` Kai Großjohann
2003-05-23 13:44 ` Javier Oviedo
0 siblings, 1 reply; 9+ messages in thread
From: Kai Großjohann @ 2003-05-23 6:09 UTC (permalink / raw)
"Javier Oviedo" <email_joviedo@yahoo.com> writes:
> I just discovered that for almost any .el I compile I see problems. Since I
> hardly change things outside of my .emacs most of my .elc files have been
> around for some time...I am just noticing this problem now.
What does the *Messages* buffer say after you do M-x
byte-compile-file RET? What does the *.elc file contain after this?
--
This line is not blank.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-23 6:09 ` Kai Großjohann
@ 2003-05-23 13:44 ` Javier Oviedo
2003-05-23 16:51 ` Kai Großjohann
2003-05-23 17:28 ` Kevin Rodgers
0 siblings, 2 replies; 9+ messages in thread
From: Javier Oviedo @ 2003-05-23 13:44 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
These errors did not start happening until recently...
I byte compiled folding.el and I see the following in the *Messages* buffer:
Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...
Folding buffer... done
Folding buffer... done
File local-variables error: (error "Local variables entry is missing the
prefix")
Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...done
Wrote c:/data/joviedo/Emacs/site-lisp_21_2/folding.elc
Byte-Compile: 1 file.
The folding.elc file shows the following:
;ELC\x14
;;; Compiled by a0850403@GT64V7121 on Fri May 23 09:35:11 2003
;;; from file c:/data/joviedo/Emacs/site-lisp_21_2/folding.el
;;; in Emacs version 21.2.1
;;; with bytecomp version 2.85
;;; with all optimizations.
;;; This file uses dynamic docstrings, first added in Emacs 19.29.
(if (and (boundp 'emacs-version)
(< (aref emacs-version (1- (length emacs-version))) ?A)
(or (and (boundp 'epoch::version) epoch::version)
(string-lessp emacs-version "19.29")))
(error "`folding.el' was compiled for Emacs 19.29 or later"))
Thanks for your help!
--
=======
Javier
"Kai Großjohann" <kai.grossjohann@gmx.net> wrote in message
news:84el2qgpnp.fsf@lucy.is.informatik.uni-duisburg.de...
> "Javier Oviedo" <email_joviedo@yahoo.com> writes:
>
> > I just discovered that for almost any .el I compile I see problems.
Since I
> > hardly change things outside of my .emacs most of my .elc files have
been
> > around for some time...I am just noticing this problem now.
>
> What does the *Messages* buffer say after you do M-x
> byte-compile-file RET? What does the *.elc file contain after this?
>
> --
> This line is not blank.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-23 13:44 ` Javier Oviedo
@ 2003-05-23 16:51 ` Kai Großjohann
2003-05-23 17:28 ` Kevin Rodgers
1 sibling, 0 replies; 9+ messages in thread
From: Kai Großjohann @ 2003-05-23 16:51 UTC (permalink / raw)
"Javier Oviedo" <email_joviedo@yahoo.com> writes:
> I byte compiled folding.el and I see the following in the *Messages* buffer:
>
> Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...
> Folding buffer... done
> Folding buffer... done
> File local-variables error: (error "Local variables entry is missing the
> prefix")
> Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...done
> Wrote c:/data/joviedo/Emacs/site-lisp_21_2/folding.elc
> Byte-Compile: 1 file.
Okay, now show us the last few lines of the file folding.el. I think
the file contains the words "Local Variables" near the end -- show us
that line and the rest of the file.
--
This line is not blank.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-23 13:44 ` Javier Oviedo
2003-05-23 16:51 ` Kai Großjohann
@ 2003-05-23 17:28 ` Kevin Rodgers
2003-05-23 18:33 ` Javier Oviedo
1 sibling, 1 reply; 9+ messages in thread
From: Kevin Rodgers @ 2003-05-23 17:28 UTC (permalink / raw)
Javier Oviedo wrote:
> These errors did not start happening until recently...
>
> I byte compiled folding.el and I see the following in the *Messages* buffer:
>
> Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...
> Folding buffer... done
> Folding buffer... done
> File local-variables error: (error "Local variables entry is missing the
> prefix")
> Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...done
> Wrote c:/data/joviedo/Emacs/site-lisp_21_2/folding.elc
> Byte-Compile: 1 file.
Well, what does the file-local variables section of folding.el look like?
--
<a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-23 17:28 ` Kevin Rodgers
@ 2003-05-23 18:33 ` Javier Oviedo
2003-05-23 20:56 ` Kai Großjohann
0 siblings, 1 reply; 9+ messages in thread
From: Javier Oviedo @ 2003-05-23 18:33 UTC (permalink / raw)
I'm sorry but I'm not sure if I'm giving the correct info, but here goes...I
did a occur on "local-variables" and this is what I get:
Why would there not be an error when using .el version if something is truly
wrong with a local-variable? Thanks.
31 lines matching "local-variable" in buffer folding.el.
708:;; - (folding-set-local-variables): 2.61 New. Now it is possible to
710:;; - (folding-mode): 2.61 Call `folding-set-local-variables'
712:;; - `folding-set-local-variables'
1283:;; utilize kill-all-local-variables-hooks with defadvice around
1284:;; kill-all-local-variables ...
1287:;; kill-all-local-variables-hooks :! v, moved to variable section
2130:Use function `folding-set-local-variables' is you change the current
mode's
2795: (kill-local-variable 'folding-mode-string)
2796: (make-local-variable 'folding-mode-string)
2859: (and (assq 'folded-file (buffer-local-variables))
2862: (kill-local-variable 'folded-file)
2875:If `inhibit-local-variables' is non-nil, this will not happen
regardless
2939:(defun folding-set-local-variables ()
2944: (set (make-local-variable 'folding-stack) nil)
2945: (make-local-variable 'folding-top-mark)
2946: (make-local-variable 'folding-secondary-top-mark)
2947: (make-local-variable 'folding-top-regexp)
2948: (make-local-variable 'folding-bottom-mark)
2949: (make-local-variable 'folding-bottom-regexp)
2950: (make-local-variable 'folding-regexp)
3010: first read (see `hack-local-variables').
3135: (folding-set-local-variables)
3209: (set (make-local-variable 'folding-top-mark)
3211: (set (make-local-variable 'folding-bottom-mark)
3213: (set (make-local-variable 'folding-secondary-top-mark)
3215: (set (make-local-variable 'folding-top-regexp)
3218: (set (make-local-variable 'folding-bottom-regexp)
3221: (set (make-local-variable 'folding-regexp)
4495: (buffer-local-variables))
4638: (make-local-variable 'minibuffer-local-isearch-map)
4686: (kill-local-variable 'minibuffer-local-isearch-map)
--
=======
Javier
"Kevin Rodgers" <ihs_4664@yahoo.com> wrote in message
news:3ECE5A50.6010709@yahoo.com...
> Javier Oviedo wrote:
>
> > These errors did not start happening until recently...
> >
> > I byte compiled folding.el and I see the following in the *Messages*
buffer:
> >
> > Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...
> > Folding buffer... done
> > Folding buffer... done
> > File local-variables error: (error "Local variables entry is missing the
> > prefix")
> > Compiling c:/data/joviedo/Emacs/site-lisp_21_2/folding.el...done
> > Wrote c:/data/joviedo/Emacs/site-lisp_21_2/folding.elc
> > Byte-Compile: 1 file.
>
> Well, what does the file-local variables section of folding.el look like?
>
>
> --
> <a href="mailto:<kevin.rodgers@ihs.com>">Kevin Rodgers</a>
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-23 18:33 ` Javier Oviedo
@ 2003-05-23 20:56 ` Kai Großjohann
2003-05-27 13:40 ` Javier Oviedo
0 siblings, 1 reply; 9+ messages in thread
From: Kai Großjohann @ 2003-05-23 20:56 UTC (permalink / raw)
"Javier Oviedo" <email_joviedo@yahoo.com> writes:
> I'm sorry but I'm not sure if I'm giving the correct info, but here goes...I
> did a occur on "local-variables" and this is what I get:
Search for the string "Local variables:", including the colon but
without the quotes. You will see that it occurs twice. The first
occurrence is missing the "end" line. I guess it confuses Emacs.
I propose to replace the first "Local variables:" with
"Local\ variables:" which should mask the problem. Also, maybe
suggest to the author to make this change and to add an "end:" line
to that snippet.
--
This line is not blank.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: elisp byte compilation problem
2003-05-23 20:56 ` Kai Großjohann
@ 2003-05-27 13:40 ` Javier Oviedo
0 siblings, 0 replies; 9+ messages in thread
From: Javier Oviedo @ 2003-05-27 13:40 UTC (permalink / raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
I added the backslash and it had no affect. What else could be going wrong?
--
Javier
"Kai Großjohann" <kai.grossjohann@gmx.net> wrote in message
news:844r3lo00d.fsf@lucy.is.informatik.uni-duisburg.de...
> "Javier Oviedo" <email_joviedo@yahoo.com> writes:
>
> > I'm sorry but I'm not sure if I'm giving the correct info, but here
goes...I
> > did a occur on "local-variables" and this is what I get:
>
> Search for the string "Local variables:", including the colon but
> without the quotes. You will see that it occurs twice. The first
> occurrence is missing the "end" line. I guess it confuses Emacs.
>
> I propose to replace the first "Local variables:" with
> "Local\ variables:" which should mask the problem. Also, maybe
> suggest to the author to make this change and to add an "end:" line
> to that snippet.
>
> --
> This line is not blank.
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2003-05-27 13:40 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-22 15:39 elisp byte compilation problem Javier Oviedo
2003-05-22 18:00 ` Javier Oviedo
2003-05-23 6:09 ` Kai Großjohann
2003-05-23 13:44 ` Javier Oviedo
2003-05-23 16:51 ` Kai Großjohann
2003-05-23 17:28 ` Kevin Rodgers
2003-05-23 18:33 ` Javier Oviedo
2003-05-23 20:56 ` Kai Großjohann
2003-05-27 13:40 ` Javier Oviedo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).