From: Sten Drescher <sten.drescher@tivoli.com>
Subject: Re: multiple .signatures possible
Date: 16 May 1996 19:32:40 -0500 [thread overview]
Message-ID: <vpwx2cf8bb.fsf@dogbert.tivoli.com> (raw)
In-Reply-To: Kai Grossjohann's message of (unknown date)
>>>>> Kai Grossjohann writes:
>>>>> 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...
KG> (defun my-signature () (cond ((string-match "ding"
KG> gnus-newsgroup-name) "Signature for Ding") ((string-match "^nnml:"
KG> gnus-newsgroup-name) "Signature for mail groups") (t "Default
KG> signature"))) (setq message-signature 'my-signature)
KG> You get the idea...
Yup, but this doesn't use multiple .signature files. ); I've
tried
(setq message-signature
'(cond ((message-news-p)
(insert-file-contents (expand-file-name "~/.signature")))
(t
(insert-file-contents (expand-file-name "~/.signature")))))
(Yes, I know, they are the same. I'm testing) But that puts
the .signature in the header. I've tried
(setq message-signature
'(cond ((message-news-p) "~/.signature")
(t "~/.signature")))
But that makes it put in the string (appropriately). I've
tried using the same thing for message-signature-file, but that blows
up. Is there any way of returning the contents of a file as a string?
I'd rather not duplicate the whole message-signature functionality in
my .gnus.
--
~/.signature
next prev parent reply other threads:[~1996-05-17 0:32 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 [this message]
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
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=vpwx2cf8bb.fsf@dogbert.tivoli.com \
--to=sten.drescher@tivoli.com \
/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).