From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: Bugs caused by recent use of define-derived-mode
Date: Mon, 02 Sep 2002 22:08:22 -0400 [thread overview]
Message-ID: <200209030208.g8328MS09722@rum.cs.yale.edu> (raw)
In-Reply-To: 200209030121.UAA26723@eel.dms.auburn.edu
> > The fact is though that currently we do not have inheritance of
> > abbrevs. I believe that the current "poor man's inheritance" is an
> > unacceptable alternative. It makes a lottery out of abbrev expansion.
> Again, please show us examples.
[..example cut out..]
So it indeed involves editing an abbrev-table. Thanks.
> I could tell you what causes this bug, but I believe you will have no
> difficulty figuring that out yourself. The really difficult thing is
> to fix this bug, without introducing others to replace it. I believe
> this is essentially equivalent with defining true inheritance.
Yes, those problems can be fixed by implementing true inheritance.
Stefan
next prev parent reply other threads:[~2002-09-03 2:08 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 2:37 Bugs caused by recent use of define-derived-mode Luc Teirlinck
2002-09-02 16:29 ` Stefan Monnier
2002-09-02 23:02 ` Luc Teirlinck
2002-09-02 23:20 ` Stefan Monnier
2002-09-02 23:25 ` Luc Teirlinck
2002-09-02 23:29 ` Stefan Monnier
2002-09-02 23:46 ` Luc Teirlinck
2002-09-03 0:26 ` Stefan Monnier
2002-09-03 1:21 ` Luc Teirlinck
2002-09-03 2:08 ` Stefan Monnier [this message]
2002-09-03 2:04 ` Luc Teirlinck
2002-09-03 2:07 ` Stefan Monnier
2002-09-03 14:05 ` Kai Großjohann
2002-09-03 15:06 ` Stefan Monnier
2002-09-03 15:36 ` Luc Teirlinck
2002-09-03 21:23 ` Luc Teirlinck
2002-09-04 0:01 ` Luc Teirlinck
2002-09-04 3:28 ` Luc Teirlinck
2002-09-04 3:49 ` Miles Bader
2002-09-04 12:31 ` Luc Teirlinck
2002-09-05 2:46 ` Richard Stallman
2002-09-05 4:37 ` Luc Teirlinck
2002-09-08 12:54 ` Richard Stallman
2002-09-09 0:14 ` Luc Teirlinck
2002-09-09 1:36 ` Luc Teirlinck
2002-09-09 23:33 ` Richard Stallman
2002-09-10 0:12 ` Luc Teirlinck
2002-09-09 2:35 ` Luc Teirlinck
2002-09-09 13:49 ` Miles Bader
2002-09-09 15:25 ` Kim F. Storm
2002-09-09 18:42 ` Luc Teirlinck
2002-09-10 16:36 ` Richard Stallman
2002-09-11 4:30 ` Luc Teirlinck
2002-09-11 20:03 ` Richard Stallman
2002-09-09 19:15 ` Richard Stallman
2002-09-05 11:07 ` Kai Großjohann
2002-09-06 1:26 ` Miles Bader
2002-09-06 2:11 ` Luc Teirlinck
2002-09-06 2:26 ` Miles Bader
2002-09-06 2:31 ` Luc Teirlinck
2002-09-06 2:31 ` Miles Bader
2002-09-06 10:52 ` Kai Großjohann
2002-09-07 3:16 ` Richard Stallman
2002-09-06 20:03 ` Richard Stallman
2002-09-06 15:11 ` Richard Stallman
2002-09-04 14:13 ` Richard Stallman
2002-09-04 16:01 ` Stefan Monnier
2002-09-03 13:26 ` Richard Stallman
2002-09-03 14:57 ` Stefan Monnier
2002-09-05 2:46 ` Richard Stallman
2002-09-06 16:07 ` Stefan Monnier
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=200209030208.g8328MS09722@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=emacs-devel@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).