# here is where my aliases go yo
alias alias-edit="vim ~/.local/config/alias_config && source ~/.local/config/alias_config && echo 'Alias updated. \n'"
## Modern cli
alias ls="exa"
alias find="fdfind"
## System 76
alias battery-full="system76-power charge-thresholds --profile full_charge"
alias battery-balanced="system76-power charge-thresholds --profile balanced"
alias battery-maxhealth="system76-power charge-thresholds --profile max_lifespan"
## Maintenance
alias update-flatapt="sudo apt update && sudo apt upgrade -y && flatpak update --assumeyes"
## Misc
alias tree="exa --tree"
## Incus
alias devi-do="sudo incus exec dev0 -- su -l devi"
## Some programs
alias code="flatpak run com.visualstudio.code"
~
vim
Opinion disregarded.
As an aside: I really wish flatpaks would put symlinks or something in ~/.local/bin so you could just run them without the flatpak run boilerplate.
They sorta do.
Flatpak user install puts shims in ~/.local/share/flatpak/exports/bin/. You just need to add it to your path.
I’m pretty sure flatpak system installs are at /var/lib/flatpak/exports/bin/ so you’d just add that to path.
I’d like to one day have the confidence to do upgrade -y
I always do that. Is that bad on pop os/fedora? I wouldn’t know any different. Selectively choose what to update?
Apparently apt has a stroke sometimes. I don’t think I’ve had an update fuck up this bad but it’s better to read the output so you know what changed in case something stops working.
That’s by no means a routine upgrade though, the guy just “upgraded to” backports which you’re not even supposed to do. Not comparable to the soothingly boring apt upgrade of Debian stable.
If you haven’t special requirements then just use Debian stable, and never be worried about an update again.
Headline: MAJOR EXPLOIT FOUND IN NEW LINUX KERNEL VERSION!
Debian: business as usual…
TBH I don’t even remember the last time some actually important bug came out on the kernel, long gone are the days of ptrace-kmod.c and hatorihanzo.c
Or if you like beating your head against a brick wall constantly NixOS is really hard to brick. Any update that fails can just be reverted with a reboot.
Of course the downside is poor documentation, and nothing at all works like you expect it to work. It’s like hey, you want to learn Linux again from scratch? And by the way no two things work the same.
Added the exa aliases. Nice to see pacman points exa to eza as the former is unmaintained.
I think I have a simple function in my .zshrc file that updates flatpaks and runs dnf or zypper depending on what the system uses. This file is synced between machines as part of my dotfiles sync so I don’t have to install anything separate. The interface of most package managers is stable, so I didn’t have to touch the function.
This way I don’t have to deal with a package that’s on a different version in different software repositories (depending on distribution) or manually install and update it.
But that’s just me, I tend to keep it as simple as possible for maximum portability. I also avoid having too many abstraction layers.
I use lsd how is nexa?
