Comment 16 for bug 1068451

Well, a summary of the situation (or my reply in https://git.reviewboard.kde.org/r/106177/)

    1. The reported problem happens to konsole 2.9.x. But the same problem also happens to xterm, gnome-termianl under the same situation.

    2. There is *nothing* wrong on the konsole side, IMO. The "faulty" commit mentioned in comment #3 only makes konsole more like other emulators.

    3. No matter whose fault it is , if users think it is konsole's fault, then it is and should be fixed.

    4. I don't like the idea of writing extra (strange) code to work around a long outstanding problem in another component. More precisely, the problematic code is here: http://lxr.kde.org/source/kde/kdelibs/kio/kio/krun.cpp#1079 .

    5. Reverting that "faulty" konsole commit is an easy task, while it also means konsole will lose that only recently gained similarity to other emulators.

In the end, I think reverting is the right way. But I'm still reluctant to do it (because there is nothing wrong on the konsole side, you know...). That is why I didn't fix this problem in KDE SC 4.9.1, although I had enough time to do it.

So all subscribers of this report, you have two choices to get this problem fixed :

    1. Raise your hands and push me in this report: "I don't care whose fault. I only want it to be fixed ASAP(4.9.2). Revert that commit. "

    2. Go to bug 183534, add your polite and convincing argument why the current behavior of using KGlobalSettings::documentPath() as the fallback working directory is problematic. Then wait for bug 183534 to be fixed.
l