# 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"
~                                                
  • SavvyWolf@pawb.social
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    11 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.com
      link
      fedilink
      English
      arrow-up
      11
      ·
      edit-2
      11 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.social
        link
        fedilink
        English
        arrow-up
        8
        ·
        11 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.

  • BananaTrifleViolin@lemmy.world
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    11 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

        • narc0tic_bird@lemm.ee
          link
          fedilink
          arrow-up
          5
          ·
          11 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.

  • razorozx@lemm.ee
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    11 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.

  • myrmidex@slrpnk.net
    link
    fedilink
    arrow-up
    2
    ·
    11 days ago

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