# 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"
~                                                
    • Draghetta@lemmy.world
      link
      fedilink
      arrow-up
      18
      ·
      1 month ago

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

      • linearchaos@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        29 days ago

        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.

        • Draghetta@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          30 days 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

          • sorrybookbroke@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            1
            ·
            30 days 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.

    • user@lemmy.one
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      1 month ago

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

        • Draghetta@lemmy.world
          link
          fedilink
          arrow-up
          3
          ·
          30 days 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.

          • MicrowavedTea@infosec.pub
            link
            fedilink
            arrow-up
            1
            ·
            30 days ago

            True, it’s just an example to always look at the output. I’ve definitely used that in Fedora to reinstall packages when something stopped working after an upgrade.

            (Maybe this doesn’t happen by itself in Debian but I wouldn’t trust Ubuntu for example)