Re: lynx-dev peculiar behavior

[Klaus Weide]

On Sat, 10 Jul 1999, Larry W. Virden wrote:
> 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
> 
> From: Kim DeVaughn <address@hidden>
> > 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.

You may be using ksh as the login shell, but the system(editor command)
command uses "sh" for you, according to the ps output above.  That's the
level Kim was talking about.

The man page text Tom send talked about using ksh instead of sh as the
shell for system, by referring to some other man pages:

     If  the
     application  is standard-conforming (see standards(5)), sys-
     tem() uses /usr/bin/ksh  (see  ksh(1));  otherwise  system()
     uses /usr/bin/sh (see sh(1)).

No I don't mean what they mean by "standard-conforming", but apparently
your lynx isn't according to their definition since it uses "sh".

    Klaus