Skip to content

About

KDE Plasma 6 dropdown app launcher for Wayland, with Yakuake-style toggle behavior for any app you configure.

Topics

Resources

Security policy

Stars

26 stars

Watchers

0 watching

Forks

Repository files navigation

plasma-drop

plasma-drop icon

CI Release Crates.io License: GPL-3.0-or-later macOS: quartz-drop OpenSSF Scorecard SLSA Build L2 Provenance

plasma-drop is a KDE Plasma 6 dropdown app launcher. It registers global shortcuts through KWin, finds or starts the apps you configure, and moves their windows into dropdown-style screen positions.

Think Yakuake-style dropdown behavior, but for Dolphin, Kate, Chromium, or any other app you add to the config.

It is heavily inspired by windows-terminal-quake. If you need a GUI, a Windows version, or a broader configuration surface, use that app.

On macOS, use the sibling project quartz-drop. It is a Swift port of plasma-drop and reads the same config file.

Contents: Install · First Run · Configure Apps · Verify Your Download · Documentation · Development · Distribution and Releases · Support Ukraine

Demo

plasma-drop-demo.mp4
plasma-drop-demo.webm

Install

You need KDE Plasma 6.3 or later on Wayland, with a session D-Bus and KWin scripting. Older releases don't let scripts read whether a window is maximized. plasma-drop doesn't support X11 or other compositors. Packages and tarballs exist for x86_64 and aarch64.

Distribution How to install
Fedora and other DNF-based systems DNF repository, .rpm, tarball
Debian, Ubuntu and other APT-based systems APT repository, .deb, tarball
Any distribution tarball, mise, packslip or cargo

All downloads are on the latest release page.

Fedora: DNF repository

This is the recommended method: dnf upgrade then keeps plasma-drop up to date.

sudo curl -fsSLo /etc/yum.repos.d/plasma-drop.repo https://skellla.github.io/plasma-drop/rpm/plasma-drop.repo
sudo dnf install plasma-drop

Debian and Ubuntu: APT repository

This is the recommended method: apt upgrade then keeps plasma-drop up to date.

sudo curl -fsSLo /usr/share/keyrings/plasma-drop-keyring.asc https://skellla.github.io/plasma-drop/plasma-drop.asc
sudo curl -fsSLo /etc/apt/sources.list.d/plasma-drop.list https://skellla.github.io/plasma-drop/deb/plasma-drop.list
sudo apt update
sudo apt install plasma-drop-keyring plasma-drop

The packages and the repository metadata are signed with the plasma-drop packages key, plasma-drop.asc (the same as packaging/signing/repo.asc); APT and DNF refuse anything it didn't sign. DNF asks you to confirm the key's fingerprint on the first install. The plasma-drop-keyring package keeps APT's copy of the key current, so key rotations and revocations arrive with apt upgrade. If you set up the repository before it existed (with the key in /etc/apt/keyrings/), that setup keeps working; run the commands above once to switch over, then delete /etc/apt/keyrings/plasma-drop.asc. The repositories keep the 10 most recent releases, so you can also pin or downgrade a version (details).

A single .deb or .rpm file

You get no automatic updates with this method. Download the file from the latest release, then run:

sudo apt install ./plasma-drop_<version>_amd64.deb      # Debian, Ubuntu (arm64.deb on aarch64)
sudo dnf install ./plasma-drop-<version>-1.x86_64.rpm   # Fedora (aarch64.rpm on aarch64)

Packages install /usr/bin/plasma-drop, the user service /usr/lib/systemd/user/plasma-drop.service and the starter config /usr/share/plasma-drop/examples/config.toml.

Any distribution: tarball

This method installs for your user only, into ~/.local, and doesn't need root. It also copies the starter config and installs the user service:

tar -xzf plasma-drop-<version>-<arch>-unknown-linux-gnu.tar.gz   # <arch>: x86_64 or aarch64
cd plasma-drop-<version>-<arch>-unknown-linux-gnu
./install-user.sh

mise, packslip, Nix or cargo

These put plasma-drop on your PATH. Pick one:

# mise. Append @<version> to pin a release.
mise use -g github:SkeLLLa/plasma-drop

# packslip. Checks the signed release manifest before it installs into ~/.local/bin.
packslip install github.com/SkeLLLa/plasma-drop --pin ps1_4yd5vxao3lfzaox72lynxuotke

# Nix, prebuilt (x86_64 and aarch64 Linux). Installs the release's static binary, pinned by SHA-256.
nix profile install https://skellla.github.io/plasma-drop/nix/flake.tar.gz

# cargo. Builds from crates.io.
cargo install plasma-drop --locked

plasma-drop init --systemd then writes the starter config and the user service. The service starts ~/.local/bin/plasma-drop; for a Nix install, change its ExecStart to %h/.nix-profile/bin/plasma-drop.

The packslip --pin fingerprint identifies this repository (not a workflow) and stays the same across releases. Check it against this README rather than trusting it on first use. With mise, mise use -g packslip:github.com/SkeLLLa/plasma-drop also checks the signed manifest.

Verify your download

Every release file is built by this repository's release workflow on GitHub-hosted runners and carries signed build provenance naming the commit and the run that built it. APT, DNF and packslip check signatures for you; for a file from the releases page, run:

gh attestation verify plasma-drop-<version>-x86_64-unknown-linux-gnu.tar.gz \
  --repo SkeLLLa/plasma-drop \
  --signer-workflow SkeLLLa/plasma-drop/.github/workflows/release.yml \
  --source-ref refs/heads/master

Crates published by this pipeline carry the same provenance (releases with a plasma-drop-<version>.crate asset); see docs/verifying.md.

Newer releases also attach plasma-drop-<version>.intoto.jsonl (use it with --bundle) and can be immutable (marked Immutable on the release page; check with gh release verify v<version>). docs/verifying.md covers every artifact and what each check proves. To report a vulnerability, see SECURITY.md.

After installing

Create your config, then start the user service:

# APT, DNF or a .deb/.rpm file: copy the starter config
mkdir -p ~/.config/plasma-drop
cp /usr/share/plasma-drop/examples/config.toml ~/.config/plasma-drop/config.toml

# mise, packslip or cargo: write the config and the user service
# (use `plasma-drop init` to skip the service)
plasma-drop init --systemd

# Every method
systemctl --user daemon-reload
systemctl --user enable --now plasma-drop.service

The tarball's install-user.sh already did the first step. Next, see First Run.

Uninstall

First stop the service with systemctl --user disable --now plasma-drop.service, then:

Installed with Remove with
DNF sudo dnf remove plasma-drop, then sudo rm /etc/yum.repos.d/plasma-drop.repo
APT sudo apt purge plasma-drop plasma-drop-keyring, then sudo rm /etc/apt/sources.list.d/plasma-drop.list
Tarball or packslip rm ~/.local/bin/plasma-drop
mise mise unuse -g github:SkeLLLa/plasma-drop
cargo cargo uninstall plasma-drop

Every method except the packages also wrote ~/.config/systemd/user/plasma-drop.service; delete it too. Your config in ~/.config/plasma-drop stays in place until you delete it.

First Run

Edit the starter config before relying on the service:

$EDITOR ~/.config/plasma-drop/config.toml
systemctl --user restart plasma-drop.service

Watch logs while testing:

journalctl --user -u plasma-drop.service -f

If your session does not use systemd --user, start plasma-drop from your session startup instead:

plasma-drop --config ~/.config/plasma-drop/config.toml

For foreground debugging:

plasma-drop --config ~/.config/plasma-drop/config.toml -v

Configure Apps

Configuration is TOML. Each [[app]] entry defines one managed app, its hotkey, how to find or launch it, and where to place it.

Minimal example:

[[app]]
name = "dolphin"
hotkey = "super+f9"
filename = "/usr/bin/dolphin"
attach_mode = "find-or-start"
hide_decorations = true
hide_behavior = "minimize"
hide_on_focus_lost = true

[app.placement]
width = "50%"
height = "100%"
position = "left"

Animation example:

[app.animation]
style = "slide"
direction = "left"  # top | bottom | left | right, slide entry/exit edge for slide and slide-fade
duration_ms = 180

Omit direction to use the default (top). It is ignored by fade and none.

Common fields:

Field Purpose
name Unique app identifier
hotkey Global shortcut, for example super+f9, or a lone super tap
filename App/window identity matcher
command Explicit launch command array, useful for wrappers such as Flatpak
attach_mode find or find-or-start
hide_decorations Hide the KWin title bar and border while managed
hide_behavior offscreen (default) or KWin minimize when hidden
hide_on_focus_lost Hide after focus moves to another window
[app.placement] Width, height, position, offsets, and target screen
[app.animation] Optional slide/fade behavior, including slide direction

Focus-loss hiding is event-driven through KWin

See resources/example-config.toml examples, and docs/configuration.md for every supported option.

Documentation

cargo doc --no-deps --document-private-items uses the guide pages in docs/ as the crate documentation entry point.

Development

This repo includes a pinned .mise.toml for contributor tooling. It is separate from the end-user mise use -g github:SkeLLLa/plasma-drop install flow.

Typical setup:

mise install
mise run build

For a release binary, use the release task:

mise run build-release

The release binary is written to target/release/plasma-drop.

Mise routes these Cargo commands through Mr Boxington, which reuses compiled Rust work across builds on this machine. The first build fills the cache; later matching builds can reuse it. Use mise run or mise exec when you want this cache. The Make targets and GitHub Actions continue to use regular Cargo commands and do not require mise or Mr Boxington.

Run the full local quality suite with either task runner:

make check
mise run check

Common project scripts:

Task Make mise
Build make build mise run build
Release build — mise run build-release
Format make fmt mise run fmt
Check format make fmt-check mise run fmt-check
Lint make lint or make clippy mise run lint or mise run clippy
Test make test mise run test
Docs make doc mise run doc
Complexity make lint-complexity mise run lint-complexity
KWin script make lint-js mise run lint-js
Full check make check mise run check

Both runners use the same Cargo operations; mise also enables the Mr Boxington build cache.

Distribution and Releases

Release CI builds:

  • tar.gz binary bundle with install-user.sh
  • deb
  • rpm
  • GitHub Pages RPM/APT repository metadata

Each artifact ships the plasma-drop binary, a user systemd unit, and an example config. The detailed install layout and CI plan live in docs/distribution.md.

Version bumps, changelog updates, tags, and GitHub releases are managed with release-plz. Maintainers should use Conventional Commits so release-plz can infer the correct SemVer bump. CI enforces this with opensource-nepal/commitlint on pull requests, except for Dependabot's generated dependency update commits.

The repo release flow is:

  1. Push commits to master
  2. release-prepare.yml runs release-plz update, which updates the version and CHANGELOG.md, and commits that release bump back to master
  3. It then starts release.yml for that exact commit and waits for it; if master has moved on by then, the newest push's run redoes the bump instead
  4. release-plz release tags that commit and creates a draft GitHub release
  5. The workflow builds the tar.gz, deb, and rpm assets and packages the crate (plasma-drop-<version>.crate), signs the rpm, and writes SHA256SUMS, one .sha256 sidecar per artifact, and the build provenance bundle plasma-drop-<version>.intoto.jsonl
  6. A separate job signs a packslip.sigstore.json manifest for the tar.gz; every signature is verified before anything is uploaded
  7. All files are uploaded to the draft and compared byte for byte with what was built
  8. The exact attested .crate is published to crates.io (the workflow checks crates.io's checksum against it), then the release is published (immutable from then on when release immutability is enabled) and verified again from its public URLs; only then is the provenance badge updated
  9. The workflow publishes signed RPM/APT repositories and the badge to GitHub Pages (Linux signing)

Crates.io publishing uses trusted publishing through GitHub Actions OIDC. After the first manual crate publish, configure crates.io to trust SkeLLLa/plasma-drop and workflow release.yml; no long-lived Cargo registry token is required for later releases.

Support Ukraine

If plasma-drop is useful to you and you want to say thanks, please consider supporting Ukrainian defenders instead of sending money to the author.

Come Back Alive Sternenko Fund Prytula Foundation

License

GPL-3.0-or-later. See COPYING.

About

KDE Plasma 6 dropdown app launcher for Wayland, with Yakuake-style toggle behavior for any app you configure.

Topics

Resources

Security policy

Stars

26 stars

Watchers

0 watching

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages