In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (David/Bill Benjamin) writes:
> I have deleted the old configuration files, but that did not seem to
> resolve the problem. However, I did discover something: if I change the
> SHELL environment variable to anything other than /bin/zsh, it
On Sat, 5 Apr 1997, Jim wrote:
>
> On Sat, 5 Apr 1997, David/Bill Benjamin wrote:
>
> > Today, I upgraded MC to version 3.5.17 from the unstable tree, and so
> > far, I have been unable to get the new version to run.
>
> Could it be trying to use your old .mc.ini files? It acted very strangely
On Sat, 5 Apr 1997, David/Bill Benjamin wrote:
> Today, I upgraded MC to version 3.5.17 from the unstable tree, and so
> far, I have been unable to get the new version to run.
Could it be trying to use your old .mc.ini files? It acted very strangely
here until I deleted them and created new one
I can't help you with the *.deb package nor 3.5.17, but I've used 3.5.18
for some time without any problems -- compiled from upstream sources and
installed in /usr/local.
It creates mc.hot, mc.hot.bak and mc.ini in my ~ -- no "10".
FWIW I just finished compiling 3.5.22.
--
Dimitri
(emaziuk at
On Sat, 5 Apr 1997, David/Bill Benjamin wrote:
> Today, I upgraded MC to version 3.5.17 from the unstable tree, and so
> far, I have been unable to get the new version to run. It prints two blank
> lines and then hangs, and I have to kill it from another terminal to get
> my prompt back. I have tr
Today, I upgraded MC to version 3.5.17 from the unstable tree, and so
far, I have been unable to get the new version to run. It prints two blank
lines and then hangs, and I have to kill it from another terminal to get
my prompt back. I have tried using different terminal definitions, turning
off mo
6 matches
Mail list logo
