Hello Stephen. Stephen Isard wrote in <[email protected]>: |> But .. what has editing to do with IMAP? | |That is what I was hoping you could explain. Why does losing the IMAP |connection stop s-nail from reading the temp file back into its buffer |when editing is done?
I have problems to parse this Stephen. What is going on? What is "reading back the temp file"? |> Your friend should be able to simply force `disconnect' and then |> `connect' again to get back into IMAP. | |He did try 'disconnect' after the error, but s-nail says it isn't |connected. But supposing he manages to get back into IMAP somehow, will Good, then breaking the connection invalidated the current folder. A following `connect' should bring it back, doesn't it? That code is primitive but like Gunnar Ritter said, it shall be so, "Seriously.". Somewhere. |that rescue his lost edit? He isn't so much bothered by having to |reconnect as losing the work that he did in the editor. | |> *folder* is just too special in my opinion. | |Could you expand on that remark a little? The 'folder' command, the |'folder' variable? Special how? All i mean is that, personally, i do not use network-based folders by default. I switch to them, do stuff, disconnect again. As you see above, the network code is not robust, it is blocking, it uses alarm signals to implement explicit keep-alive's, i _never_ would have done it like this. I mean, i personally "am" (was) a POP3 user, and if POP3 connection breaks you will see myriads of errors because the code is not prepared to handle this gracefully. Things are a bit better with IMAP, especially with active cache. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
