From: "St. Suika Roberts" <wrobert2@mailhost.tcs.tulane.edu>
Subject: Re: letting message-signature-file be a function
Date: Wed, 5 Mar 1997 08:40:08 -0600 [thread overview]
Message-ID: <199703051440.IAA22666@rs5.tcs.tulane.edu> (raw)
> It would be nice if the content of message-signature-file could be a
> function that could evaluate to the signature file name.
IWBNI the documentation also mentioned that one needs to set
message-signature-file to nil if one wants to have message-signature be
a function. It took me longer than I thought it should to figure out
that that was why I was getting double signatures when I first set
message-signature to call my sigrandomizer and insert the text instead
of changing the contents of ~/.signature (which speeded things up a
little bit).
(also it might be nice to have either an example function in the
documentation, and/or a function & variable so that one can specify just
the function to be inserted, and not worry about inserting the ^-- \n )
(defun sig ()
"call sigrnd"
(interactive)
(goto-char (point-max))
;; Insert the signature.
(unless (bolp)
(insert "\n"))
(insert "\n-- \n")
(call-process "sigrnd" nil t) ;; have this line be an if, and when one
;; has the varible set, use the specified
;; function, else use
;; message-signature-file
(goto-char (point-max))
(or (bolp) (insert "\n")))
(in case you can't tell, this is the message-signature-file insertion
function, hacked a bit, and I just coppied it out of my .emacs, so I
haven't tried the above modification)
Thanks,
Suika
--
wrobert2@mailhost.tcs.tulane.edu
"Amazing what caffeine and no sense of self-preservation can do..."
<a href="http://studentweb.tulane.edu/~wrobert2">lists</a>
next reply other threads:[~1997-03-05 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-05 14:40 St. Suika Roberts [this message]
1997-03-06 3:53 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
1997-03-05 7:59 Steinar Bang
1997-03-05 13:40 ` Steinar Bang
1997-03-06 3:52 ` Lars Magne Ingebrigtsen
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=199703051440.IAA22666@rs5.tcs.tulane.edu \
--to=wrobert2@mailhost.tcs.tulane.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).