Warning configuration file texmf.cnf not found searched these directories

BlackShift BlackShift 2, 2 2 gold badges 17 17 silver badges 25 25 bronze badges. Add a comment. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually. Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled.

But I decided to switch to Gnome. So, installed necessary packages, removed the ones I did not need and am now using Gnome without any problem. When I opened emacs to compile a tex file something I have been doing for a very long time , it suddenly produced an error:. But if I run xelatex test. So, I tried the solution here. Make sure that your texlive installation directory comes first, both in PATH presumably set in some shell initialization file and also in exec-path which is what emacs uses to find executables.

I'm pretty sure that at initialization, exec-path is set from PATH , but if you change the latter later, the change does not automatically propagate to exec-path. So you have to make sure that any changes to PATH are faithfully reflected in exec-path - otherwise, you will get different versions of the program when you run it from a shell than when it gets executed in emacs , perhaps by AucTeX or something similar.

It is also true as Rusi points out in a comment, that when you start emacs from a shell command line, you might get a different value of PATH than if you start it by clicking on a button in the DE.

That's because PATH is passed from the parent process to the child process in the environment, so emacs might end up with different values of PATH when it is started from a shell than when it is started from the GUI. The problem with the OP's duct-tape as Rusi called it solution is that there are now two places where PATH needs to be set: once in the shell initialization file, so that the shell will pick up the right executable and once in the emacs initialization file so that emacs will do so.

That's a recipe for future problems. It would be better to have a single place where PATH is defined, so that both the shell's environment and the GUI environment would be able to get it, so that when emacs is started either way from them, it would inherit the correct value of PATH without having to worry about it itself N.

B BTW that doing the setenv in the emacs init file is "wrong": when emacs is started from the shell, then the additional directory would be added to PATH twice: once when the shell is initialized and then once more when emacs is initialized. That should not cause problems in finding the correct executable but it is probably less efficient. Sign up to join this community. Jump to bottom. Copy link. VictorKong94 closed this Dec 19, Sign up for free to join this conversation on GitHub.

Already have an account? Sign in to comment. I didn't want to use a broken setup so I actually uninstalled it right away. I could try reinstalling it I ended up doing a manual install for now as talked about on the wiki , but ultimately it would be preferred to have the package manager taking care of this.

Arch replaces texmf. However, this is done when installing texlive-core, which occurs only after texlive-bin is installed and it is the installation of texlive-bin which issues the warning. It can clearly find the file fine because it has no trouble creating formats etc. The later warnings are simply due to the fact that you've only installed a very small fraction of TeX Live and so a lot of stuff which you could have, but don't, is not found.