https://bugzilla.suse.com/show_bug.cgi?id=1203617 https://bugzilla.suse.com/show_bug.cgi?id=1203617#c77 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|werner@suse.com |amajer@suse.com CC| |werner@suse.com --- Comment #77 from Dr. Werner Fink <werner@suse.com> --- (In reply to David Rankin from comment #76)

I can confirm on TW, that mc does not exit to the current directory any longer when sourcing mc-wrapper.sh as the mc startup. Instead, mc reverts back to exiting to the start directory regardless of the current directory. The mc-wrapper.sh script has worked for -- ever. So something broke that setup.

This has nothing todo with this bug. The shells do now their jobs with my changes to aaa_base. The rest is the job of mc, see e.g. /usr/share/mc/mc-wrapper.sh MC_USER=`whoami` MC_PWD_FILE="${TMPDIR-/tmp}/mc-$MC_USER/mc.pwd.$$" /usr/bin/mc -P "$MC_PWD_FILE" "$@" [...] ... and accoringly to man manual page of mc -P file, --printwd=file Print the last working directory to the specified file. This option is not meant to be used directly. Instead, it’s used from a special shell script that automatically changes the current directory of the shell to the last directory Midnight Commander was in. Source the file /usr/libexec/mc/mc.sh (bash and zsh users) or /usr/libexec/mc.csh (tcsh users) respectively to define mc as an alias to the appropriate shell script. I guess that simply the pwd is not that what you expect. -- You are receiving this mail because: You are on the CC list for the bug.