Aitikin wrote:Ok, I did that, didn't get me anything though. What information would be key for you to help me? Like my rank'll tell ya, I'm still a n00b.
Which part didn't work? Generating the ~/sig.txt file upon login, or that you don't see the signature when using a new mail? Usually I tend to set things like this in the ~/.bash_profile file (maybe a quick and dirty way ...), but it works.
What this line will do: execute fortune and pipe it (taking the output of a program and pass it on to another program after the |-sign without displaying it), ie. cowsay and moving the output of this program to the file 'sig.txt' which resides in your home-directory (~).
So:
Code: Select all
bknid@pc50016:~$ fortune | cowsay > ~/sig.txt
bknid@pc50016:~$ cat sig.txt
______________________________________
/ Q: What do agnostic, insomniac \
| dyslexics do at night? A: Stay awake |
\ and wonder if there's a dog. /
--------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
bknid@pc50016:~$
Keep in mind btw that you're gonna use (simple) 'ASCII-art' (cowsay) in your signature, which implies that - for it to be displayed entirely correct - you need to format your mails in plain text OR make sure courier-type fonts are being used. And that the recipients won't override font-formatting when receiving/displaying mails.
Here's how your signature will look like if you don't use plain text (which you should anyway: html mails are evil

) or specificly set courier-type fonts:
______________________________________
/ Q: What do agnostic, insomniac \
| dyslexics do at night? A: Stay awake |
\ and wonder if there's a dog. /
--------------------------------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
Garbled and dead-ugly! Apart from cowsay or figlet being nifty programs, I would advise
against using these programs to make up a signature, for the reason as shown above. (although this is of course entirely up to you).