otty / dotfiles

All tools/Bash-it

Bash-it

bash-it

A community Bash framework: a collection of aliases, completions, plugins and themes for Bash 3.2+.

Detected by bash-it | macOS, Linux |github.com

Sync it bash-it.toml

Sync rules

What travels, what stays, what never leaves

Bash-it in your home directory Every rule on this page, by file

· example.bash Exclude

· aliases/custom.aliases.bash Sync

· completion/custom.completion.bash Sync

· lib/custom.bash Sync

· plugins/custom.plugins.bash Sync

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/bash-it.tomlThe file this page is generated from

id = "bash-it"

name = "Bash-it"

homepage = "https://github.com/Bash-it/bash-it"

description = "A community Bash framework: a collection of aliases, completions, plugins and themes for Bash 3.2+."

# The project's mark, as the Bash-it organisation's avatar — the repository

# publishes no image file of it.

icon = "https://github.com/Bash-it.png"

detect = ["bash-it"]

platforms = ["macos", "linux"]

# Bash-it is installed by cloning it: "Check out a clone of this repo to a

# location of your choice, such as `git clone --depth=1

# https://github.com/Bash-it/bash-it.git ~/.bash_it`" (docs/installation.rst),

# so ~/.bash_it is a checkout and not a config directory. What belongs to the

# user is the custom content, which docs/custom.rst names file by file:

# "For custom scripts, and aliases, just create the following files (they'll be

# ignored by the git repo): aliases/custom.aliases.bash,

# completion/custom.completion.bash, lib/custom.bash,

# plugins/custom.plugins.bash, custom/themes/<custom theme name>/<custom theme

# name>.theme.bash", and "Anything in the custom directory will be ignored,

# with the exception of custom/example.bash".

# The line that loads Bash-it, and BASH_IT_CUSTOM if the user moved the custom

# directory elsewhere, live in ~/.bashrc — that file belongs to the `bash`

# entry, not this one.

paths = [

"~/.bash_it/custom/",

"~/.bash_it/aliases/custom.aliases.bash",

"~/.bash_it/completion/custom.completion.bash",

"~/.bash_it/lib/custom.bash",

"~/.bash_it/plugins/custom.plugins.bash",

]

# custom/example.bash is the one file in custom/ that ships with the clone.

exclude = ["~/.bash_it/custom/example.bash"]

# Aliases, functions and themes the user wrote. Nothing here is an account.

secret = []

# No machine_lines: these are the user's own shell snippets. A custom file

# that exports a machine-specific PATH is possible, but which line that is

# differs per user, and the shell rc that has the same problem is covered by

# the `bash` entry's rules rather than guessed at here.

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/bash-it. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page.