When I compile a document from within TexStudio on my Linux Mint 17 the software reports:
Process started: pdflatex -synctex=1 -interaction=nonstopmode "community-detection".tex
and the log file starts with:
This is pdfTeX, Version 3.1415926-2.5-1.40.14 (TeX Live 2013/Debian)
But when I run exactly the same command from the Terminal I get:
This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded format=pdflatex)
When I run Help > Check LaTeX Installation I get:
which pdflatex: /usr/bin/pdflatex
but running which pdflatex from my Terminal results in:
pdflatex is /usr/local/texlive/2014/bin/x86_64-linux/pdflatex
pdflatex is /usr/bin/pdflatex
pdflatex is /usr/local/texlive/2014/bin/x86_64-linux/pdflatex
pdflatex is /usr/local/texlive/2014/bin/x86_64-linux/pdflatex
So what is the /usr/bin/pdflatex file doing there and which package should I uninstall to get rid of it?
PATH, (2) Start TeXStudio? If you addedPATHto.bashrcand startedTeXStudiovia a menu, then you are in trouble. – daleif Nov 14 '14 at 15:28aptor whatever.) There are instructions here for how to configure things e.g. how to install a 'dummy' package to satisfy dependencies. – cfr Nov 14 '14 at 15:29.bashrccontains the lineexport PATH=/usr/local/texlive/2014/bin/x86_64-linux:$PATH. But I can't see how to set the path for TexStudio. – LondonRob Nov 14 '14 at 15:35PATHin.bashrc. Move it to.profile, log out, and log in again. Then it should work. Wehn TeXStudio make a call to latex it does so though a shell, but that shell may never even run.bashrc, thus we need something else. Add it to.profileand it is set as a global variable (and not just a bash variable) and TeXStudio should to good to go. The.bashrcthing is a common mistake that we are trying to correct. BTW: where from do you have that you should add the PATH variable to.bashrc? – daleif Nov 14 '14 at 16:30.bashrcsins were committed too long ago to remember why I set path in there, but it's all over the internet. Here's a prominent example. – LondonRob Nov 14 '14 at 17:17