From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Abbrev table
Date: Sat, 26 Apr 2003 15:12:37 +0200 [thread overview]
Message-ID: <84wuhhl7wa.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <microsoft-free.87adeer62q.fsf@eicq.dnsalias.org>
Steve Youngs <youngs@xemacs.org> writes:
> Seems to be RMS who thinks message-mode should use text-mode abbrevs.
> I've emailed him to find out what he was smoking that day. :-)
Ah, I think it's this: there is no inheritance mechanism for abbrev
tables. But abbrevs used in text mode are useful in all kinds of
text, including email. And when you introduce a new abbrevs table
for message mode then all the text mode abbrevs are gone.
So the right solution is to implement inheritance for abbrev tables.
And the best workaround is to just use one abbrev table.
That was the argument, IIRC.
--
file-error; Data: (Opening input file no such file or directory ~/.signature)
next prev parent reply other threads:[~2003-04-26 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 10:54 Steve Youngs
2003-04-25 13:39 ` Kai Großjohann
2003-04-25 14:43 ` Steve Youngs
2003-04-26 13:12 ` Kai Großjohann [this message]
2003-04-27 4:31 ` Steve Youngs
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84wuhhl7wa.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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 NNTP newsgroup(s).