From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: (require 'mailabbrev)
Date: Thu, 07 Feb 2002 14:26:53 -0500 [thread overview]
Message-ID: <2npu3h9jpe.fsf@zsh.cs.rochester.edu> (raw)
(require 'mailabbrev) barfs. It should require sendmail at run time
too.
The backtrace:
Debugger entered--Lisp error: (void-variable mail-mode-map)
byte-code(...)
require(mailabbrev)
eval((require (quote mailabbrev)))
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
The related change:
2002-02-06 Richard M. Stallman <rms@gnu.org>
* mail/mailabbrev.el: Require sendmail only at compile time.
ShengHuo
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next reply other threads:[~2002-02-07 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 19:26 ShengHuo ZHU [this message]
2002-02-08 23:24 ` (require 'mailabbrev) Richard Stallman
2002-02-09 4:02 ` ShengHuo ZHU
2002-02-09 4:33 ` ShengHuo ZHU
2002-02-10 5:18 ` 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=2npu3h9jpe.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).