> Rewriting the mode to use define-derived-mode can always be done later
> when one has more time and has no other, more urgent, things to do.
When was the last time this happened to you?
Stefan
___
Emacs-devel mailing list
Emacs-devel@gnu.or
Sorry, I did not really mean to have this "Subject" field for this
thread. That address was supposed to be a CC. I must have messed
things up one way or the other. I only noticed now.
Sincerely,
Luc.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
Stefan Monnier wrote:
If at all possible, please use define-derived-mode which results in
cleaner code and neatly hides those details.
The problem is that rewriting a mode to use define-derived-mode has to
be done carefully and takes time. Otherwise, there is the risk of
introducing bugs.
> Michael), once I know how we want to handle them. We could make them
> all use define-derived-mode, but that has to be done carefully and has
> the potential of introducing bugs. Enclosing stuff in a
If at all possible, please use define-derived-mode which results in
cleaner code and neatly hi
So it should be sufficient to
enclose the call to the parent mode inside a delay-mode-hooks form,
which results in less deeply nested code.
Yes, that is fine.
command (called the @dfn{parent mode}) and then alter some of its
settings. A mode that does this is called a @df
There appear to be several derived modes that do not yet properly
enclose the call to the parent mode in a delay-mode-hooks form.
Examples include sql-interactive-mode, inferior-emacs-lisp-mode and
inferior-lisp-mode.
Currently, we recommend to put the call to delay-mode-hooks around the
entire bo
