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

Comparing files and updating them via PATCH

diff
To compare 2 text files or 2 directories

A patch file contains the deltas (changes) required to update an older version of a file to the new one. The patch files are produced by running:
$ diff -Nur originalfile newfile > patchfile
or
$ diff -N -u -r originalfile newfile > patchfile

To apply a patch:
$ patch -p1 < patchfile for an entire directory tree
$ patch originalfile patchfile for a single file


cmp
To compare 2 binary files


$ diff3 FIRST-FILE REFERENCE-FILE SECOND-FILE
To compare 2 files with the referenced one

Comments

Post a Comment