Re: lynx-dev ^g is a menace

[Philip Webb]

000229 Klaus Weide wrote:
> On Mon, 28 Feb 2000, Philip Webb wrote:
>> only after invoking Most or my editor from the Print screen
>> or my editor from the  g  e-mail screen
>> or after Mutt (from the Print screen) invokes my editor;
>> not from the Print screen itself or a normal Lynx screen;
> obviously invoking those external programs has some lasting effect
> that it shouldn't have.

not only not obvious, no even so (smile)!
there's no difference in behaviour at the normal Lynx pseudo-prompt
before/after invoking the external programs;
the problem arises ONLY WHILE USING those programs.
 
> It could be (a) lynx's fault, (b) curses's fault,
> (c) the external programs' fault, or some combination.

yes: i'ld say (a), in that Lynx is taking an internal program command
as an overriding command to Lynx itself or to the system.
 
> What happens if you set your "editor" to smoething simple like cat
> then try to 'edit' a file (in a new lynx session)?

to make this work you have to invoke  cat  alone,
which tries to take input from Stdin: Lynx sits there "printing file",
& entering  ^g  simply echoes it as  ^G  on the screen;
entering  ^c  to exit  cat  also exits Lynx,
which also happens if i enter  ^c  at the Lynx pseudo-prompt.
BTW how do you terminate Stdin input for  cat  without using  ^c ?
 
>> if i enter  ^g  after starting Mutt from the Print screen,
>> but before Mutt calls the editor, the print request is cancelled.
> I don't know what to make of this, but it seems to be a matter
> between mutt and the editor - so let's leave this case aside for now.

no: the editor hasn't been invoked at that point.
Lynx reacts to  ^g  here as it does in the  mailto:  screen:
might that be a clue to what Lynx is thinking hereabouts?
 
> Let's try to find out what it is while Lynx is in curses mode.
> --- snip ---
> #! /bin/sh
> echo "Content-type: text/plain"
> echo ""
> echo -n "stdin: "; tty
> stty -a </dev/tty
> --- snip ---
> Save the snippet &  chmod  to make it executable
> Have a lynx compiled with lynxcgi support.
> Check TRUSTED_LYNXCGI in lynx.cfg, enable if necessary.

all present & correct ...

> Access the snippet using  g  &  lynxcgi: .
> Compare output between the normal state (before calling any editor etc)
> and the lynx-aborts-on-^g state.

... there's no difference (as one would expect: see above).
however, there ARE differences from  stty -a  outside Lynx:

stdin: not a tty
speed 38400 baud; line = 1; 
intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^A; eol = ^@;
 old-swtch = ^Z
; susp = ^Z
lnext = ^V; werase = ^W; rprnt = ^R; flush = ^O; stop = ^S; start = ^Q;
 dsusp = ^@
-parenb -parodd cs8 -cstopb hupcl cread clocal -cnew_rtscts -loblk -tostop 
-ignbrk brkint ignpar -parmrk -inpck istrip -inlcr -igncr -icrnl -iuclc 
ixon ixany -ixoff -imaxbel 
isig -icanon -xcase -echo echoe echok echoke echoctl
 -echoprt -echonl -noflsh -flusho -pendin 
opost -olcuc -onlcr -ocrnl -onocr -onlret -ofill -ofdel 

[PW] the diffs are as follows:

1c1
< 
---
> stdin: not a tty
3,4c3,4
< intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = ^@;
< old-swtch = ^Z; susp = ^Z
---
> intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^A; eol = ^@;
>  old-swtch = ^Z ; susp = ^Z
8,10c8,10
< -ignbrk brkint ignpar -parmrk -inpck istrip -inlcr -igncr icrnl -iuclc 
< -ixon ixany -ixoff -imaxbel 
< isig icanon -xcase echo echoe echok echoke echoctl
---
> -ignbrk brkint ignpar -parmrk -inpck istrip -inlcr -igncr -icrnl -iuclc 
> ixon ixany -ixoff -imaxbel 
> isig -icanon -xcase -echo echoe echok echoke echoctl
12c12
< opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel tab3
---
> opost -olcuc -onlcr -ocrnl -onocr -onlret -ofill -ofdel 

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto