From 7057af668bb478233ffb2f517fb5f5c87cc75dcb Mon Sep 17 00:00:00 2001
From: Runxi Yu <me@runxiyu.org>
Date: Thu, 05 Dec 2024 20:08:56 +0800
Subject: [PATCH] e^2

---
 Makefile  | 2 +-
 README.md | 6 ++++--

diff --git a/Makefile b/Makefile
index 579aa92e6102905bb8d07cb6a57be38cf90a6cb9..2a4029d2ea03a0d4d9cc7f0b70b961037d25ae3c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
 .PHONY: upload
 
 README.html: README.md
-	pandoc -so README.html -c style.css README.md
+	pandoc --mathml -so README.html -c style.css README.md
 
 upload: README.html style.css
 	rsync --mkpath README.html style.css runxiyu.org:/var/www/docs/e2/
diff --git a/README.md b/README.md
index 8d7936dc0359de4212c60368bc0e8971d99b06d7..618783e0934beac6ad8ff581d883b51200d778f7 100644
--- a/README.md
+++ b/README.md
@@ -1,7 +1,9 @@
 ---
-title: e2 language testing space
+title: $e^2$ language testing space
 author: Test_User and Runxi Yu
 ---
+
+Note: The name "$e^2$" (or `e2` in ASCII) is subject to change.
 
 Many languages attempt to be "memory safe" by processes such as reference
 counting, borrow checking, and mark-and-sweep garbage collection. These, for
@@ -14,7 +16,7 @@ memory safe languages) do not handle stack overflows correctly;
 although dynamic allocation failures could be easily handled, correctly-written
 programs could crash when running out of stack space, with no method to detect
 this condition and fail gracefully.
-
+)
 Conventional memory safety features are not our priority, but we may choose to
 include them in the future, likely with reference counting while allowing weak
 pointers to be labelled.

-- 
2.48.1