commit faf50994d58d2651a2ab1bb1ed94dce1feb246bd
parent 80248375a2810ca5023750fc75a5c4ed70b3d8c3
Author: Kévin Le Gouguec <kevin.legouguec@gmail.com>
Date: Tue, 14 Jan 2025 22:25:05 +0100
Contain the Emacs invasion
Tuck everything under guides/emacs.
Diffstat:
3 files changed, 25 insertions(+), 27 deletions(-)
diff --git a/guides/setups/emacs/AUCTeX.org b/guides/emacs/AUCTeX.org
diff --git a/guides/emacs/windows.org b/guides/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?
diff --git a/guides/setups/windows.org b/guides/setups/windows.org
@@ -1,27 +0,0 @@
-* Emacs setup
-=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~).
-** Emacs
-*** 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?
