162 lines
6.9 KiB
Plaintext
162 lines
6.9 KiB
Plaintext
=Bashrc=
|
|
|
|
Source: https://git.thurstylark.com/vcsh/bashrc.git
|
|
|
|
==Profile==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bash_profile
|
|
|
|
Bash chooses which dotfile to source based on how it gets run. If starting from a login shell, `~/.bash_profile` will get sourced, but if there's not a command in there to source your `~/.bashrc`, you may find yourself having to `exec bash` after starting bash. This can be fixed by adding the following line to your `~/.bash_profile`:
|
|
|
|
{{{class="prettyprint"
|
|
[[ -f ~/.bashrc ]] && . ~/.bashrc
|
|
}}}
|
|
|
|
I also use `~/.bash_profile` for setting numlock while in a tty:
|
|
|
|
{{{class="prettyprint"
|
|
case $(tty) in /dev/tty[0-9]*)
|
|
setleds -D +num # (numlock for X is set in ~/.xinitrc)
|
|
;;
|
|
esac
|
|
}}}
|
|
|
|
The last thing of note in my `~/.bash_profile` is a warning:
|
|
|
|
{{{class="prettyprint"
|
|
# Temporary fix for a systemd bug related to systemd --user timers that run on login
|
|
[[ -z "$DBUS_SESSION_BUS_ADDRESS" ]] && printf "%bWARNING: \$DBUS_SESSION_BUS_ADDRESS is unset! %b\n" "$(tput bold)$(tput setab 1)" "$(tput sgr0)"
|
|
}}}
|
|
|
|
----
|
|
|
|
==Main bashrc==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc
|
|
|
|
Things started getting a little too expansive, so I split off relevant sections into their own files. Now all my individual utilities have their own file, making troubleshooting and adding functionality much easier. You can find info for each file and what it does in its own section on this page.
|
|
|
|
===General config===
|
|
|
|
I'm not going in to detail about every line, but I'll hilight the important parts. The rest should be documented in the script itself.
|
|
|
|
First off, if we're not running bash interactively, there's no use for any of the rest of this, so just skip it.
|
|
|
|
{{{class="prettyprint"
|
|
# If not running interactively, don't do anything
|
|
[[ $- != *i* ]] && return
|
|
}}}
|
|
|
|
Another cool option is actually built in to bash: If you call for a directory without any command before it, just `cd` into that directory.
|
|
|
|
{{{class="prettyprint"
|
|
# If a directory is given without any command, CD into it.
|
|
shopt -s autocd
|
|
}}}
|
|
|
|
This is where all the other utilities, aliases, and functions get pulled in. Anything in `~/.bashrc.d/` ending in `.sh` will get pulled in.
|
|
|
|
{{{class="prettyprint"
|
|
for f in ~/.bashrc.d/*.sh; do source "$f"; done
|
|
}}}
|
|
|
|
This also removes the need for the local bashrc sourcing that I [[https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc?id=30c53ca7224b583ed5068038b697653810e3b94b#n45|had in this file previously]]. If that functionality is needed, simply make a new script in `~/.bashrc.d/` and don't track it with `vcsh`.
|
|
|
|
Ordering can be done by adding numbers to the beginning of filenames. For example: `10-prompt.sh`. Currently, nothing that I use requires that kind of functionality.
|
|
|
|
----
|
|
|
|
==Prompt==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/12-prompt.bash
|
|
|
|
I originally built my prompt using http://bashrcgenerator.com and, while it's a nice tool for visually building a prompt, it has several limitations on what you're able to create with it. But more importantly to me, it generates a rediculously long string, defines and resets color for every single character, uses both a color and bold escape sequence to use light/bright colors, mixes raw escape sequences and subshells running tput, and as a result is utterly unreadable and unmaintainable.
|
|
|
|
So, I replaced it with my own setup that generates the needed color codes on the fly to improve readability. I intentionally put everything in a function and call it immediately so I may use local vars for the color definitions. I didn't really want to leave them around just in case.
|
|
|
|
I'm not completely happy with this solution because it causes each of the tput subshells to execute each time the prompt is printed. I would like to change this to quash the extra output this causes when using `bash -x`, but I would also like to find a solution that minimizes so many subshells just for a prompt, but avoid hard-coding colors so it can be general enough to support any env in which it may be used.
|
|
|
|
----
|
|
|
|
==Aliases==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/10-alias.bash
|
|
|
|
Most of these are simple creature comforts and are commented with sufficient explanation.
|
|
|
|
----
|
|
|
|
==Colored man Pages==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/colored-man-pages.bash
|
|
|
|
Some color changes in `man` are almost essential for readability for me, so I define my own.
|
|
|
|
This can be replicated for any similar program that uses `less` as its pager.
|
|
|
|
----
|
|
|
|
==Get Dell Service Tag==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/getdst.bash
|
|
|
|
I work with Dell machines a lot, and when dealing with hardware problems, it's nice to have the service tag handy. Lucky for me, the service tag is easily retrieveable using `dmidecode(1)`, so I made a function for it.
|
|
|
|
As an added bonus, the `-l` option will print the url for that product's support page.
|
|
|
|
----
|
|
|
|
==Screenshot==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/shot.bash
|
|
|
|
`shot()` used to be much more complicated, but after moving to sway, I found that I couldn't be arsed to reimplement all of its former functionality. It turned out that the majority of the time, I want to select a region, and put it on stdout to be dealt with how I please. If I find that full-screen or all-screen screenshots are more useful to me in the future, I'll cross that bridge when I come to it.
|
|
|
|
|
|
----
|
|
|
|
==Countdown==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/countdown.bash
|
|
|
|
Found this little function when I wanted to add functionality to `shot()`. It takes an integer as an argument, then counts down that number of seconds visually.
|
|
|
|
I no longer use `countdown()` from `shot()` directly, but sometimes will in some sort of pipeline in tandem with it. I found that I want that flexibility out in the open for me to use instead of packed behind a bespoke ui for little benefit.
|
|
|
|
----
|
|
|
|
==FontFind==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/fontfind.bash
|
|
|
|
Sometimes you just need to figure out what font provides a specific character. This function provides that solution.
|
|
|
|
----
|
|
|
|
==Vactivate==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/vactivate.bash
|
|
|
|
I started needing more than one python virtualenv, and I wanted easy access to my own specific file structure. Additionally, I wanted the ability to deactivate the venv like I would exit a child shell. This is the solution that I came up with:
|
|
|
|
{{{class="prettyprint"
|
|
vactivate() {
|
|
local path=~/.venv/$1
|
|
|
|
if [[ ! -d $path ]]; then
|
|
python -m venv $path --prompt "venv: $1"
|
|
fi
|
|
source $path/bin/activate; bash; deactivate
|
|
}
|
|
}}}
|
|
|
|
A caveat to this is that the prompt modification that venv usually applies is not available using this method. If a prompt modification is desired, it needs to be taken care of elsewhere. I take care of it in my prompt setup detailed [[https://wiki.thurstylark.com/Bashrc.html#Prompt|here]].
|
|
|
|
----
|
|
|
|
==Weechat==
|
|
|
|
https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/weechat.bash
|
|
|
|
See: [[Weechat]].
|