From 615200446f84f67cd090ef1ab5d305634285884d Mon Sep 17 00:00:00 2001 From: David Thurstenson Date: Sat, 5 Jun 2021 18:05:29 -0500 Subject: [PATCH] Bashrc.wiki: Updated links --- Bashrc.wiki | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/Bashrc.wiki b/Bashrc.wiki index 27ad912..996506d 100644 --- a/Bashrc.wiki +++ b/Bashrc.wiki @@ -4,6 +4,8 @@ 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" @@ -30,6 +32,8 @@ The last thing of note in my `~/.bash_profile` is a warning: ==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=== @@ -64,7 +68,7 @@ Ordering can be done by adding numbers to the beginning of filenames. For exampl ==Prompt== -https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/prompt.sh +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. @@ -106,7 +110,7 @@ I intentionally put everything in a function and call it immediately so I may us ==Aliases== -https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/alias.sh +https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/10-alias.bash Most of these are just creature comforts and fairly self-explanitory: @@ -136,6 +140,8 @@ alias screenterm='TERM=screen-256color' ==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 here's how I achieve that: {{{class="prettyprint" @@ -158,7 +164,7 @@ This can also be done 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.sh +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. @@ -178,7 +184,7 @@ As an added bonus, the `-l` option will print the url for that product's support ==Screenshot== -https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/shot.sh +https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/shot.bash This function wraps `maim(1)` and `fb(1)` to simplify my most used options. It uses maim to capture either the full screen, the active window, or a mouse selection to a file, or directly to a pastebin. @@ -265,7 +271,7 @@ This probably isn't the most robust solution, but it works pretty well. Patches ==Countdown== -https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/countdown.sh +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. @@ -293,7 +299,7 @@ This probably isn't the sanest or safest solution to the problem, but it gets th ==FontFind== -https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/fontfind.sh +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: @@ -311,7 +317,7 @@ fontfind() { ==Vactivate== -https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/vactivate.sh +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: @@ -332,6 +338,6 @@ A caveat to this is that the prompt modification that venv usually applies is no ==Weechat== -https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/weechat.sh +https://git.thurstylark.com/vcsh/bashrc.git/tree/.bashrc.d/weechat.bash See: [[Weechat]].