From cf8a3f15ee1c80b874be10cbdd34496b84560f59 Mon Sep 17 00:00:00 2001 From: Kévin Le Gouguec Date: Tue, 14 Jan 2025 22:48:35 +0100 Subject: Sort guides up a bit --- guides/applications/emacs/windows.org | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 guides/applications/emacs/windows.org (limited to 'guides/applications/emacs/windows.org') diff --git a/guides/applications/emacs/windows.org b/guides/applications/emacs/windows.org new file mode 100644 index 0000000..06cad7e --- /dev/null +++ b/guides/applications/emacs/windows.org @@ -0,0 +1,25 @@ +=nt/INSTALL.w64= provides detailed instructions for compiling Emacs on +recent Windows versions. Here are some additional steps I had to +figure out on my own: +* Mingw-w64 +- Set =$HOME= to =%HOMEPATH%= by changing =db_home= to =windows= in + =c:/msys64/etc/fstab=. +- In addition to =c:\msys64\mingw64\bin=, adding =c:\msys64\usr\bin= + to the system =PATH= allows Emacs to access applications installed + with =pacman=. + - It's not obvious whether the Mingw-w64 =PATH= entries should go + last (in which case Emacs will pick the wrong ~find~ command) or + first (in which case… /everything else/ will pick the wrong ~find~ + command?). At least Emacs has a variable to configure + (~find-program~). +* Compiling +Make sure to specify ~-c core.autocrlf=false~ *when cloning* the Emacs +repository; ~autogen.sh~ gets confused otherwise. +* Configuring +AFAICT one must set the variable ~shell-file-name~ explicitly to +=c:/msys64/usr/bin/bash.exe=, otherwise Emacs's Windows-specific +initialization logic uses a built-in shell ersatz (=nt/cmdproxy.c=). +** TODO =HOME= +Went with the instructions from [[info:emacs#MS-Windows Registry]]; could +maybe use [[info:emacs#Windows HOME]] by setting =HOME= to =%HOMEPATH%=, +to avoid having to spell out my username? -- cgit v1.2.3