Subject: Pine/lynx limbo

From: Rick Lewis <[email-masked]>
Date: Wed, 4 Feb 2004 03:59:17 -0700 (MST)

Hi, All,
Wonder if there's a workaround for this.
As a pine and lynx user, I often suspend pine or lynx to do something on
the shell. After doing a control-z to accomplish this, of course I put
pine or lynx into the foreground with fg.
The problem actually comes when I've used pine to invoke lynx, but,
involved in what I'm doing, forget that I've used pine beforehand.
If I've invoked lynx from Pine, then hit control-z to suspend, I seem to
end up in limbo. At least in bash in freebsd, I don't get a shell prompt,
and I only get keystrokes echoed back to me. I can neither return to lynx
nor pine, or at least I know of no way to do this.
Even control-c doesn't abort this mess. In short, I know of no way to get
back to a shell prompt to even kill any of the processes.
Granted, this could very well be more of a lynx issue than a Pine issue,
but since pine is still in the mix somewhere, I figured someone might have
an idea how I can escape out of this, or even a way to escape to a shell
without ending up in limbo.
However, of course, the problem is that I forget that I'm in a lynx
session invoked by Pine rather than a lynx session of its own.
I've seen this on more than one system.
I suppose I could try getting into the habit of hitting F1 first to get
into the default shell from lynx.
That works in lynx, and in lynx invoked by pine.
But if I get into this control-z limbo, how do I get out?
Any ideas?
--Rick

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: Matt Ackeret <[email-masked]>
Date: Wed, 4 Feb 2004 11:00:14 -0800 (PST)

>back to a shell prompt to even kill any of the processes.

Does this _always_ happen?

I don't know the 'real' solution (sounds like it might be a job-control
issue on freebsd, as a handwaving explanation), but you could run under
screen, and then at least be able to kill the process(es) easily.

You might also try links, another text browser, simply to see if it has the
same problem.. then you might be able to narrow it down to lynx or pine.