# 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"
~
        • @[email protected]
          3•1 hour ago

          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.

  • SavvyWolfEnglish
    11•8 hours ago

    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.

    • VirualEnglish
      4•5 hours ago

      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.

    • @Draghetta
      9•10 hours ago

      If you haven’t special requirements then just use Debian stable, and never be worried about an update again.

      • TimeSquirrel
        3•8 hours ago

        Headline: MAJOR EXPLOIT FOUND IN NEW LINUX KERNEL VERSION!

        Debian: business as usual…

        • @Draghetta
          2•2 hours ago

          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

          • @[email protected]English
            1•16 minutes ago

            A while back, somewhere around Linux 5.17, some Intel chips in laptops caused the Linux kernal to rapidly set backlight brightness to 100% then zero. This flashing would likely cause it to break. That’s the last one I remember only a year or so ago.

            This only effected arch an it’s varients to my knowledge though, as they were the first to recieve the update, and it was fixed very quickly. To my knowledge nobodies systems were broken from this.

    • @[email protected]
      3•8 hours ago

      I always do that. Is that bad on pop os/fedora? I wouldn’t know any different. Selectively choose what to update?

        • @Draghetta
          1•2 hours ago

          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.

  • @[email protected]
    8•9 hours ago

    They’re too long. Geez, learn to implement shorthand or acronyms. What are you a monster?

    /roast

  • myrmidex
    2•9 hours ago

    Added the exa aliases. Nice to see pacman points exa to eza as the former is unmaintained.