From: Jack Vinson <jvinson@cheux.ecs.umass.edu>
Subject: Re: multiple .signatures possible
Date: 17 May 1996 08:35:09 -0400 [thread overview]
Message-ID: <wo3f4zjx4y.fsf@cheux.ecs.umass.edu> (raw)
In-Reply-To: Sten Drescher's message of 16 May 1996 19:32:40 -0500
>>>>> On 30 Apr 1996 10:23:31 +0200, Uwe Sigurd Valentin Kubosch
>>>>> <uwek@ifi.uio.no> said:
Uwe> I often write for different organizations and would like the
Uwe> .signature to replect this. Sometimes I represent my University,
Uwe> and sometimes just myself, or my firm, or...
For multiple signature files, I advise the message-insert-signature
function to set message-signature-file to a random file from my signature
directory: (I have files that look like "sig1" "sig2" etc in that
directory.)
;; random insertion of .signature file
;; Thanks to Glenn R Coombs: glenn@prl.philips.co.uk
(defvar grc-signature-dir "~/.sig/")
(defvar grc-signature-base "sig")
(defadvice message-insert-signature (before random-mail-sig-ag act comp)
"Change the value of message-signature-file each time
`message-insert-signature' is called."
(let ((files (file-name-all-completions
grc-signature-base (expand-file-name grc-signature-dir))))
(if files (let ((file (nth (random (length files)) files)))
(setq message-signature-file (concat grc-signature-dir file))
))))
--
Jack Vinson jvinson@cheux.ecs.umass.edu
Sunderland, MA <http://www.cis.upenn.edu/~vinson/home.html>
Q. "Is a cat's urinary tract health important?" A. "Yes, very."
- Purina Cat Chow Special Formula Commercial
next prev parent reply other threads:[~1996-05-17 12:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-30 8:23 Uwe Sigurd Valentin Kubosch
1996-04-30 9:34 ` Kai Grossjohann
1996-05-17 0:32 ` Sten Drescher
1996-05-17 4:31 ` Lars Magne Ingebrigtsen
1996-05-17 17:22 ` Sten Drescher
1996-05-17 18:54 ` Richard Pieri
1996-05-17 12:35 ` Jack Vinson [this message]
1996-05-17 15:29 ` Scott Blachowicz
1996-05-17 20:05 ` Steven L Baur
1996-04-30 12:08 ` Hallvard B Furuseth
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=wo3f4zjx4y.fsf@cheux.ecs.umass.edu \
--to=jvinson@cheux.ecs.umass.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.
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).