Document path as session's current working directory?

[Kevin Krammer]

Hi all,

Just came across an interesting observation on one of our user mailinglist.

A user reports that they are unable to unmount certain filesystems because the 
are apparently in use.
fuser indicates that these processes use the mount point directory as their 
current working directory.

The directory is the one configured as KDE's "Documents" directory.

I've just checked myself (4.3.4, Debian packages) and I see the same thing.

startkde still ha $HOME as its working directory, so does kdeinit4 and 
ksmserver. klauncher and kded4 are already using the document path.

My guess is that this is some kind of "compatibilty" feature to help improve 
uniform experience across apps even if they don't support configurable 
document paths.

The question is: can this be deactivated in case filesystem control is more 
important than non-KDE apps opening their file dialogs in $HOME?

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20100404/b3095670/attachment.sig>