Hi Uwe, >>>>> Uwe Brauer <o...@mat.ucm.es> writes: > May it is a personal defect of mine. > Let me try to explain this a bit better. For me right now the most > interesting new Latex package is called leanblueprint. It is connected > to the proof checkers, that are currently quite popular.
> If I can make it work for my purpose, I am thinking for writing an > auctex style at least. > Nowe I feel rather uncomfortable to mess around with files that dwell in > elpa > in my case (~/.emacs.d/elpa) > and are *not* under version control! Hmm, then you can separately install ELPA-devel for your daily work and have a repo, under version control, for your experiments. In the experiment repo, *don't run make*. Basically developments/experiments don't need "make" to be run. When you wan't to try byte compile the file to check whether there is compile error/warning, do that manually by emacs -f batch-byte-compile foo.elc . (A shell alias is handy for it.) The repo can be created by either (1) Copy elpa files by "cp -r" into another directory and "hg init" there. (2) Clone the remote AUCTeX repo at savannah by "hg clone git://...". > https://lists.gnu.org/archive/html/auctex-devel/2024-04/msg00113.html > Seems the correct one You don't have to worry about "make". It isn't necessary for your primary purpose. (Actually, I expect you can even run "make" in your repo because, as I said before, the commit by Stephan changed nothing about data extraction from the .git directory. But I recommend to stay away from "make" if you are worrying that something goes wrong.) Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine #Gaza #StopMassiveKilling #CeasefireNOW
