dotfiles VS dotfiles

I have a few functions in my bashrc for fast directory navigation.

up <#> - cd .. # times

upto

- find dir in the current path above you and cd to it

down

- find dir in the current tree below you including inside any number of subdirectories and cd to it

https://github.com/robmccoll/dotfiles/blob/master/bashrc#L15...

> 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

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)