KDE Plasma + Brave on Debian

  This is the “how do I make Brave do what I want” note --- especially when Brave profile UI is broken and KDE is strict about .desktop launchers. 1) Know what you’re running. Check where Brave comes from. which brave-browser If it returns /usr/bin/brave-browser , you’re on the APT-installed build (good, predictable). Also note that on Debian you often have both commands available. brave-browser is commonly a wrapper. brave-browser-stable is commonly the actual binary. 2) Where Brave stores its data. Default Brave user-data root (APT install). ~/.config/BraveSoftware/Brave-Browser/ If you only see Default/ , then you effectively have a single Brave “profile” in that directory. 3) Multiple isolated Brave sessions without Brave profiles. This is the clean workaround: run separate user-data directories . Create a new isolated environment. mkdir -p ~/.config/BraveSoftware/Brave-RDT Launch Brave using that directory. brave-browser-stable --user-data-dir= ...

Capitalisation in Linux

There’s no strict standard, but there is a clear Unix culture:


Commands → lowercase

If something is meant to be run like a system tool, it stays lowercase and has no extension.
Examples I use:

  • lcs (an acronym, which in normal language should all be written in capital letters)

  • backup

  • autorotate

Lowercase feels like a real command.


Scripts → lowercase + .sh

If it’s a helper script or automation that I run as a file (not a tool), lowercase with .sh is the normal style.
Examples:

  • update.sh

  • autorotate-wayland.sh

Lowercase says “this is a local script,” .sh says “you can open and edit me.”


Directories → depends on role

  • normal folders → lowercase (projects, scripts, notes)

  • acronyms or mount points → UPPERCASE

    • /mnt/LCS

    • /mnt/ISO

    • /mnt/VM

Uppercase makes special-purpose folders stand out, especially for devices and acronyms.

The rule I’m keeping

  • lowercase for commands

  • lowercase + .sh for scripts

  • UPPERCASE allowed for directories

Comments