From: "Stefan Monnier" <monnier+gnu/emacs@cs.yale.edu>
Cc: kai.grossjohann@gmx.net, emacs-devel@gnu.org, rms@gnu.org,
monnier+gnu/emacs@cs.yale.edu
Subject: Re: define-derived-mode again (was: Emacs design question)
Date: Wed, 23 Jul 2003 09:27:22 -0400 [thread overview]
Message-ID: <200307231327.h6NDRNmS030080@rum.cs.yale.edu> (raw)
In-Reply-To: buon0f5u23f.fsf@mcspd15.ucom.lsi.nec.co.jp
> > (defalias 'define-major-mode 'define-derived-mode)
> >
> > The two macros should not have the same calling convention.
> > define-major-mode should not have a parent argument.
>
> Why? It's certainly the case that some major-modes have `parent' modes,
> and some don't; really, the fact that they're major modes seems far more
> significant than that particular detail, so I'd think it would be _good_
> that they use the same macro, as long as:
As mentioned, in my view of the world, they all have a parent.
But this aside, we can also make the PARENT argument optional
(since it's always a symbol and the next arg (the mode's name) is
always a string).
Stefan
next prev parent reply other threads:[~2003-07-23 13:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19c0Fd-0004sD-DC@fencepost.gnu.org>
[not found] ` <200307141341.h6EDfxEd006523@rum.cs.yale.edu>
2003-07-16 10:31 ` run-mode-hooks Richard Stallman
2003-07-16 12:08 ` Emacs design question (was: run-mode-hooks) Kai Großjohann
2003-07-20 23:07 ` Richard Stallman
2003-07-21 14:51 ` define-derived-mode again (was: Emacs design question) Stefan Monnier
2003-07-22 5:06 ` Miles Bader
2003-07-23 7:13 ` Richard Stallman
2003-07-23 7:36 ` Miles Bader
2003-07-23 13:27 ` Stefan Monnier [this message]
2003-07-24 2:31 ` Miles Bader
2003-07-25 8:00 ` Richard Stallman
2003-07-24 19:59 ` Richard Stallman
2003-07-24 19:58 ` Richard Stallman
2003-07-22 15:12 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200307231327.h6NDRNmS030080@rum.cs.yale.edu \
--to=monnier+gnu/emacs@cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=kai.grossjohann@gmx.net \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).