Subject: enabling save on crash

From: *selah* <[email-masked]>
Date: Mon, 7 Dec 1998 06:23:45 -0500 (est)

I understand that pine uses the pico editor. I was wondering if there's a
way to enable pico to automatically save if a post gets interupted by a
disconnect?

Thanks.

-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Yasholomew Yashinski <[email-masked]>
Date: Mon, 7 Dec 1998 16:45:24 -0500 (EST)

> way to enable pico to automatically save if a post gets interupted by a

I believe that is you do ^O  (Control+O) it will postpone the message,
then the next time you do "C" to compose a message, you will have the
option of starting a new one, or continuing with the old.

-=/Yashy/=-

 In a World without Walls and Fences ...
 Who needs Windows and Gates ?!

---

From: Lea <[email-masked]>
Date: Mon, 7 Dec 1998 14:59:09 -0700 (MST)

> option of starting a new one, or continuing with the old.

^O will postpone if you still have an active session.

If the user is using Pine within a Unix account, I'd suggest listing the
contents of the home directory of the account with the command

ls -la                (ls -la|more if the list is more than one screen)

Look for a filename like             #pico123456789

where 123456789 is a long random number.

If you find one of those filenames and the date and time look about right
for when the session crashed, that should be where the contents of your
compose buffer went.  

What you can then do is start  Pine, open a compose screen, fill the header
out as usual,  and use ^R to read the contents of the #pico123456789 file
into the body of the message.

Lea
-----------------------------------------------------------------------------
                       Lea Andrellan       CNS Consulting Team; Helpdesk
         [email-masked]  OR  [email-masked]
                 492-9380 (voicemail)  OR  492-9400 (helpdesk)
             http://www.ualberta.ca/~maldridg/tutor/Tutorials.html

"My spelling is wobbly", said Pooh.  "It's good spelling, but it wobbles,
and the letters get in the wrong places."
-----------------------------------------------------------------------------

---

From: Stephanie Michelle Skinner <[email-masked]>
Date: Mon, 7 Dec 1998 18:02:14 -0500 (EST)

I would like to unsubscribe to this list because it has proved to be
filled with very crude and useless people (sorry to those who actually
helped me). But this list is, I guess, not the right place for my
questions. Hopefully I have made some realize that they should get a life
and stop the insults and just make a suggestion to help those of us who
are not "computer-talented". We learn quickly, ya know?
Please unsubscribe me from this list immediately.
Stephanie

"SMALL1DER" :)

---

From: "Adam H. Kerman" <[email-masked]>
Date: Mon, 7 Dec 1998 18:47:31 -0600 (EST)

>From: Stephanie Michelle Skinner <[email-masked]>
>Date: Mon, 7 Dec 1998 18:02:14 -0500 (EST)

>Hopefully I have made some realize that they should get a life

You learn quickly, do you? Then learn this:

Never, NEVER send unsubscribe requests to the list posting address. List
members do not want to read them. Instructions for unsubscribing are given at
the URL below, added to every single message that goes through this list.

If you join another mailing list, SAVE the instructions on sending unsubscribe
commands to the list server.

---

From: Shoeless in San Jose <[email-masked]>
Date: Mon, 7 Dec 1998 16:03:54 -0800 (PST)

> option of starting a new one, or continuing with the old.

Problem with that is, he's wanting to know how to recover from a
disconnect.  The only way to guarantee that you won't lose data
from that is to occasionally postpone, then exit or suspend the
pico job and save a copy of the postponed file.  I've done that
before when I have a squirrely phone line, or the ISP is having
modem troubles.  I've never seen pico consistently save during
a crash, so I've never relied on it too much.

Greg

---

From: "Matthew N. Dodd" <[email-masked]>
Date: Tue, 8 Dec 1998 01:43:46 -0500 (EST)

On Mon, 7 Dec 1998, Shoeless in San Jose wrote:
> disconnect.  The only way to guarantee that you won't lose data from
> that is to occasionally postpone, then exit or suspend the pico job
> and save a copy of the postponed file.  I've done that before when I
> have a squirrely phone line, or the ISP is having modem troubles.  
> I've never seen pico consistently save during a crash, so I've never
> relied on it too much.

I tend to assume everyone else that uses a unix shell knows and uses
screen.  I keep wondering how it is people get disconnects.

# w | grep winter | grep pine
winter   P0  3Cust235.tnt1.dc 13Oct98     -  (pine4)

Now, I would have had a longer running process but I restarted just for
kicks when I changed something in my .pinerc.

Anyhow, for everyone that doesn't use screen, go out and grab it, or if
you're not running your own boxes (as if most of the people are) try
typing 'screen' at your prompt.

Chances are it will be installed already.

Screen is one of the few things that you can't live without.  Its like
making a bash user use 'sh'.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| [email-masked] |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |

---

From: Michael Talbot-Wilson <[email-masked]>
Date: Tue, 8 Dec 1998 20:01:26 +1030 (CST)

> > > way to enable pico to automatically save if a post gets interupted by a
	
By chance I was typing a Pine message at the console about two
minutes ago when I became aware of a situation requiring urgent
attention (I had modem troubles).  Forgetting about my message I did
a few hasty and drastic things, finally shutting down and rebooting
the computer that Pine was running on.  It is a Linux computer and
it was an orderly shut down, i.e. processes were signalled. 

When it came up again I ran Pine and it immediately asked if I
wanted to continue editing the message that had been saved.  It
was intact.

So, if it's interrupted by a disconnect, I guess you'd be okay.

--
Michael Talbot-Wilson ------------------- [email-masked]
"Many good morrows to my noble lord!" - Catesby greeting Hastings
(Richard III, Act III, Scene II).

---

From: Jan Kalin <[email-masked]>
Date: Tue, 8 Dec 1998 14:31:08 +0100

> So, if it's interrupted by a disconnect, I guess you'd be okay.

If Selah is running M$ Windoze I wouldn't be convinced that is the case.
I do have a suggestion, though.

Pico is s standalone program as well as being incorporated into Pine as
the 'internal' editor. What you can try is configure Pine to use the
standalone Pico as your alternate editor ("editor" variable in config).
You can invoke it either manually with ^_ (<Ctrl>+<Underscore>) or have it
enabled implicitly ("enable-alternate-editor-implicitly" variable in
config). In either case you are then actually editing a temporary file on
disk, and even if Pine gets disconnected, the file can probably be saved
under a different name and pulled back later. Try and see (and tell us if
it works).

I actually always use an alternate editor for two reasons. First is that I
am used to 'vi' and prefer it to Pico. The second is that I have a
relatively poor connection to my IMAP server and even if the connection
acts up (no response from server for up to a few minutes), you can still
compose your text. If you get a flaky connection while composing with the
internal Pico, everything freezes up until the connection is
reestablished.

Cheers,
Jan

-- 
 Jan Kalin (male, preferred languages: Slovene, English)
 <A HREF="http://www.zag.si/~jank/"> contact information </A>

-- 
 Jan Kalin (male, preferred languages: Slovene, English)
 <A HREF="http://www.zag.si/~jank/"> contact information </A>

---

From: *selah* <[email-masked]>
Date: Wed, 9 Dec 1998 02:59:44 -0500 (est)

> under a different name and pulled back later. Try and see (and tell us if

Actually, I'm only talking about pico - not pine. The problem isn't
happening with pine - it's happening with slrn. Also, we're using a shell
account on the isp, (we also have a ppp account but prefer to use the
shell alot of times cause it's much faster.)