mavcunha / shell

What this is

These are functions and aliases that I use on my daily shell interactions. Most of them are configurations for commands that I type often. You might check this blog post Taking Laziness Seriously for some information behind my motivation.

It is probably more useful to explore the configs directory which contains the bulk of the aliases, functions and tricks I pull on my shell.

Nowadays my current shell is Z-shell. So if you're using bash or other some functions may need changes to work properly.

Loading functions and aliases

In order to keep the files in another place other than my home directory I load all scripts with load.

You can add the follow to your .bash_profile, .zshrc, or similar:

	. /path/to/this/project/load

Then load takes care of loading all configurations, aliases and etc. Mind that every directory defined in load will be sourced recursively, mistakes made on the scripts can lead you to a immediately closing terminal (see bellow for tips on how to fix it).

Directory organization

You will find some directories:

common/ - It gets loaded first, common data and settings go here. configs/ - This is the main directory almost all functions are defined here. bin/ - All purpose scripts not only bash ones, it gets added to your path. dotfiles/ - Some of my dotfiles things like vimrc and gitconfig can be found here.

This directory structure is my personal choice. You can redefine and reorganize it by editing the load script to add/rename/remove directories it should clear how to do it.

Look into the configs directory and explore you might find something useful to you.

"Got myself in trouble, my terminal closes immediately"

I got myself in this situation, sometimes mistakes are made and your bash just closes before you have a chance of fixing it. There are several ways to fix it depending on the tools available to you. Here's a couple of alternatives:

If you can invoke bash from another place like a run on terminal... UI just go for:

>/usr/bin/bash --noprofile --norc

Use an GUI editor to take the offending line from the script and start the terminal again.

If you have another terminal window open just use that window and fix the problem without reloading.