unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Troubles with abbrev-mode
Date: Sat, 30 Sep 2006 10:02:08 +0200	[thread overview]
Message-ID: <v9sli9ye7z.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: 878xk2e2rl.fsf@baldur.nicundtas.de

On Sat, Sep 30 2006, Tassilo Horn wrote:

> So the only question is why gnus uses text-mode-abbrev-table (where
> interactively added abbrevs go, too) when there's a
> message-mode-abbrev-table in `edit-abbrevs' by default.

`define-derived-mode' does this by default:

,----[ (info "(elisp)Derived Modes") | Emacs 22 ]
|         * The new mode has its own abbrev table, kept in the variable
|           `VARIANT-abbrev-table', unless you override this using the
|           `:abbrev-table' keyword (see below).
|
| [...]
|
|     `:abbrev-table'
|           You can use this to explicitly specify an abbrev table for
|           the new mode.  If you specify a `nil' value, the new mode
|           uses the same abbrev table as PARENT, or
|           `fundamental-mode-abbrev-table' if PARENT is `nil'.  (Again,
|           a `nil' value is _not_ equivalent to not specifying this
|           keyword.)
`----

Maybe `message-mode' could use ":abbrev-table nil" instead of "(setq
local-abbrev-table text-mode-abbrev-table)".  (Probably we need it for
compatibility with Emacs 21 and/or XEmacs.)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

      reply	other threads:[~2006-09-30  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 18:56 Troubles with abbrev-mode Tassilo Horn
2006-09-26 20:14 ` Reiner Steib
2006-09-26 21:33   ` Tassilo Horn
2006-09-27  7:56     ` Reiner Steib
2006-09-27  9:36       ` Tassilo Horn
2006-09-29 20:52         ` Reiner Steib
2006-09-29 22:17           ` Tassilo Horn
2006-09-30  8:02             ` Reiner Steib [this message]

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=v9sli9ye7z.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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.
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).