# 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"
~
        • narc0tic_bird@lemm.ee
          5·
          19 days 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.

    • Draghetta@lemmy.world
      18·
      19 days ago

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

        • Draghetta@lemmy.world
          2·
          19 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.worksEnglish
            1·
            19 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.

      • linearchaos@lemmy.worldEnglish
        2·
        18 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.

    • user@lemmy.one
      3·
      19 days 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
          3·
          19 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
            1·
            19 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)

  • SavvyWolf@pawb.socialEnglish
    161·
    19 days 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.

    • Virual@lemmy.dbzer0.comEnglish
      11·
      19 days 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.

      • SavvyWolf@pawb.socialEnglish
        8·
        18 days ago

        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.

  • myrmidex@slrpnk.net
    2·
    19 days ago

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

  • BananaTrifleViolin@lemmy.worldEnglish
    11·
    18 days ago

    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

  • razorozx@lemm.eeEnglish
    3·
    18 days ago

    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.