wrong-type-argument when ~/.emacs is byte compiled

wrong-type-argument when ~/.emacs is byte compiled

[Esben Stien]

I have this code in my ~/.emacs to automatically byte compile when I
save the file.

(defun autocompile nil
  "compile itself if ~/.emacs"
  (interactive)
  (require 'bytecomp)
  (if (string= (buffer-file-name) (expand-file-name (concat default-directory ".emacs")))
(byte-compile-file (buffer-file-name))))
  (add-hook 'after-save-hook 'autocompile)
(defconst animate-n-steps 3)

Now, when I try to start my function irc, defined: 

(defmacro de-erc-connect (command server port nick)
  "Create interactive command `command', for connecting to an IRC server. The command uses interactive mode if passed an argument."
  (fset command
	`(lambda (arg)
	   (interactive "p")
	   (if (not (= 1 arg))
	       (erc-select ,server ,port ,nick)
	     (erc ,server ,port ,nick ,erc-user-full-name t)))))

(autoload 'erc "erc" "" t)
(autoload 'erc-select "erc" "" t)
(de-erc-connect erc-fn "irc.gnu.org" 6667 "b0ef")

(defun erc-autojoin-channels (server nick)
  (dolist (l erc-autojoin-channels-alist)
    (when (string-match (car l) server)
      (dolist (chan (cdr l))
        (erc-send-command (concat "join " chan))))))
(add-hook 'erc-after-connect 'erc-autojoin-channels)

 (defun irc ()
   "Start to waste time on IRC with ERC."
   (interactive)
   (call-interactively 'erc-fn))

I get, when trying to M-x irc:

Debugger entered--Lisp error: (wrong-type-argument commandp erc-fn)
  call-interactively(erc-fn)
  irc()
  call-interactively(irc)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

Now, everything works if I just take out the auto compile function or
rm the ~/.emacs.elc file.

Anyone have any pointers on what to look at?

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
          [sip|iax]:   e     e 
           jid:b0ef@    n     n

Re: wrong-type-argument when ~/.emacs is byte compiled

[Stefan Monnier]

> I have this code in my ~/.emacs to automatically byte compile when I
> save the file.

This is a bad idea.  If your .emacs contains something worth byte-compiling,
it should be moved outside .emacs into its own file.  I.e. you're just
wasting your time with such a hack.


        Stefan

Re: wrong-type-argument when ~/.emacs is byte compiled

[Thien-Thi Nguyen]

Esben Stien <b0ef@esben-stien.name> writes:

>    (call-interactively 'erc-fn)

that is a strange approach.

unless you are "manually" supplying a prefix arg, you
might as well just use a straightforward function call.

thi

Re: wrong-type-argument when ~/.emacs is byte compiled

[Esben Stien]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> If your .emacs contains something worth byte-compiling, it should be
> moved outside .emacs into its own file.

Aiight, I'll do that. 

-- 
Esben Stien is b0ef@e     s      a             
         http://www. s     t    n m
          irc://irc.  b  -  i  .   e/%23contact
          [sip|iax]:   e     e 
           jid:b0ef@    n     n

Re: wrong-type-argument when ~/.emacs is byte compiled

[Johan Bockgård]

Esben Stien <b0ef@esben-stien.name> writes:

> (defmacro de-erc-connect (command server port nick)
>   "Create interactive command `command', for connecting to an IRC
>   server. The command uses interactive mode if passed an argument."
>   (fset command
>       `(lambda (arg) [...]

This macro is broken.

-- 
Johan Bockgård

Re: wrong-type-argument when ~/.emacs is byte compiled

[Kevin Rodgers]

Esben Stien wrote:
 > I have this code in my ~/.emacs to automatically byte compile when I
 > save the file.
 >
 > (defun autocompile nil
 >   "compile itself if ~/.emacs"
 >   (interactive)
 >   (require 'bytecomp)
 >   (if (string= (buffer-file-name) (expand-file-name (concat 
default-directory ".emacs")))
 > (byte-compile-file (buffer-file-name))))
 >   (add-hook 'after-save-hook 'autocompile)

That will automatically byte compile .emacs files in any directory.

-- 
Kevin Rodgers