Bug 282909 - an option for running programs in the current working directory
Summary: an option for running programs in the current working directory
Status: RESOLVED DUPLICATE of bug 271824
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 1.7
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-27 14:14 UTC by mar.bialek
Modified: 2011-09-27 23:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mar.bialek 2011-09-27 14:14:36 UTC
Version:           1.7
OS:                Linux

I would wish to have an option to choose for each type of files where the program that opens it will be running. I would like it to be the current working directory, not my home directory, or any particular directory as it is now. The problem is for example in gvim: if I open a file, and then edit it for some and in the moment I want to run command :sav 'new_file_name', this 'new_file_name' is created in my home directory, not in my working directory. The same is if I want to run compile program from gvim. I also write some scripts, which I would like to run from dolphin by clicking. Yet there is a problem if those scripts opens some file in current directory. Either I put full path to the files in the directory or I run script from the terminal (which I don't have always open).

Or maybe I don't see this option. Also I not sure if dolphin is the right direction for this question, because it's actually filetypes in systemconfig. Redirect this please to the right place then.

Reproducible: Didn't try



Expected Results:  
.

OS: Linux (x86_64) release 3.0-ARCH
Compiler: gcc
Comment 1 Frank Reininghaus 2011-09-27 23:25:06 UTC
Thanks for the bug report! I fully agree with your request. Some changes in kdelibs are required to resolve this problem, which has been reported already.

*** This bug has been marked as a duplicate of bug 271824 ***