From: Scott Blachowicz <scott@statsci.com>
Cc: ding@ifi.uio.no
Subject: Re: multiple .signatures possible
Date: Fri, 17 May 1996 08:29:14 -0700 [thread overview]
Message-ID: <m0uKRSt-000r3sC@main.statsci.com> (raw)
In-Reply-To: Your message of "17 May 1996 08:35:09 -0400." <wo3f4zjx4y.fsf@cheux.ecs.umass.edu>
>>>>> "Jack" == Jack Vinson <jvinson@cheux.ecs.umass.edu>
>>>>> 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...
Jack> For multiple signature files, I advise the message-insert-signature
Jack> function to set message-signature-file to a random file from my
Jack> signature directory
Hey...that sounds pretty tricky/cool. Is 'advice' supported in XEmacs?
I thought there already was a method for doing that sort of stuff...by
setting the signature-file variable to an elisp function or by making your
.signature file an executable script or some such? Hmmm...I guess the
script wouldn't have the gnus context information to base the decision on
though.
Scott Blachowicz Ph: 206/283-8802x240 Mathsoft (Data Analysis Products Div)
1700 Westlake Ave N #500
scott@statsci.com Seattle, WA USA 98109
Scott.Blachowicz@seaslug.org
next prev parent reply other threads:[~1996-05-17 15:29 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
1996-05-17 15:29 ` Scott Blachowicz [this message]
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=m0uKRSt-000r3sC@main.statsci.com \
--to=scott@statsci.com \
--cc=ding@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).