Subject: Problems with signature and tokens

From: Goran UnreaL Krajnovic <[email-masked]>
Date: Wed, 24 Feb 1999 10:23:50 +0100 (MET)

I recently compiled and installed pine 4.10 (UNIX, Solaris 2.6, gcc
compiled) and I am having problems with the new feature of tokens in
signature files.

This:
                                          _ _  ___  ___  ___  ___  ___
 unreal at fly dot cc dot fer dot hr     / Y \/. |\/ __\/ -_)/ - \/  (_
    http://fly.cc.fer.hr/~unreal/        \___/\|__/\_)\/\___/\_|_/\___/
                                                   Feel the Art.

is my original signature, and has been for a long time, and the ascii art
has worked perfectly in older versions of pine.
However, v4.10 thinks that there are tokens inside the signature, and the
ascii ends up looking like this:
                                          _ _  ___  ___  ___  ___  ___
 unreal at fly dot cc dot fer dot hr     / Y \/. |\/ __\/ -_)/ - \/  (_
    http://fly.cc.fer.hr/~unreal/        ___/\|__/_)\/___/_|_/___/
                                                   Feel the Art.

I have searched the help and the mailing list, and there are no references
to this bug (or feature). I haven't managed to find an option to turn off
the token expansion, and experimenting with escaping backslashes yielded
no results.

The only way to get my normal signature back is to first delete it, and
then use the ^R (Read file) command in composer to insert the .signature
file at the end of the mail.

Any help, patches, similar problems or advice would be appreciated.

I have also tried the precompiled solaris version (9 MB executable!) and
it behaves the same way.

PS. If you can't see the ascii art properly in your mailer, set your font
to a non-proportional one, such as Courier, System or Fixed.

-- 
                                          _ _  ___  ___  ___  ___  ___
 unreal at fly dot cc dot fer dot hr     / Y \/. |\/ __\/ -_)/ - \/  (_
    http://fly.cc.fer.hr/~unreal/        \___/\|__/\_)\/\___/\_|_/\___/
                                                   Feel the Art.

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Daniel Sands <[email-masked]>
Date: Wed, 24 Feb 1999 09:11:55 -0700

Does it work to add an extra backslash before each backslash?  i.e:
>     http://fly.cc.fer.hr/~unreal/        \\___/\\|__/\\_)\\/\\___/\\_|_/\\___/
>                                                    Feel the Art.

It looks ugly here, but might solve your problem.

---

From: Goran UnreaL Krajnovic <[email-masked]>
Date: Wed, 24 Feb 1999 17:55:35 +0100 (MET)

> It looks ugly here, but might solve your problem.

Nope. I too thought of that, but there is no effect. Actually, both

\___/ and \\___/

come out as

___/

and pine doesn't appear to care about escaping backslashes. And anyway, as
far as I have seen from the manuals, all the tokens are of the form _NAME_
and I don't see why pine has to mangle my backslashes. And also notice
that in the previous line of the ascii, everything is just fine, all the
backslashes are in place.

---

From: Terry Gray <[email-masked]>
Date: Wed, 24 Feb 1999 09:54:08 -0800 (Pacific Standard Time)

It's a bug.  Will be fixed in next release.

-teg

---

From: Steve Hubert <[email-masked]>
Date: Wed, 24 Feb 1999 10:04:43 -0800 (PST)

The backslash underscore problem is a bug. It will be fixed in next
version. Your old signature file will work again at that point. Sorry for
the trouble.

-- 
Steve Hubert <[email-masked]>
Networks and Distributed Computing, Univ. of Washington, Seattle