shell-scripts
dotfiles
shell-scripts | dotfiles | |
---|---|---|
1 | 3 | |
0 | 28 | |
- | - | |
0.0 | 7.1 | |
about 3 years ago | about 2 months ago | |
Python | Shell | |
- | Do What The F*ck You Want To Public License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
shell-scripts
-
How to navigate directories faster with Bash (2015)
Here's my answer to that, an 'nd' (newdir?) alias that calls this python script:
https://github.com/danwills/shell-scripts/blob/bb989985d270c...
This makes all directories with names provided by args, including spaces and multiple levels (slashes) at once. It then enters the resulting directory as well (when aliased including 'cd' as advised in the comment).
dotfiles
-
The bash book to rule them all
> An interactive shell can be a login-shell or a non-login-shell.
A shell can be login and non-interactive.
This happens e.g when starting a session from a X session manager. Subsequently a terminal such as Xterm starts non-login interactive sessions.
Similarly doing ssh starts a non-interactive login shell.
> However, bash behaves like an interactive non-login shell in this case and reads `bashrc`.
IIRC nope: distros such as Debian often have bashrc source bash profile (or the other way around, I can't recall) which has me irate to no end+. They even have some TTY dependent stuff in profile which spits out some error in some cases when no TTY is allocated because heh not interactive.
+ I took great length to have my rc and profile properly separated because it's that much faster not to source the unneeded stuff. https://github.com/lloeki/dotfiles
-
A Dotfile History
Got a similar repo: https://github.com/lloeki/dotfiles
A couple of differences though.
- there's a setup script to do the basic symlinks, automatically from the files in the "home" subdir by prepending the names with .
- then for shell stuff everything is sourced from either shell, bash, or zsh subdirs, all in modular files
- shell dir content is autoloaded based on +x
- there are polyfills for bash that makes it more zsh-like (stuff like precmd)
- each shell module tests for tool presence and is a noop or sets up a fallback when the tool is not available, so I can clone this on any system and have it still work, gracefully degrading down to zero deps except the shell itself
- it also attempts to provide a uniform experience across bash versions and OSes (darwin, linux)
- prompt is minimal (workdir, dirname only, not the full path), increases with detail progressively and in a hierarchical order (root if root, host if ssh, workdir, vcs branch if in repo, vcs status as symbols if nonempty, venv name if virtualenv, "nix" if in nix shell)
- How to navigate directories faster with Bash (2015)
What are some alternatives?
fasd - Command-line productivity booster, offers quick access to files and directories, inspired by autojump, z and v.
fzf - :cherry_blossom: A command-line fuzzy finder
zoxide - A smarter cd command. Supports all major shells.
nnn - n³ The unorthodox terminal file manager