Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Differences between Alpine's and Pine's .pinerc

68 views
Skip to first unread message

Lucas Levrel

unread,
Sep 27, 2011, 4:38:02 AM9/27/11
to
Hi,

The title nearly says it all: I'm looking for a list of such differences.
E.g. it seems that Pine used incoming-folders-to-check where Alpine uses
incoming-check-list. It looks like Alpine kept those outdated options when
I migrated from Pine, so I'd like to do some cleanup.

Thanks.

--
LL

cha...@washington.edu

unread,
Sep 27, 2011, 10:55:25 PM9/27/11
to
Lucas,

The problem is that you were using a patched version of Pine which
was able to check for new mail in incoming folders
and that the patch was not updated because such feature was added in
Alpine, although with different ways to configure it (that is the
variables that configure the variables in Pine are not the ones chosen
to configure the same in Alpine).

If you want a fresh pinerc, you could start Alpine with the command

alpine -p newpinerc

this will create the file "newpinerc", and then you can copy the
values of the old variables over the new ones.

--
Eduardo
http://patches.freeiz.com/alpine/

Lucas Levrel

unread,
Sep 28, 2011, 10:08:14 AM9/28/11
to
Thanks Eduardo for the explanation and solution!

--
LL

Lucas Levrel

unread,
Sep 29, 2011, 5:30:19 AM9/29/11
to
Le 27 septembre 2011, cha...@washington.edu a écrit :
> If you want a fresh pinerc, you could start Alpine with the command
>
> alpine -p newpinerc
>
> this will create the file "newpinerc", and then you can copy the
> values of the old variables over the new ones.

So, I followed this procedure and found several variables inherited from
my previous Pine version that don't appear in a fresh Alpine .pinerc.

Could you confirm or invalidate my following hypotheses?

Those variables come from patches to Pine: threading-display-style-rule,
threading-index-style-rule, compose-rules, forward-rules, index-rules,
replace-rules, reply-indent-rules, reply-subject-rules, save-rules,
smtp-rules, sort-rules, startup-rules, key-definition-rules.

Those come from a regular Pine, and are now obsolete: character-set,
assumed-charset, inc-fld-timeout.

Those about which I'm uncertain: charset-aliases, iconv-aliases.

Thanks again.

--
LL

cha...@washington.edu

unread,
Sep 29, 2011, 8:06:31 PM9/29/11
to
On Sep 29, 4:30 am, Lucas Levrel <lucas.lev...@u-pec.fr> wrote:
> Could you confirm or invalidate my following hypotheses?
>
> Those variables come from patches to Pine: threading-display-style-rule,
> threading-index-style-rule, compose-rules, forward-rules, index-rules,
> replace-rules, reply-indent-rules, reply-subject-rules, save-rules,
> smtp-rules, sort-rules, startup-rules, key-definition-rules.

These variables come from the fancy thread patch, and rules to make
Pine flexible. Those patches still exist for Alpine, and if you ever
used them, you should keep them. If not, you can safely remove them.

> Those come from a regular Pine, and are now obsolete: character-set,
> assumed-charset, inc-fld-timeout.

The last option come from the patch that used to check for new mail in
incoming folders.
>
> Those about which I'm uncertain: charset-aliases, iconv-aliases.

That was from the UTF-8 patch that opensuse distributed. You probably
use OpenSuse and that is how you got a patched version of Pine.

Normally these options are harmless. Alpine (and Pine) ignore options
that it can not recognize, so you can keep them, but cleaning up stuff
that you have no use for is also a good idea.

--
Eduardo
http://patches.freeiz.com/alpine/

>
> Thanks again.
>
> --
> LL

0 new messages