Dolphin starts programs with a wrong current directory

Nikos Chantziaras realnc at
Wed Dec 9 15:23:44 GMT 2009

On 12/09/2009 01:21 AM, Duncan wrote:
> Nikos Chantziaras posted on Tue, 08 Dec 2009 19:19:30 +0200 as excerpted:
>> It's a program I wrote myself (University assignment) and the files in
>> question are an SSL certificate file and a private key file.  It usually
>> works on every other file manager, except for Dolphin, which lend me to
>> believe that Dolphin is doing it wrong.  Common sense dictates that the
>> current directory should always be the directory "you are in"; if you
>> are in it in the CLI or a file manager shouldn't matter.  The current
>> directory should always be "where you are now".
> You're thinking the MSWormOS way, not the Unix/POSIX/Linux way.  In *ix,
> the PWD (present working directory or print working directory, see the
> shell builtin of the same name) is usually[...]

Thanks for the lengthy explanation, though unneeded in my case.  I use 
Unix systems and program for them for 15 years now and pretty much know 
what PWD is.

In any event, and IMO, "current directory" is the current directory 
(duh).  So to ask in another way, if I go to /usr/local in Dolphin, 
Dolphin has no reason to consider the current directory as being $HOME 
while I'm actually in /usr/local.

Don't take me wrong.  All your points are perfectly valid and reflect 
accepted (some de-facto, some real) standards.  But you missed the point 
that there's also a de-facto standard of having "current directory" 
being the directory "you are in right now."  Dolphin breaks that "standard."

This message is from the kde mailing list.
Account management:
More info:

More information about the kde mailing list