[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Single Page
Top Document: Signature, Finger, & Customized Headers FAQ
Previous Document: ... ... 1.2.5 Emacs Mail Mode
Next Document: ... ... 1.2.7 NN
-
Search the FAQ Archives
Single Page
Top Document: Signature, Finger, & Customized Headers FAQ
Previous Document: ... ... 1.2.5 Emacs Mail Mode
Next Document: ... ... 1.2.7 NN
... ... 1.2.6 MH and Emacs mh-e
From: Jym Dyer <jym@remarque.berkeley.edu> Followup-To: comp.mail.mh =o= MH doesn't have an automatic signature mechanism, but it is so configurable that there are a number of different ways to implement one. Check the periodic "MH Frequently Asked Questions (FAQ) with Answers" posting for details. =o= CAVEAT: If you use the environment variable SIGNATURE to point to your signature file, MH will use it not as a signature, but as your "fullname". Even worse, if your version of MH was built with the "UCI" option and you *don't* use the environment variable SIGNATURE to point to another file, MH will use the $HOME/.signature file for this purpose! To see if your version of MH has this behavior, enter this command: % send -help And look for the string "[UCI]" in the output. =o= There's an Emacs interface to MH, called MH-E. It has its own signature mechanism, which is invoked with the "mh-insert- signature" command (bound to the "C-c C-s" keys by default). =o= This will insert the file $HOME/.signature file by default. If your signature file has another name (e.g., to avoid its being used by an MH build with the "UCI" option), you can set the "mh-signature-file-name" variable to refer to a different file.
Top Document: Signature, Finger, & Customized Headers FAQ
Previous Document: ... ... 1.2.5 Emacs Mail Mode
Next Document: ... ... 1.2.7 NN
Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
FAQ Editor <faq-editor@ii.com>
Last Update October 23 2009 @ 09:18 AM