Subject: Multiple Pine behavior...

From: Corey Lawson <[email-masked]>
Date: Tue, 17 May 1994 14:27:05 -0700 (PDT)

The standard default with Pine is that if one starts another Pine session
then any previous instantiations of Pine are made read-only on the various
open mail boxes. 

I guess I find this annoying.  Any thoughs about changing the behaviour so
that the first instantiation does not have its mailboxes locked, and any 
additional instantiations get only read-only access?

And keyboard customization.  Any thoughts about having a keymap file so
that us poor people who use emacs for their editor for other things 
besides Pine can, for instance, change ^O to insert a new line, instead 
of postponing a message?  Yes, I realize that this will probably not work
for every terminal type out there, but for the vast majority of VT-100ish 
users this could have potential...

-Corey Lawson
 [email-masked]

-------------------------------------
 U   U W   W   W  Bothell Campus
 U   U  W W W W   ===================
  UUU    W   W    Computer Facilities
-------------------------------------

---

From: David L Miller <[email-masked]>
Date: Tue, 17 May 1994 14:59:34 -0700 (PDT)

Corey,

Actually, Pine used to have the first instantiation keep the lock, but that
made it impossible for e.g. someone who left Pine running at work to update
their INBOX while dialed in from home.  If you don't want a second session to
steal the lock, start Pine with the "-o" command line option.  This will
cause Pine to open your INBOX read-only and not steal the lock.  Another
alternative is to convert to the Tenex folder format which allows
simultaneous read/write access.  This format is not recognized by other mail
tools though... 

We have absolutely no intention to support keyboard customization.  We feel
that the small gain for a few power-users is not worth the endless support
nightmare for those who accidently do something strange.  If you want a
customized keyboard in the composer, I suggest using the alternate-editor
feature... 

Thanks for the suggestions!

--DLM

|\ |  |\/|  David L. Miller    [email-masked]  (206) 685-6240
|/ |_ |  |  Software Engineer, Pine Development Team   (206) 685-4045 (FAX)
University of Washington, Networks & Distributed Computing, JE-20
4545 15th Ave NE, Seattle WA 98105, USA

---

From: Barry Cornelius <[email-masked]>
Date: Wed, 18 May 1994 08:46:14 +0100 (BST)

On Tue, 17 May 1994, David L Miller wrote:
> cause Pine to open your INBOX read-only and not steal the lock. ...

Sometime ago I wanted to use pine in a readonly mode and looked at the 
man page and didn't find an option to do it.   I don't believe that the 
-o option is documented in pine's man page (as at 3.89).

--
Barry Cornelius                Until 15 Apr 95:   (091 or +44 91) 374 4717
IT Service, Science Site,      From 01 Aug 94:  (0191 or +44 191) 374 4717
University of Durham,          IT Service Office: 374 2892   Fax: 374 3741
Durham, DH1 3LE, UK                   E-mail: [email-masked]

---

From: John Stumbles <[email-masked]>
Date: Wed, 18 May 1994 14:39:29 +0100 (BST)

AND THEN David L Miller replied:

> cause Pine to open your INBOX read-only and not steal the lock.

My suggestion: how about an option (call it -O ?) which has the effect of
-o if another session has the lock, but is r/w otherwise? 

That way, when (as I do) I start up pine, forgetting that another pine
session or other MUA already has access to the mailbox I will not screw up
the first one (ECSmail really gets its knickers in a twist if you do
this!), but otherwise I will get normal access. 

If I really DO want to grab the lock for my new session I can re-start
pine without the special option. (Maybe there could be a way of doing this
from within pine, but it's not that important.)

John Stumbles                                       [email-masked]
University of Reading                                              0734 318435
Whiteknights, Reading, RG6 2AF, UK
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

---

From: David L Miller <[email-masked]>
Date: Wed, 18 May 1994 08:51:55 -0700 (PDT)

Unfortunately that is not the only thing missing from the Pine 3.89 man 
page.  Use "pine -h" for a more accurate list of commands...

---

From: Philip Hazel <[email-masked]>
Date: Thu, 19 May 1994 09:11:31 +0100 (BST)

> page.  Use "pine -h" for a more accurate list of commands...

That shows

         -o             ReadOnly - Open first folder read-only
         
Is there any way of opening *subsequent* folders read-only? We have an 
archive of all messages to our hostmaster, and it would be very nice to be 
able to access it from a normal pine session in a read-only manner. I'd 
like to be able to mark folder collections in the .pinerc file as 
read-only.

Philip

--
Philip Hazel                   University Computing Service,
[email-masked]             New Museums Site, Cambridge CB2 3QG,
[email-masked]          England.  Phone: +44 223 334714