Words by Pavel Roskin [Mon, Nov 04, 2002 at 12:47:57AM -0500]:
Hello, Jose!
Sorry that I didn't not reply earlier.
It is indeed a subshell problem, see ahead.
Good to know.
Hmmm, all of a sudden it started to work ok again. Certainly I have made
some changes to tons of other stuff, I
Words by Pavel Roskin [Fri, Oct 25, 2002 at 07:13:25PM -0400]:
Hello, Jose!
Let's return the discussion to the list. I've seen some complaints from
users reading the archives that the important pieces of the discussion are
missing when the discussion becomes private.
Fair enough :)
Hello, Jose!
Let's return the discussion to the list. I've seen some complaints from
users reading the archives that the important pieces of the discussion are
missing when the discussion becomes private.
1) Run xterm 2) Run mc in it 3) Press Ctrl-O 4) Run mc from the
command line 5) Press
It there any known bug running mc over an existing one
frozing the virtual terminal?
I mean, when I'm running mc on a xterm and I do a CTRL+O and (by
mistake) I run another mc get the xterm to froze.
--
Jose Celestino [EMAIL PROTECTED] SysAdmin::SAPO.pt http://www.sapo.pt
Hello!
It there any known bug running mc over an existing one frozing the
virtual terminal?
As far as I know, it's not a known bug.
I mean, when I'm running mc on a xterm and I do a CTRL+O and (by
mistake) I run another mc get the xterm to froze.
I could not reproduce this bug with the CVS
