[Alpine-info] more report on web alpine pine.conf .pinerc

Lucio Chiappetti lucio at lambrate.inaf.it
Fri Jul 15 06:19:42 PDT 2011


On Thu, 14 Jul 2011, Lucio Chiappetti wrote:


> Are there any hint about the usage of web alpine in order to share as

> much as possible of the standard .pinerc I use locally ?

>

> I first tried copying it

> pine -copy_pinerc .pinerc '{poseidon/ssl/user=lucio}remote_pinerc'


I am inclined to think web alpine (as distributed with alpine 2.00) is
sort of unstable or unsupported. Pity because it could have been A Good
Thing.

I have solved PART of my problems, which I want to share, and still have
some other ones.

- First of all I discovered that web alpine has two interfaces, a cute
"standard" one, more lkely other web mailer, and one (reached clicking
on "HTML view" in the bottom bar) which is more like the plain alpine
client.

- I get errors in the apache log about the "yui" library, it looks
for datasource-beta-min.js and simpleeditor-beta-min.js. I solved
it softlinking the existing datasource-min.js etc. (non beta)

- I also got errors accessing any folder other than inbox. Also while
composing it failed on saved-messages, and also failed with "Unknown
attachment ID" sending with attachments.

all these errors go away if in my remote_pinerc (which I copied from
my local .pinerc) I define ALL folder collections and incoming folders
prefixing them with my {imapserver/user=myname/ssl}

(my pinerc was peculiar, as I had lot of folder collections
corresponding to local directories)

- still there are two problems. A minor one is that I cannot honour
message ordering by arrival, with most recent last (any change I make
to Settings, and save, are not honoured)

- the most severe is that I cannot view message content !
I get blank content, and get this error sequence in the apache log

list element in braces followed by "<td" instead of space
while executing
"WPSend $_wp(sockname) $args"
(procedure "WPSendCmd" line 4)
invoked from within
"WPSendCmd cgi_buffer {drawMessageText 0 {INBOX} 30025 0}"
("eval" body line 1)
invoked from within
"eval "$_wp(eval) $args""
(procedure "WPCmd" line 4)
invoked from within
"WPCmd cgi_buffer "drawMessageText $c {$f} $u $showimg""
invoked from within
"if {$n > 0} {
cgi_puts [WPCmd cgi_buffer "drawMessageText $c {$f} $u $showimg"]
cgi_puts "<script>"
if {0 == [catch {WPCmd PEMessage $u needpass..."
(file "/poseidon/WWW/Primary/Webalpine/web/cgi/alpine/2.0/newview.tcl"
line 239)

- also it is not clear to me what is the purpose of the "Contacts"
button, I thought it should give access to the addressbook, but it
looks it is not the case.

However the address book (copied to remote_addrbook with the appropriate
command) IS accessed when composing, with a sort of name completion.

If I use the HTML view instead, things go somewhat better. First most
things are more similar to the interface I'm used to, and also the access
to the addressbook, folder list and configuration file.

- However when I view a folder index (for which it seems to somewhat use
my standard
index-format=FULLSTATUS KEYINIT MSGNO DATE FROMORTO(33%) ATT SUBJECT(67%)

it seems not to honour ANY specification of the length of the FROMORTO
field (nor a percentage, nor a fixed number of characters, nor making
a "sensible choice", but display a very long string in all cases the
To: line is a list of users.

This is inconvenient as I have to scroll left to see the subject.

- In the HTML view I *generally* can view the message content. I say
generally, because my .pinerc (copied to remote_pinerc) made use of
extensive colour customization (based on the fact I work on a colour
onto black background terminal).

So in most places I get a mixture of black-on-white or other colour
on white, with colour on black (e.g. message headers, status flags
in folder indices). Sometimes the message content is however black
on black, as if no appropriate html colour spec is made.

I will now try to edit my remote_pinerc to fix the colours. I hope to be
able to do that before I disappear for vacations.

I will anyhow read any reply on the list when I return (or may be if I get
a connection to my new webalpine in some public library while away :-) )


More information about the Alpine-info mailing list