Re: Fwd: PINE problem

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


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

On Thu, Feb 04, 2010 at 12:37:39PM +0800, Bret Busby wrote:
>=20
> Can it be done, that a user renames the mail directory hierarchy (eg,
> to pinemail), and .pinerc (eg, to .pinerc-pine), then intalls alpine,
> renamed the pinemaildirectory hierarchy to mail, and then imports the
> .pinerc settings into the alpine .pinerc file, so that the settings
> from the original .pinerc file, are preserved into the new alpine
> .pinerc, but the alpine .pinerc inline documentation, is also
> preserved in the file?

Your over thinking the situation. As I suggested in a previous post,
*copy*, not rename, your mail directory to mail.bak. You don't have to
copy .pinerc. Delete Pine, install Alpine and run it. If it works, and
it will, delete the mail.bak directory and your good to go.

--=20
Bob Holtzman
Key ID: 8D549279
"If you think you're getting free lunch,
 check the price of the beer"

--oyUTqETQ0mS9luUI
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)

iD8DBQFLaukov5BYD41UknkRAg+JAKCvbPWyOjTTYKefaGQOxQieLGJUxwCfVrGC
fIA8c9lqaoreOLB7419rKj0=
=ey27
-----END PGP SIGNATURE-----

--oyUTqETQ0mS9luUI--


--===============1026767633==
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

--===============1026767633==--