Difference between revisions of "BASH Shortcuts"
| Line 7: | Line 7: | ||
== Required .bash_profile File == | == Required .bash_profile File == | ||
| − | If you are a bash shell user, you will also need to have a <code>.bash_profile</code> in your CIFS home directory (the ~ directory) for the shortcuts to work. The contents of the profile should be: | + | If you are a bash shell user, you will also need to have a <code>.bash_profile</code> in your CIFS home directory (the ~ directory) for the shortcuts to work. Use <code>emacs</code> to edit the file with the command: |
| + | emacs ~/.bash_profile & | ||
| + | |||
| + | The contents of the profile should be as given below; best bet is to select the text from the browser, middle click in the emacs window to paste, then save the file.: | ||
<source lang="bash"> | <source lang="bash"> | ||
# .bash_profile | # .bash_profile | ||
| Line 23: | Line 26: | ||
== Main Shortcuts == | == Main Shortcuts == | ||
| + | These shourtcuts should go in a <code>~/.bashrc</code> file. You will want to copy them from the browser and middle click them in an emacs window you started with: | ||
| + | emacs ~/.bashrc & | ||
=== EGR 103 Lab Startup === | === EGR 103 Lab Startup === | ||
| Line 34: | Line 39: | ||
} | } | ||
</source> | </source> | ||
| − | and then if you log out and log back in (or type <code>source ~/.bashrc</code>, from that point forward, '''once you are in the correct directory | + | and then if you log out and log back in (or type <code>source ~/.bashrc</code>, from that point forward, '''once you are in the correct directory''', you can type the command |
<source lang=bash> | <source lang=bash> | ||
get103 N | get103 N | ||
| Line 47: | Line 52: | ||
</source> | </source> | ||
every time. To make a /bin/bash shortcut for that, add the following to your <code>.bashrc</code> file: | every time. To make a /bin/bash shortcut for that, add the following to your <code>.bashrc</code> file: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
<source lang="bash"> | <source lang="bash"> | ||
ltx() { | ltx() { | ||
| Line 72: | Line 66: | ||
} | } | ||
</source> | </source> | ||
| + | Note that to use it, you do not need to include the ".tex" at the end of your file name, but you can. The script will automatically take the extension off whatever you gave as an input. | ||
| + | |||
From that point on, once the <code>.bashrc</code> runs to start your session, you can simply type | From that point on, once the <code>.bashrc</code> runs to start your session, you can simply type | ||
ltx FILE | ltx FILE | ||
Revision as of 14:46, 6 February 2019
The following is a list of shortcuts Pratt students may want to add to their .bashrc profile. This, first of all, assumes that they are using the bash shell. To check this, type
echo $SHELL
If the result is
/bin/bash
than this page applies to you; if not, see the TCSH Shortcuts page.
Contents
Required .bash_profile File
If you are a bash shell user, you will also need to have a .bash_profile in your CIFS home directory (the ~ directory) for the shortcuts to work. Use emacs to edit the file with the command:
emacs ~/.bash_profile &
The contents of the profile should be as given below; best bet is to select the text from the browser, middle click in the emacs window to paste, then save the file.:
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
Main Shortcuts
These shourtcuts should go in a ~/.bashrc file. You will want to copy them from the browser and middle click them in an emacs window you started with:
emacs ~/.bashrc &
EGR 103 Lab Startup
You can create a script to automate the process of getting the tar file, expanding it, and making a local copy. This command should only be used once you have created the appropriate labN folder in your EGR103 folder and should only be used if you have changed into that folder! Type pwd first to make sure you are in the right place! You can add the following to your .bashrc file:
get103(){
LabNum=$1;
wget people.duke.edu/~mrg/EGR103public/Lab${LabNum}Files.tar
tar -kxvf Lab${LabNum}Files.tar
cp -i Lab${LabNum}Sample_S19.tex lab${LabNum}.tex
}
and then if you log out and log back in (or type source ~/.bashrc, from that point forward, once you are in the correct directory, you can type the command
get103 N
where N is the appropriate lab number and this will get the tar file from Dr. G's web space, expand it, and make a local copy of the lab skeleton in labN.tex.
latex and dvipdf in One Command
Now that you need to run both latex and dvipdf to get a PDF file for evince to look at, you may want to have a shorter way than having to type
latex FILE.tex
dvipdf FILE.dvi
every time. To make a /bin/bash shortcut for that, add the following to your .bashrc file:
ltx() {
MyFile=$1;
MyFile=${MyFile%%.*}
if [[ -f $MyFile.tex ]]
then
latex $MyFile.tex
dvipdf $MyFile.dvi
else
echo "*ERROR*: '$MyFile.tex' not found"
fi
}
Note that to use it, you do not need to include the ".tex" at the end of your file name, but you can. The script will automatically take the extension off whatever you gave as an input.
From that point on, once the .bashrc runs to start your session, you can simply type
ltx FILE
or
ltx FILE.tex
and it will run
latex FILE.tex dvidf FILE.dvi
