Subject: Re: auto backups in pico?

From: kremžská HOŘČICE <[email-masked]>
Date: Wed, 10 Apr 1996 14:53:41 +0200

On Tue, 9 Apr 1996, Nancy McGough wrote:

>  when
> I crash out of a pico session the file seems to be lost.  Is there any way
> to set pico up so it will keep a recovery file around?

    If you mean standalone Pico (not within Pine itself), I believe the
answer is no.  I could be wrong, since I haven't looked at the code to
verify that it's only in the Pine source, but I've just started to write a
junk file of several hundred characters and get no auto-save file.

    As far as Pico as part of Pine is concerned, in 3.92 it is automagic
that there is a file checkpointed every 200 keystrokes.  As I compose this
message, I see the following file increasing in size...
-rw-rw-r--    1 core     hackerz      766 Apr 10 14:47 #pico00642#
    This file contains most of the contents of this message.

>  Also, when I'm
> using pico to compose a message there does not seem to be a way to do a
> save.  ^O postpones the message

    Here it sounds that you refer to Pico as part of Pine.  This is the
case in which you get the checkpointed message as I noted above.

    When you use Pico standalone, that means you are able to use ^O to
write out a checkpointed copy of your message.  As part of Pine3.92, this
is automatic for you (but you must recover from the #pico... file -- there
is no automagic way to do this).

Barry Bouwsma, Radio Prahoohaw  <[email-masked]>
posted, mailed, and /dev/nulled

---

From: [email-masked] (Jie Yuan)
Date: 10 Apr 1996 19:38:51 GMT

In article <[email-masked]>,
	Nancy McGough <[email-masked]> writes:
>Whenever I crash out of a vi session, I get a nice message mailed to me
>saying that I can recover my file using `vi -r /tmp/filename'.  But, when
>to set pico up so it will keep a recovery file around?  Also, when I'm
>save.  ^O postpones the message but I just want to be able to do a quick
>save so that if I crash I'll have a backup.

If you compose in Pine, your editing session will be saved very often.  
Should you crash in the middle of an editing session, you can continue 
it next time you launch Pine.  This has happened a few times when I 
access Pine from a dialin line.  I am not sure whether the standalone
Pico can do this.  It probably does.  Have you checked the /usr/tmp
directory?

Jie
-- Jie Yuan, PhD - U. Cincinnati - Pharmacology & C.B. --
== POBox 670575, Cin., OH 45267-0575  =  513-558-2352  ==
== [email-masked] = www.uc.edu/~yuanj =  using Knews  ==
== finger -l [email-masked] for my PGP pub. key=

---

From: [email-masked] (Jamie Royer)
Date: 15 Apr 96 17:28:02 PDT

Colette Monaghan <[email-masked]> writes:
> I have a query regarding the use of the utility "ansiprt", which is
> included with the pine source code.

It is probably a pass-through program.  Test it using:

      echo "Hello World" | ansiprt | lp -dSomePrinter
or
      cat SomeFile | ansiprt | lp -dSomePrinter

If this doesn't work, sorry, can't help.

> Once it is compiled, do I need to have the executable placed anywhere
> in particular? I've looked at various bits of documentation, but
> there doesn't seem to be anything specific enough for me.

It needs to be in the path.  We put ours in /usr/local/bin.

> Also how exactly do I need to set up the printer configuration to
> be able to use ansiprt?

Use "Setup Printer" select the third option, "Personally selected
print command".  If the above works, you would use:
   ansiprt | lp -dSomePrinter

----------------------------------------------------------------------
Jamie Royer                         Tel:    (604) 775-2879
Senior Programmer                   Fax:    (604) 775-2880
GAEA Management & Consulting Ltd.   E-Mail: [email-masked]
Burnaby, BC, Canada
----------------------------------------------------------------------
         My opinions may be wrong, but at least they're my own.