| Summary: | kde4 krun -- run a terminal | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | andrew <aos> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
andrew
2008-02-22 06:52:30 UTC
having buttons switchign purpose like that is pretty bad usability; it also assumes that launching konsole is so common that it deserves it's own button (some of the time). there are better ways to achieve this. its just my suggestion, I dont say this is a "must" but i think putting terminal somewhere easy to access is a must, since I probaly run terminal a few hundred times a day and i bet most ppl do the same. If you want quick access to the terminal, you can put a button on the panel or assign a shortcut to it. That's a lot quicker than having to press ALT+F2 and then click a button. In fact, you could just use kickoff with that amount of keystrokes. I doubt that a lot of people start konsole 100 times a day, but rahter re-use their x konsoles they have already opened. When setting a menu entry to start in terminal mode, the started process does not run into the directory chosen by the "work path" option. The same is true when editing manually .desktop files: if Terminal=true, Path variable is not used. You can quickly reproduce this behaviour by creating a script: echo `pwd` >> /tmp/touched And then creating a menu entry for it, setting a "work path" value. Run it first without selecting "run in terminal", the checking it. I'm using live cd kde4 20080430 i386. ooops - created bug http://bugs.kde.org/show_bug.cgi?id=162183 |