Scripts for Bash et al.

Description

This is a miscellaneous repository for scripts and small programmes. Be warned that not everything in here may be functional. I have prefixed depricated files with dep-<filename>, and development (i.e., in development) files as dev-<filename>.

Contents

• Description
• Contents
• Installation
• Executing Commands
• In Case of Moving Files Around
• In Case of Finding and Replacing Text Within Files
• A Note on Sourcing Scripts Which Change Directory

---

Installation

Simply run

cd ${HOME} && mkdir -p "${HOME}/projects/" && cd ./projects/ && git clone https://www.github.com/jakewilliami/scripts.git; echo 'export PATH=$PATH:~/projects/scripts/bash' >> ~/.bash_profile && chmod -R u+x ~/projects/scripts/bash && source ~/.bash_profile && scripts

Executing commands

Once the scripts have been written, you will need to add the script location to your path, and then make it exacutable (although, these are done in the installation process). The former can be done by:

echo 'export PATH=$PATH:/path/to/dir' >> ~/.bash_profile

You may need to restart terminal after this step. To make the script executable, simply type (in the directory of your script)

chmod u+x <name_of_script>`

and your script will be executable (from that directory only, until you add it to your path; then it will be executable anywhere).

You only need to do the above for bash scripts (which, for ease of commandifying them, do not have a file extension). Running other kinds of scripts may have different requirements.

Happy scripting!

In Case of Moving Files Around

See commit message git show ef3086a148b7c3f129213e7b438b70d8ad53379a for the original notes on this process. The process of moving files while retaining their commit history is as follows:

1. git filter-branch --tree-filter 'if [ -f <file_to_be_moved> ]; then mkdir <new_dir> && mv <file_to_be_moved> ./<new_dir>/<file_to_be_moved>; fi'. Note that this will fail if the new_dir already exists.
2. If you are doing this more than once, after each move, you will have to run git update-ref -d refs/original/refs/heads/master.
3. Once you are finished moving all of the files you need to move, push by using git push -f origin master.

In Case of Finding and Replacing Text Within Files

I have had trouble replicating Unix-based sed solutions, so I have used perl:

perl -pi -e 's/<term to find>/<term to replace>/g' path/to/file(s)

It should be noted that you must escape any special characters with a \. For example, replacing if [[ $USER = "jakeireland" ]], you want to type

perl -pi -e 's/if \[\[ \$USER = \"jakeireland\" ]]/if \[\[ \$\(hostname) == \"jake\-mbp2017\.local\" ]] && \[\[ \$\(whoami) == \"jakeireland\" ]]/g' bash/*

A Note on Sourcing Scripts Which Change Directory

On this day, 3rd March 2020, I no longer need messy return statements for sourcing scripts. Rather than putting return rather than exit in my bash scripts (which, within the scripts, change the directory), and add in my .bashrc an alias to source them, I did this (for example, for the command which takes me to this git directory):

alias scripts="cd ${HOME}/projects/scripts/; scripts $@"

I've felt dirty for the longest time because of this session madness. Eureka.