Re: mc bug ?

From: /dev/rob0 <rob0 gmx co uk>

On Tuesday 2005-September-13 02:15, Maurice Beckles wrote:

trying the ctrl-o option to see if I could use my shell while having
mc suspended. However when I switched back to the shell it freaked
out and would not allow me to enter any commands and also gave me an
error when I went back to mc.

The shell is busy. This is a feature. Yes, it is annoying but when you
understand it you don't have this problem.

In mc hit Ctrl-o again. Hit enter, in the shell. Ctrl-o to get back to
mc. All done.

I haven't looked at the code yet, so I'm merely guessing that mc detects
busy-shell by looking at keystrokes before passing them to the shell. That
could explain why leafing through history flags busy if you don't finish
with a newline.

A necessary feature, but such an assbiter! It might be better if mc threw up
a flag outright when it suspected a busy shell rather wait until you finish
entering a long, complicated command in a distant directory and lose both
position and command.

ObGrumble: Before rejecting /bin/sh as background shell, how'bout checking
if it's a symlink to an acceptable shell? Or does 4.6.1 check it already?

Reynir Stefánsson (reynirhs bakkar is)
- -
These words: "Four-oh-four --
Page not found". Your hopes, dash'd, fall
like cherry blossoms.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]