From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: [5.2.2] message vs. bbdb/mailabbrev
Date: 29 May 1996 23:26:06 +0200 [thread overview]
Message-ID: <x6vihf9no1.fsf@eyesore.no> (raw)
In-Reply-To: "Paul D. Smith"'s message of Wed, 29 May 96 11:39:57 EDT
"Paul D. Smith" <psmith@BayNetworks.com> writes:
> But I've tried to use mailabbrev and for some reason my abbreviations
> aren't defined for me. As far as I can see message-mode calls
> mail-abbrevs-setup, but I have no abbrevs defined when the message
> buffer is created.
>
> If I explicitly rebuild the abbrevs, then they're OK and I can expand
> them. But for old mail, all I had to do was add mail-abbrevs-setup to
> mail-setup-hook and all was fine.
That's odd. The mailabbrev things work OK for me -- it reads the
.mailrc file and expands To (etc) fields quite nicely...
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-05-29 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-29 15:39 Paul D. Smith
1996-05-29 21:26 ` Lars Magne Ingebrigtsen [this message]
1996-05-30 0:46 ` Jack Vinson
1996-05-30 7:52 ` Darren/Torin/Who Ever...
1996-05-31 1:14 ` Lars Magne Ingebrigtsen
1996-05-31 3:14 ` Darren/Torin/Who Ever...
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=x6vihf9no1.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).