syd@DSI.COM (Syd Weinstein) (11/25/89)
In putting together patch 14, I wanted to include something to handle
the problem with editors and bad status returns due to interupts.
(The problem with loosing outgoing messages with the 'unable to
execute editor' messages)
However, I could not find a common thread to allow for it.
The problem: If you cause a SIGINT (interrupt), while in the
editor composing the message, Elm gets a non-zero status back from
the shell that runs the editor.
However, this is no difference between that status and possible status
values when the editor does run into trouble. Some have mentioned
that their system returns 3 (SIGINT) as the stauts, my Sun returns
208 (now what does 208 mean?) I can make it not check the status
at all, but then a bad Editor option would not be detected.
My Sun returns 1 for missing editor, but I doubt if that is standard
either.
Any good suggestions?
--
=====================================================================
Sydney S. Weinstein, CDP, CCP Elm Coordinator
Datacomp Systems, Inc. Voice: (215) 947-9900
syd@DSI.COM or {bpa,vu-vlsi}!dsinc!syd FAX: (215) 938-0235