https://bugs.kde.org/show_bug.cgi?id=427550

Nate Graham <n...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Ridiculously difficult to   |Ridiculously difficult to
                   |figure out how to add a     |figure out how to create a
                   |launcher to the task bar    |new launcher from scratch
                   |(or panel or whatever it's  |and pin it to the task
                   |called)                     |manager
                 CC|                            |n...@kde.org
             Status|CONFIRMED                   |NEEDSINFO
         Resolution|---                         |WAITINGFORINFO

--- Comment #1 from Nate Graham <n...@kde.org> ---
Thanks for trying out KDE Plasma! Other than this hiccup, I hope you're
enjoying it so far.

As for your issue, the way you can pin an arbitrary CLI command to the Task
Manager is by creating a new .desktop file entry for the command you want to
run. You can do this using the KMenuEdit app, which is also accessible from
Right-Click on Application Launcher > Edit Applications.

>From KMenuEdit you can click the "New Item" button and create an entry for the
thing. You can give it a name, and icon, and specify an command to run. Once
this is done, it will appear in Application Launcher and you can add it to your
Task Manager in all the normal ways: drag it there, right-click > pin, etc.

If you need for it to handle arguments/paths, you can add a special keyword. %f
means "handle a single file" and %F means "handle potentially multiple files if
given a space-separated list". %u and %U do the same thing for URLs, if the app
has the capability to handle arbitrary URLs with schemes like HTTP:// SMB://
and so on. If you set up the .desktop file this way, you can actually drag
files to the Task Manager entry and it will do exactly what you expect.

All of this is not KDE-specific; it's governed by a cross-desktop standard
about .desktop files:
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html

---

I agree that being able to create your own .desktop files for arbitrary
command-line programs isn't the most discoverable feature. However it's also
not a very common workflow, because typically, installing a GUI app will also
install a suitable .desktop file automatically. If this isn't happening, I
would argue that that's a pretty significant bug that should be reported to the
app's developer. Manually creating .desktop files isn't something we should
expect users to have to do themselves.

Can you explain which specific apps you're having this problem with?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to