I installed texlive and I want to add it as an environment variable to my Path so that Emacs AucTeX can read it when I start emacs from the GUI or from the command line. So far I've read that emacs only reads files from
Therefore my plan is to add texlive to my path in
.profile to enable emacs GUI to read it and then source
.bashrc in order for emacs that is started inside my non-login interactive GNOME terminal to see the path.
Note: I do not have a
.profile file in my home directory, only in my
/etc directory, and I'd rather not touch that one, but I have a
.bash_profile in my home directory. However I read that
.bash_profile is only run for an interactive login session aka console mode which I don't use.
My plan is to create a
.profile file in my home directory and do the following:
step 1: Create
Step 2: Add texlive environment variable to path in
export PATH=/usr/local/texlive/2018/bin/x86_64-linux:$PATH export MANPATH=/usr/local/texlive/2018/texmf-dist/doc/man:$MANPATH export INFOPATH=/usr/local/texlive/2018/texmf-dist/doc/info:$INFOPATH
Step 3: Source
#Adding this at the bottom or start of .bashrc to source .profile when the terminal is opened. if [-s ~/.profile]; then; source ~/.profile; fi
I know that there is a lot of apprehension towards sourcing
.bashrc due to the risk of causing an infinte loop. However since I am creating a
.profile file from scratch this will not be a problem as it will not contain any code that references
- What do you think of my plan?
- Do you think it will work?
- Do you have any suggestions on how to improve it or perhaps other alternatives
Additional info: My
.bashrc only contains code that sources
~/etc/bashrc and one environment variable that was automatically added by Anaconda:
Keep in mind that I know gnome-terminal can be run as an interactive login shell but I have never done this and don't know if it will impact the performance of my terminal sessions.