GamingOnLinux

This Week in Plasma

This Week in KDE Apps

Fedora Magazine

KDE

My bash prompt is just me copying the prompt I have set on fish.

# Prompt
green=$'\e[38;5;2m'
bright_red=$'\e[38;5;9m'
bright_green=$'\e[38;5;10m'
reset=$'\e[0m'

prompt_command()
{
    local exit_status=$?

    if [[ $exit_status != 0 ]]; then
        exit_color=$bright_red
        exit_prompt=" [$exit_status]"
    else
        exit_color=$bright_green
        exit_prompt=""
    fi
}

PROMPT_COMMAND=prompt_command
PS1='\[$green\]\w\[$exit_color\]$exit_prompt\n❯ \[$reset\]'

I have a small issue with this prompt though. Sometimes the ❯ ends up turning white for some reason.

I haven’t had any issues with the kernel yet. The worst thing that I can remember doing is messing up the systemd boot entry on my Arch Linux install.

Yeah. I just found out about it by accident when I ran it with the --help flag.

I’d like to add that you can setup desktop shortcuts pretty easily for Mullvad and TOR browser manual installs. For TOR browser simply run this after opening a terminal in the folder it was extracted to:

./start-tor-browser.desktop --register-app

Same thing should work for mullvad.

It is the default atime option used when mounting if I’m correct. If it’s an ubuntu specific mount option it will be specified in /etc/fstab file.

You can run this to check

findmnt --real

I actually use both in fish. I use aliases for some longer commands. For example I have la as an alias for eza -la --icons=auto --group-directories-first because I don’t really want to see it every time I run la. I use abbreviations for some shorter commands. For example systemctl abbreviated to sys and systemctl --user abbreviated to sysu.

I use Firefox as my main browser. I use the multi-account containers extension in Firefox to seperate my browsing activities. Brave is installed as a backup in case firefox fails me. I use TOR browser for searching for stuff that I don’t want linked to me.

I’m going to guess that the make dependencies are installed explicitly and not as a dependency. You can check the if they are explicitly installed or not with the output from pacman -Qi packagename iirc. If it doesn’t work then try pacman -Qii packagename.

So does yay and/or pacman know that the things I am installing don’t actually depend on the make dependencies?

I’m pretty sure make dependencies aren’t considered dependencies of the package you are installing.