[Bug 1203617] In plasma5 midnight commander doesn't exit to current directory anymore
http://bugzilla.opensuse.org/show_bug.cgi?id=1203617 http://bugzilla.opensuse.org/show_bug.cgi?id=1203617#c19 Dave Plater <davejplater@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(amajer@suse.com) | --- Comment #19 from Dave Plater <davejplater@gmail.com> --- (In reply to Christophe Giboudeaux from comment #18)
(In reply to Dave Plater from comment #15)
This is apparently part of mc's process of exiting to it's current directory. What is different between the GUIs that could cause this?
Last comment to answer this. What you see is the difference between a interactive login shell (which reads /etc/profile) and an interactive non-login shell (which only reads your shell configuration file)
This can be demonstrated easily, in konsole, run `ssh localhost`, this will read the profile files and mc will behave the way you want.
"echo "alias mc='source /usr/share/mc/mc-wrapper.sh'" >> ~/.bashrc" works, the next question is - why is this needed in Tumbleweed plasma5 Leap:15.4 doesn't have the line "alias mc='source /usr/share/mc/mc-wrapper.sh'" >> ~/.bashrc in ~/.profile seeing the alias command prompted me to check my bash.bashrc.local To answer this, I have a bash.bashrc.local on all my computers with various alias statements and export EDITOR=mcedit .They are identical across all three systems. I moved the laptop one to bash.bashrc.local.bu and logged out and in and mc behaved as expected. I copied over Leap's bash.bashrc.local and logged out and in. Still mc behaves as expected. Moved bash.bashrc.local to bash.bashrc.local.leap and bash.bashrc.local.bu back to bash.bashrc.local and still mc behaves as expected. I didn't check permissions or owners but the Leap copy ended up with user permissions whereas the original has root ownership. I've deleted the leap bash.bashrc.local and rebooted for good measure and still I can't reproduce this bug. Next step is to boot into this PC's Tumbleweed and maybe I can find out what went right. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com