Re: Alt editor failure cause found -- vim returning errors
Dan Hatton <[email protected]>
| Newsgroups | gmane.mail.pine.general |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 16 Feb 2007, Curt Sampson wrote: > On Thu, 15 Feb 2007, Matt Ackeret wrote: > > > Well, I found the problem. If vim gets any error, including searching for > > text that's not found (like if I do /ZZZ right now in vim launched from > > pine), then vim returns an error. > > It ought not do this, and doesn't do this for me. It should only return > an error code if it can't write out the file or something like that. > Could there be something else in the environment that is causing a real > error? I'm consistently getting the same "alt editor failed" error message with my alt editor, emacs -nw, launched from alpine 0.8. It happens even if I just exit the editor straight away after it's launched; but there's never anything wrong with the text produced. Emacs prints no error message to the terminal, nor on its own status line, and I can't find any way of making it more verbose. I've tried running identical emacs commands outside of alpine, and the return value is zero. Could it be something internal to pine/alpine? For example, why does line 269 of pico/osdep/altedit.c have both the conditions trv == 0 and status == 0? I can only understand the first of them. Any ideas would be welcome. -- Thanks, Dan Hatton <http://www.bib.hatton.btinternet.co.uk/dan/> _______________________________________________ Pine-info mailing list [email protected] http://mailman1.u.washington.edu/mailman/listinfo/pine-info