home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Club Amiga de Montreal - CAM
/
CAM_CD_1.iso
/
files
/
426.lha
/
SigTune_v1.0
/
Readme.doc
< prev
next >
Wrap
Text File
|
1990-10-07
|
5KB
|
89 lines
Presenting SigTune v1.0, by Ben Scott ©1990
This program is hereby entered into the PUBLIC DOMAIN. This means I can
reserve no rights whatsoever to it, however, it's such a simple piece of
code I feel that it matters little. Do with it as you will, but I ask that
it be left as-is. Distribute by any and all means, etc., use as birdcage
liner, or sell it to someone gullible for lots of money.
This is my first nontrivial Amiga C program that was not done as a class
assignment. Basically, I did it to refamiliarize myself with writing code
after more than six months of sitting on my duff. So far as I know, it is
100% clean and tidy in all circumstances, and contains no bugs. It cannot
be made resident but eventually I hope to finish reading the Lattice
manuals so I can learn how to produce pure code.
Also included is a short "man" page, for my own amusement if no one
else's.
I am very fond of humorous quotes, and since I began reading Usenet I
always found it necessary to change my .signature file quite often in order
to include all my favorite quotes, since a 60-line .sig is frowned upon
(and rightly so...). Anyway, I had heard of the Unix program "fortune"
which can print out quotations randomly selected from a file, and I began
looking for a way to incorporate this into the .signature mechanism so that
I could have a different quote every message, and not have to mess with it
myself. I was also looking for a simple C program to write since I am
trying to learn how to program this beast. The result is the enclosed
file, named for SIGnature forTUNE.
It will take a quote file TUNE which contains the number of lines of
quotations on line 1 and select one at random, then read a file SIG and
insert the quote line where you have placed the proper escape character
(the default is "$", the dollar sign). Example SIG and TUNE files are
included. Below are some possible SIG configurations:
,--------------------------------------------------------------------.
| Arthur Dent, galactic traveler and kneebiter for Sirus Cybernetics |
| $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ |
`--------------------------------------------------------------------'
-----------------------------------------------------------
| $$$$$$$$$ | Buckaroo Banzai and his Hong Kong Cavaliers |
| $$$$$$$$$ | The Banzai Institue for Biomedial Research |
| $$$$$$$$$ | Internet: bbanzai@hb88.grovers-mills.nj.us |
-----------------------------------------------------------
Note that the second example will work fine, but the quotes will still
have to be in one line - they will be mapped into anywhere the escape
character occurs. If the quote line has fewer characters than there are
escape characters in the SIG file, it will be padded with spaces at the end
(SigTune v2.0 may have auto-centering). If it is longer, it will simply
not put the whole quote in. (personally I like to make sure the quotes are
the same length as the number of escape characters in SIG, just to be tidy.
The sample quotes are all sized in this way)
SigTune will search for SIG and TUNE first in the current directory, then
in UULIB:. They don't have to be in the same place. It will output to
stdout, which, if not redirected, will be the CLI or shell you ran it from.
The usual command line would be "SigTune >UULIB:.signature" so that it will
feed into your .sig file. When using the Dillon/Loftus Amiga UUCP port,
one idea is to configure the "MailEditor" and "NewsEditor" to actually call
a DOS script which has the SigTune command line, and then a call to the
editor - this way, you get a new .sig automatically every time you post.
Something like:
SigTune >UULIB:.signature
run dme
To compile SigTune for yourself, simply execute the source file (an idea
I picked up from the RKM example disks). I'd also suggest you replace most
if not all of the quotes in TUNE with your own, since I'm not sure which
are legally usable...
I'd like to extend thanks to Frank P. Weed III, for his many suggestions
(two of which I used) and beta-testing.
If anyone comes up with another use for this thing, I'd like to know. I
can't think of anything else. I may try porting it to Unix, where it might
find a wider audience, but I'd need to learn more about Unix first!
Anyway, have fun. I can be reached at bscott@nyx.cs.du.edu (...@nyx.UUCP),
through FIDOnet at 1:104/421.2, at the Arvada 68K BBS (303)424-9831 in
Colorado, or by telepathy. Note that the latter method is untested.
Ben Scott