tomfromberlin / bashrc

This repo contains my bashrc. I put it on Github to save it somewhere in case I mess up my system. Also, I use this repository to figure out how Github works. So it may happen that strange things happen here.

---

The .bashrc-file

For detailed information about this repo, please refer to the wiki

❗	There is absolutely no warranty of any kind! Use at your own risk!	❗

This .bashrc produces a simple but nice output and is suitable for the average user. If you want more functionality while using e.g. GitHub then you should look for other repos like Voku/dotfiles.

Suggestions are always welcome. If errors occur, I would be grateful for information on this and will take them into account accordingly.

System requirements

This piece is intented to run on a Linux box with Bourne Again Shell (bash) as the default interactive shell.

Note that the amount of time before the command prompt or GUI is available can be increased. Unfortunately, Debian 11 (Bullseye) is - out of the box - a bad example here when it comes to boot times, even without this dot-bashrc. But the weaker the hardware, the longer it can take in principle (that seems logical).

Tested on:

Does not work on:

You will only need the follwing files:

• ~/.bashrc (necessary)
• ~/.shellcfg/logos/example (optional, the term "example" is to be understood as a placeholder)
• ~/.shellcfg/alias (necessary for full functionality)
• ~/.shellcfg/colors (optional, necessary for color prompt and other color gimmicks)
• ~/.shellcfg/functions (necessary for enhanced functionality)
• ~/.shellcfg/what_shell (optional, see also wiki page What the (S)hell)
• ~/.mostrc (optional, contains color definitions for most)
• ~/.dircolors (optional, contains color definitions for less)

Installation of command-not-found-package is recommended!

The ~/.bashrc has to be a script file but without shebang #!/bin/bash. The other files must not be script files, only text files. Otherwise an error message will probably appear.

If any of these files (except for ~/.bashrc) are missing, the shell will still work. However, under certain circumstances (e.g., your /etc/bash.bashrc as well as your ~/.profile don't contain alias definitions or functions) no or at least lesser aliases or functions will then be available. If ~/.shellcfg/colors is missing, the prompt will still appear colored (lack of color support should be the exception), but customization will be more challenging, since you need to use color codes (see wiki page about configuration of the prompt).

Other things that come with the zip file may also be important, but not required.

How to use this

If you want to use this stuff, you need do do a few simple things:

Downloading as ZIP File

When you downloaded the zip file use the following commands:

$ cd ~
$ cp -i .bashrc bashrc.old
$ cd </download/directory/>
$ unzip bashrc-main.zip
$ cd bashrc-main
$ cp -iR .bashrc .mostrc .shellcfg ~/
$ cd ~
$ source .bashrc

Using Git

Its a bit easier to clone the repo with git. The directory will be just called bashrc and you don't have to extract the files. If you want this you can use the following commands:

$ cd ~
$ cp -i .bashrc bashrc.old
$ git clone https://github.com/TomfromBerlin/bashrc
$ cd bashrc
$ cp -iR .bashrc .mostrc .shellcfg ~/
$ cd ~
$ source .bashrc

git should be installed by default on your Linux box. If not, just type sudo apt-get install git (replace apt-get according to your distribution's command, e.g. yum or pacman) in the command line and press Enter.

If you leave it as it is, next time you start an interactive shell, the result looks like this (assuming you have lolcat installed). The colors are slightly different each time you start an interactive shell:

The logo does not appear every time you issue a command. That would be annoying. You can recall the logo at any time with the command lolcat ~/.shellcfg/logos/raspberrypi, or cat ~/.shellcfg/logos/raspberrypi for grayscale output.

If you don't want to see a logo, just rename or delete the file in the ~/.shellcfg/logos/ directory. If the file named "raspberrypi" does not exist (or lolcat can't be found), a small text-based intro with some system information is output. Then the result looks like this:

If you want to change the logo read the wiki page on how to do it.

If lolcat and/or the logo file in ~/.shellcfg/logos directory doesn't exist on your system and you don't see anything at all except the command prompt, the ~/.shellcfg/colors file is probably missing. This is no drama, you can still do your work, albeit less colorful.

The file .mostrc shall provide color definitions for most. It does not work, e.g., with PowerShell 7.3.2 over ssh, so this is to be considered as WIP! This may be removed again if I don't come up with a good solution.

Have fun and be nice.

---

To do

• (Optional) cancel full time job🏴‍☠️
• (Optional) ❓
• (Optional) make profit
• (Optional) become rich 💎🍾