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= ...
0

Finding files: globbing, wildcards, command FIND

 To find a file you don't know entirely the name, you do

GLOBBING USING WILDCARDS:

?
Matches any single character

*
Matches any string of characters

[set]
Matches any character in the set of characters, eg [adf] matches any occurrence of a, d, or f

[!set]
Matches any character not in the set of characters

[character1-character2]
Matches any character included in the range (numbers or letters)

[!character1-character2]
Matches any character not included in the range (numbers or letters)


COMMAND: FIND

find -name "*.swp" -exec rm {} ’;’

  • {} is a placeholder. This means that it represents in the command all the results of the search. The results need {} to be virtually represented in the command.
  • ; The semicolon at the end closes each iteration. Therefore, it's related to the iterations, not to the command itself. It can be replaced by \; and +
  • -exec can be replaced by -ok to prompt the permission to execute the command

Comments

Post a Comment