One of the reasons I use Krusader is because of it's inbuilt locate search UI (brought by Ctrl+Shift+L by default.) It would be great if there were a way to launch Krusader directly in this mode. So something like: "krusader --locate" could be run from any directory which will not show the main Krusader window, but only the Locate panel one.
Dear Dufferzafar, adding features also involves writing and maintaining more source code in the future, writing and maintaining more documentation in the future, having more things to test and to take into account when developing Krusader in the future, etc. I'm afraid that there are too few people wanting this feature, although probably an automation tool like Xdotool can be used to achieve this, and also using it is also be useful to many, many programs, not just Krusader, which is very beneficial! Sometimes those automating utilities save a lot of time! If no developer added that new code to Krusader: to launch Krusader and simulate that you press Ctrl+Shift+L (to "locate"), I would execute: krusader & sleep 1s && xdotool key Ctrl+Shift+L Does it work for you?
Hey Toni, I'm a dev myself, so I totally understand the debt that new features can create. And as you said, nobody else has asked for this. So this is certainly low priority. I'd actually like to take a stab at it myself. I'll try to build Krusader from source and then work on this. Do you have any ideas on HOW this can be implemented in code? Which file will involve most of the changes etc. --- In the meanwhile, I've extended your xdotool approach to do this: lokate() { krusader 2>/dev/null & sleep 1s && xdotool key Ctrl+Shift+L && xdotool type "$1" } I'll use the above function and see if it works for me. --- Thanks a lot for taking the time to respond :)
> Do you have any ideas on HOW this can be implemented in code? Which file will > involve most of the changes etc. I haven't worked with those sections of the source code of Krusader :-(
I think instead of "krusader --locate" it's better to refactor the GUI code, so that it could be built as a separate tool as well as bundled into Krusader. (In reply to dufferzafar from comment #2) > ... I'm a dev myself ... > > I'd actually like to take a stab at it myself. I'll try to build Krusader > from source and then work on this. Feel free to try it out and submit a patch to https://phabricator.kde.org where we can review and iterate. For dev questions please use krusader-devel mailing list.