🚀 go-pugleaf

In article <19950628.125122.16@moffatt.demon.co.uk>,
          RobinM@moffatt.demon.co.uk (Robin Moffatt) wrote:

> I have recently noticed that when "composing" a news or email piece in Zap
> TTFN has not always acknowledged that I have finished writing it - I have
> S-Ctrl-F3 set up to close and save the window, which will normally result in
> TTFN opening it's little "Send message
> <123123123.234234@moffatt.demon.co.uk>?" window.
> Sometimes it doesn't do this, and I am left with "TTFN_Work" in the scrap
> directory, and TTFN whinging that "You can only compose one item at a time" if I
> try to write the article again.  
> I am using Zap 1.30 (although it happened with 1.2 as well) on a 5MB RPC
> What I normally have to do is move TTFN_Work to a temporary place, quit TTFN,
> reload it, find the message I was replying to, delete all of the text from the
> zap window and drop the TTFN_Work that I'd moved into zap and then save and
> close it.
> It doesn't happen all of the time - prehaps one in ten messages, but when it
> does it's a real pain :-(
> 
> 

The easy way to get the file back is click on Rescue on the TTFN menu, then
try to save / quit again.

The way I save is generally to just click on the quit icon, then select save.
 For some reason this always sends the correct message to newsbase.

-- 
Name :Ben Chalmers.               Bringing about Armageddon can be dangerous.
Email:ben@bench.demon.co.uk       Do not attempt it in your home. -Good Omens
WWW  :http://uptown.turnpike.net/B/benchal/Ben.html