Re: lynx-dev peculiar behavior

[Larry W. Virden]

From: Kim DeVaughn <address@hidden>

> You might try seeing if it happens when other programs invoke your editor.
> Try going into vi from "less" and "more" with their "v" command, then hit
> ^Z, and see if you get similar behavior to lynx -> vi -> ^Z.

I tried it with less and trn and had no problems.

> BTW ... also try setting EDITOR/VISUAL to (say) emacs, and see if it
> still happens when you ^Z out of *that* editor (and also is there any
> problem when you hit ^G inside of emacs, and then exit it).

I better not try that - if emacs is around here (and I don't know that it
is) I wouldn't have the foggiest notion of how to get out of it <grin>.


>  One other thing to look at ... when you're in your lynx invoked vi, do
> a ps from another screen before the ^Z, then after the ^Z, then after
> you fg it.

> Anything change in the ps output ... like one of your processes maybe
> "disappeared" for no reason ...?

Nope:

Processes on the tty before I invoked my editor:
 8 S    lwv26 12619  1805  1  41 20 610b4f78    558 61eb9576 07:52:04 pts/4    
0:01 lynx http://purl.org/thecliff/tcl/w
 8 S    lwv26  1805  1784  0  51 20 61208238    221 612082a8 17:12:27 pts/4    
0:07 /bin/ksh


While I am in the editor:

 8 S    lwv26 12619  1805  1  41 20 610b4f78    574 610b4fe8 07:52:04 pts/4    
0:01 lynx http://purl.org/thecliff/tcl/w
 8 S    lwv26 12650 12649  0  51 20 60a07b90    246 61eb9576 07:52:51 pts/4    
0:00 nvi /ldatae/tmp/L12619-3TMP
 8 S    lwv26  1805  1784  0  51 20 61208238    221 612082a8 17:12:27 pts/4    
0:07 /bin/ksh
 8 S    lwv26 12649 12619  0  51 20 610576a0    116 61057710 07:52:51 pts/4    
0:00 sh -c nvi  /ldatae/tmp/L12619-3TMP

After I have typed ^Z and then did the fg back to the editor:

 8 S    lwv26 12619  1805  0  41 20 610b4f78    574 610b4fe8 07:52:04 pts/4    
0:01 lynx http://purl.org/thecliff/tcl/w
 8 S    lwv26 12650 12649  0  41 20 60a07b90    246 61eb9576 07:52:51 pts/4    
0:00 nvi /ldatae/tmp/L12619-3TMP
 8 S    lwv26  1805  1784  0  41 20 61208238    221 612082a8 17:12:27 pts/4    
0:07 /bin/ksh
 8 S    lwv26 12649 12619  0  41 20 610576a0    116 61057710 07:52:51 pts/4    
0:00 sh -c nvi  /ldatae/tmp/L12619-3TMP


> was to patch trn/trn4/less/mutt/etc, so that /bin/bash would be used
> instead of /bin/sh, when the programs were spawning the editor (via a
> fork/exec, system() call, whatever).  It seems that bash was handling
> signals properly, whereas sh wasn't.

I'm using ksh, rather than sh.  ksh signal handling seems to be fine.
-- 
Larry W. Virden                 <URL: mailto:address@hidden>
<URL: http://www.purl.org/NET/lvirden/> <*> O- "No one is what he seems."
Unless explicitly stated to the contrary, nothing in this posting should 
be construed as representing my employer's opinions.
-><-