On Tue, 2010-05-11 at 13:43 +0200, martin f krafft wrote: > You mean I should duplicate/overwrite /etc/mc/mc.ext (I don't have > a specific ~/.mc/mc.ext file, since I configure everything via > mailcap)? I don't think this is a good idea.
You can cp /etc/mc/mc.ext ~/.mc and edit it accordingly, but I guess that just adding a relevant section to ~/.mc/mc.ext would work and it should take precedence on /etc/mc/mc.ext. Your mailcap configuration will not work anyway because mc does not use mailcap by default. Therefore if you want to use mailcap you have to create your own mc.ext either way. > Is there any reason why a spawned process' stderr output should be > printed to the pty where mc runs? I can't see any, and then it > really just makes more sense to block it altogether. I run different stuff in the background and if it fails I'd like to see the error messages immediately because I can Ctrl+L later to reset the terminal anyway, but if I don't take action quickly I might run into problems. These are not changes we are supposed to do as packagers especially when upstream already provides a way for the user to configure it. If you want to make it a global default for everybody I think this should be discussed with upstream. -- Sincerely yours, Yury V. Zaytsev -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
