Linux @lemmy.ml InternetCitizen2 @lemmy.world 2 wk. ago

Roast my aliases!

# 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"
~

34 comments

I'd like to one day have the confidence to do upgrade -y
- 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...
  
  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.
- Balls of steel or ironclad backups.
  
  Or, simply, masochism.
  
  You forgot apathy. That's what works for me.
- I believe in you
- 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.
For the Flatpak apt upgrade how about "flapt".
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.
  
  Oh, neat. Surprised that isn't added to the default paths though.
  
  It also still does the annoying name.like.this for binary names rather than just using normal names though.
Quick FYI - Exa is no longer fully maintained; there is a fork called Eza which is maintained. They couldn't take over the original Exa repo as the original creator is unreachable. Eza is in many distros; I've installed it on OpenSuSe Tumbleweed with ease from the factory-oss.

https://github.com/eza-community/eza
- Switched!
You forgot alias the_purge="sudo rm -rf /"
- For French language removal?
  
  Non! Aie pitié, je vous en supplie!
They’re too long. Geez, learn to implement shorthand or acronyms. What are you a monster?

/roast
Nice aliases! But I'm a fan of topgrade for updating
- Why when a simple alias will do?
  
  Laziness, mostly
- Omg yes pls
I use flatpak, pacman, and yay for my software management. I unify the basic needs by using these aliases:

SEARCH fsearch = flatpak search <input> psearch = pacman -Ss <input> ysearch = yay -Ss <input> REMOVE fremove premove yremove LIST flist plist ylist GARBAGE COLLECTION fcg pcg ycg And so on.

Additionally I also gave ucg as well as an all-in-one garbage collector command.
Added the exa aliases. Nice to see pacman points exa to eza as the former is unmaintained.
- I did notice that recently and am planning to move
I use lsd how is nexa?

You've viewed 34 comments.