Bug 180115 - ability to run command with environment settings on-fly
Summary: ability to run command with environment settings on-fly
Status: RESOLVED DUPLICATE of bug 409107
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-09 11:38 UTC by Maciej Pilichowski
Modified: 2020-07-11 15:24 UTC (History)
3 users (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 Maciej Pilichowski 2009-01-09 11:38:42 UTC
Version:            (using Devel)
Installed from:    Compiled sources

ability to run command with environment settings on-fly

Run konsole, and execute then
kile
and then
LANG=en_US kile

Now, you can do the first in krunner but not the second. Please add the ability to change environment settings on-fly as shown in the latter case.
Comment 1 Frank Van Damme 2010-01-09 14:11:45 UTC
Indeed, krunner tries to be too intelligent! :-)

I have the same issue pe with a command like 


DISPLAY=:0 wmaker

(useful for Xephyr/Xnest)

Suggestion: if the first word is not a command, run it anyway, but return an error (dialog box) if the program dies in the first 1 or 2 seconds with a non-0 exit status. 

[14:10] frank@limoen:~$ DISPLAY=:0 xterm ; echo $?
0
[14:10] frank@limoen:~$ DISPLAY=:0 xtderm ; echo $?
No command 'xtderm' found, did you mean:
 Command 'xterm' from package 'xterm' (main)
xtderm: command not found
127
Comment 2 Aaron J. Seigo 2010-01-12 03:31:09 UTC
"if the first word is not a command, run it anyway"

that would be broken in 99% of queries, so that isn't an option. i'll have to do some testing, not even sure this will work properly without running it through a terminal, but will try to come up with a fix for 4.5
Comment 3 Alexander Lohnau 2020-07-11 15:24:49 UTC

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