#shrc

# >>> shrc >>>
export EDITOR='vim'
alias ll='ls -la'
# <<< shrc <<<

#Install

#Installer script (recommended)

curl -LsSf https://raw.githubusercontent.com/tomasky/shrc/master/install.sh | bash

source <(curl -LsSf https://raw.githubusercontent.com/tomasky/shrc/master/install.sh)

#npm

npm install -g @tomasko/shrc
npx @tomasko/shrc ls          # or pnpm / yarn / bun, no global install needed

#MoonBit

moon install kupas/shrc/cmd/shrc

moon add kupas/shrc

#Windows

#Prebuilt binary

curl -LO https://github.com/tomasky/shrc/releases/latest/download/shrc-linux-x86_64
curl -LO https://github.com/tomasky/shrc/releases/latest/download/shrc-linux-x86_64.sha256
sha256sum -c shrc-linux-x86_64.sha256
install -m 755 shrc-linux-x86_64 ~/.local/bin/shrc

#From source

git clone https://github.com/tomasky/shrc && cd shrc
moon build --target native --release
./_build/native/release/build/cmd/shrc/shrc.exe help

#Usage

shrc set EDITOR vim            # environment variable, in every shell
shrc set NAME=VALUE            # same, one argument
shrc set -a ll 'ls -la'        # an alias instead of a variable
shrc set --prepend PATH /opt/bin   # add a directory in front
shrc set --append PATH /opt/bin    # add a directory at the end
shrc set --drop PATH /opt/bin      # remove a directory
shrc set -r EDITOR '$HOME/bin/vi'  # store shell syntax; references stay live
shrc rm EDITOR                 # remove every entry named EDITOR
shrc rm -a ll                  # remove only the alias
shrc ls                        # list managed entries
shrc ls EDIT                   # filter by name
shrc ls PATH                   # search paths, one directory per row, in order
shrc all                       # the manifest and every startup file
shrc init                      # import existing definitions (files untouched)
shrc refresh                   # re-scan and sync the manifest with the files
shrc version
shrc help

eval "$(shrc set EDITOR vim)"
eval "$(shrc rm EDITOR)"

#Applying changes to the current shell automatically

# bash / zsh / POSIX sh
shrc() {
  case "$1" in
    set|rm|remove|unset|delete)
      eval "$(command shrc "$@")"
      ;;
    *)
      command shrc "$@"
      ;;
  esac
}

# fish
function shrc
  switch $argv[1]
    case set rm remove unset delete
      eval (command shrc $argv)
    case '*'
      command shrc $argv
  end
end

#Search paths (PATH and friends)

• shrc set PATH /opt/bin prepends the directory; the previous value is kept through $PATH. --append adds at the end instead, --drop removes a directory, and an identical directory is never duplicated.
• shrc set PATH '/a:/b' (or the PowerShell spelling '/a;/b') replaces the whole list; a value containing $ is stored as live syntax, so shrc set PATH "$HOME/bin:$PATH" keeps expanding per shell.
• Values are stored canonically with : and rendered with each shell's own separator — PowerShell gets ;: $env:PATH = '$HOME/bin;$env:PATH'.
• shrc ls PATH prints the list as a table, one directory per row, in search order, instead of one long line.

#Importing existing configuration

#In-place vs. managed entries

• An entry adopted from a startup file is imported: it stays in its original place. shrc set NAME value edits that line in place; shrc rm NAME removes it.
• An entry created by shrc set on a name that does not yet exist is managed: it lives in the >>> shrc >>> block, and shrc set/shrc rm rewrite the block.
• shrc ls shows both kinds; the manifest marks imported ones with the imported flag (env imported,raw,list PATH ...).

#How it works

• The manifest lives in ~/.shrc/entries and is the source of truth for shrc ls and shrc all.
• A manifest line can carry attributes: raw means the value is shell syntax that stays live (env raw EDITOR $HOME/bin/vi), list means a search path stored with : between directories (env raw,list PATH /opt/bin:$PATH).
• On every change, shrc renders the manifest for each detected shell and rewrites its managed block.
• shrc init imports what the startup files already define into the manifest, so shrc ls shows them; the startup files are not modified.
• A shell is managed when its startup file already exists or it is your login shell; when nothing is found, ~/.profile is used as the portable baseline.

#Environment

#Development

moon check --target native --deny-warn
moon test  --target native
moon fmt
moon info

#License