> OTOH it's closer to what I meant by "turn it into a macro" (in the
> comment that prompted you to look into this whole thing). Ideally
> define-generic-mode should (just like define-derived-mode does)
> generate stand-alone code which does not require generic.el.
I considere
Stefan Monnier <[EMAIL PROTECTED]> writes:
[...]
>>> Another option is to evaluate those arguments before you plug them
>>> in the body of your major mode function, so they're only evaluated
>>> once, when the major mode is defined, thus reproducing the
>>> "pre-macro" behavior.
>
>> Considering
Experience proves the doc is wrong. What I found instead is that `form'
can't be used after &define. I think the bug is not that things don't work
with `&define' but that edebug should burp on a spec that uses both &define
and `form' (or `body' for that matter).
Could you fix thi
>> Try (debug (sexp def-form def-form def-form form def-form [&optional
>> stringp]))
> This does indeed work. (The brackets are not necessary, are they?)
I find it good practice to always use the brackets, but you're right, it's
not necessary.
> The node "Specification List" in the lisp manua
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> (declare (debug (sexp form form form form form &optional stringp)))
>
>> X(define-generic-mode my-mode
>> (list ?# ?% (+ 50 9))
>> (list "abba" "ebbe" (concat "ob" "bo"))
>> nil
>> X(list "\\.mm\\'")X
>> nil
>> "This is My mode.")X
>
> That
> (declare (debug (sexp form form form form form &optional stringp)))
> X(define-generic-mode my-mode
> (list ?# ?% (+ 50 9))
> (list "abba" "ebbe" (concat "ob" "bo"))
> nil
> X(list "\\.mm\\'")X
> nil
> "This is My mode.")X
That's because when you execute the call to define-generic-m
I have problems writing a debug declaration for define-generic-mode.
Maybe someone can help me?
define-generic-mode is defined like this:
(defmacro define-generic-mode (mode comment-list keyword-list
font-lock-list auto-mode-list
