Hey,
I just started a new job where I will mainly work on a DSVM (Data Science Virtual Machine), an offering from Microsoft Azure that comes with pre-installed libraries, languages and, amongst other things, emacs. However, after getting in and starting to re-create my .emacs.d I realized that it runs an old CentOS installation for which only emacs 24.3 ([https://centos.pkgs.org/7/centos-x86\_64/emacs-24.3-23.el7.x86\_64.rpm.html](https://centos.pkgs.org/7/centos-x86_64/emacs-24.3-23.el7.x86_64.rpm.html)) is available. Has anyone been in the same situation? I started using emacs with version 26 so I'm not sure exactly what I'll be missing (other than the fact that certain packages already doesn't install, like use-package which I rely heavily on). Is there a way to build a newer emacs on this old CentOS?
On my local machine I have to use Windows, but I can still install Emacs 28 so I'm trying to figure out how I could run emacs locally and use TRAMP or something else to edit and ideally also run things on the DSVM. Does this sound like a reasonable workflow? I'm new to TRAMP, but am trying to figure out the setup as we speak.
To summarize:- Can I build a newer emacs than 24.3 for CentOS 7? I assume not as otherwise someone normally would have done it already (EDIT: MIght have been too fast to post [https://justyn.io/til/compile-emacs-28-on-centos-7/](https://justyn.io/til/compile-emacs-28-on-centos-7/))
\- Are there any obvious issue with the TRAMP workflow outlined above where only emacs is installed locally, but all libraries, Python etc. are installed on the virtual machine/remote that I'm SSH-ing into? Would something simple like running a python mode w/ LSP, Flycheck etc. where all the executables are also on the virtual machine work?