Re: MC broken?
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 runs just fine. I normally use the zsh shell. Note that /bin/zsh does exist in /etc/shells, and that mc will run even if I put a non-existant program name in SHELL. It just crashes on zsh. I think this has something to do with the newer support for zsh internals. Should I just put export SHELL=/bin/bash in my .zshenv and forget about it, or what? No, you should definitely write a detailed bug report to the MC developers. They are very receptive for user input and do fix the stuff you complain about although ready-to-apply patches are more than welcome. Check out the MC site at http://mc.blackdown.org/mc/; or write directly to Miguel de Icaza [EMAIL PROTECTED]. Regards, P. *8^) -- Paul Seelig [EMAIL PROTECTED] African Music Archive - Institute for Ethnology and Africa Studies Johannes Gutenberg-University - Forum 6 - 55099 Mainz/Germany Our AMA Homepage in the WWW at http://www.uni-mainz.de/~bender/
Re: MC broken?
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 here until I deleted them and created new ones. 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 runs just fine. I normally use the zsh shell. Note that /bin/zsh does exist in /etc/shells, and that mc will run even if I put a non-existant program name in SHELL. It just crashes on zsh. I think this has something to do with the newer support for zsh internals. Should I just put export SHELL=/bin/bash in my .zshenv and forget about it, or what? Thanks, Dave
MC broken?
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 mouse support, turning off color, to no avail. There does not seem to be any debug feature for MC. On a side note, I have noticed that with newer versions of MC, the file 10 appears in my home directory with the name of that directory. I assume this is some way of keeping track of the last current directory or something, but this does not work anyway, and it is annoying (a misconfiguration, I'm sure.. but where?) I do not use MC incredibly often, but there are places where it comes in handy, especially for large-scale file actions.. so I would appreciate it if someone could help me with this. Thanks, David Benjamin [EMAIL PROTECTED]
Re: MC broken?
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 tried using different terminal definitions, turning off mouse support, turning off color, to no avail. There does not seem to be any debug feature for MC. On a side note, I have noticed that with newer versions of MC, the file 10 appears in my home directory with the name of that directory. I assume this is some way of keeping track of the last current directory or something, but this does not work anyway, and it is annoying (a misconfiguration, I'm sure.. but where?) I do not use MC incredibly often, but there are places where it comes in handy, especially for large-scale file actions.. so I would appreciate it if someone could help me with this. Thanks, David Benjamin [EMAIL PROTECTED] I'm running it on 2 systems. Check that you dependencies are up to date: libgpm1 libc5 ncurses-base Get them also from unstable if necessary. Paul Wade - Greenbush Technologies Corporation http://www.greenbush.com/cds.html Linux CD's sent worldwide
Re: MC broken?
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 curtin.edu.au) -- Entia non sunt multiplicanda praeter necessitatem
Re: MC broken?
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 ones. -!-
