Re: mc
On Sun, 1 Jun 1997, Daniel Stringfield wrote: > MC doesn't seem to want to run anymore. All I get is a blank screen when > I run it. I'm running the MC out of BO right now. Most of my stuff is > from 1.3 though. I have had trouble getting MC to work properly with zsh. If you are using zsh also, you may have some luck with turning off the subshell feature of MC. I have a command in my /etc/zshrc that reads: alias mc="mc -u" The subshell mode seems to work fine with bash, I have only had problems with zsh. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Dependencies
On Mon, 14 Apr 1997, Britton wrote: > I'm sorry to be dogmatic, but I'm going to say one more time that I like > things the way they are. If something depends on seperately maintained > library xyz it is not good but *GREAT* to know about it from the start. > The dependency structure sends this message to users load and clear, in a > way that a lumped package scheme would not even if a full description of > all dependencies were given when such a package was installed. I really > had no clue about the high level of software interdependence when I > started with slackware, and it hurt me continually. I think a little pain > with dselect in the beginning would have saved me a lot of grief later. I agree that an understanding of the dependency structure is very important and helpful in avoiding future problems as the result of mistakes in package maintenance. One thing that I would like to see added to the dpkg program is an option to display the packages that are necessary (and which ones are uninstalled) to configure a particular new package. As I do not use dselect or dftp, this would be very timesaving to me. For example, rather than using the trial-and-error approach, I could do the following: $ dpkg --list-depends blah_1.0-1.deb Installed dependencies: blah-base ncurses Required dependencies: blah-lib Conflicts: none Or something to that effect. Any thoughts? Dave -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
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]>
