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

Commands history and recalling

Command: $ history

File: ~/.bash_history

Syntax:

  • !
    Start a history substitution
  • !$
    Refer to the last argument in a line
  • !n
    Refer to the nth command line
  • !string
    Refer to the most recent command starting with string


Variables:

  • HISTFILE
    The location of the history file
  • HISTFILESIZE
    The maximum number of lines in the history file (default 500)
  • HISTSIZE
    The maximum number of commands in the history file
  • HISTCONTROL
    How commands are stored
  • HISTIGNORE
    Which command lines can be unsaved
Shortcuts:
  • CTRL+R
    Searches a previous command
  • !!
    Executes the last command


© 2022 edX Inc.

Comments

Post a Comment