Re: PINE problem

--===============1153482464==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL"
Content-Disposition: inline


--vtzGhvizbBRQ85DL
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 01, 2010 at 01:53:23PM +0800, Bret Busby wrote:
>

             ............snip.............

> Please do not reply with "get rid of PINE and install ALPINE", as I am =
=20
> familiar with PINE, and I do not know that ALPINE will work the same, =20
> with the many folders and filters and other things implemented, and, =20
> changing software can in itself, cause problems.

When I switched from Pine to Alpine, Alpine not only used my existing
~/.pinerc file but it used my existing ~/mail directory with all its
existing 30+ mail files.=20

As far as your being familiar with Pine, you won't be able to tell the
difference. Layout, commands, etc are the same.=20

--=20
Bob Holtzman
GPG key ID =3D 8D549279
If you think you're getting free lunch
check the price of the beer.

--vtzGhvizbBRQ85DL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFLZnSHv5BYD41UknkRAnFCAKDt7MkpNcFPaQ/o6ssiD8YqE7YpfACg4uer
1DlULbJoQ8fVv9IBU6s6eQw=
=JsAc
-----END PGP SIGNATURE-----

--vtzGhvizbBRQ85DL--


--===============1153482464==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Pine-info mailing list
[email protected]
http://mailman2.u.washington.edu/mailman/listinfo/pine-info

--===============1153482464==--