commit 4f9a27603c096e6f6a10e0cd789fd1dd279d5853
from: Omar Polo <op@omarpolo.com>
date: Fri Jul 02 09:05:22 2021 UTC

revert 2c16dbd5486 -- macro names can't be reserved words

While one can define a macro using a reserved word as name using
-Dname=val, inside the configuration file it'll fail.

commit - 2c16dbd54867d575f37e145d9f15a0e62e15b025
commit + 4f9a27603c096e6f6a10e0cd789fd1dd279d5853
blob - 49ae340d8bb545fa9e43d534f41fd91248badedf
blob + ff4e363058d1ea6ab0c666d760f78986aa64c2e7
--- gmid.1
+++ gmid.1
@@ -162,6 +162,7 @@ blocks after the macros and the global options is reco
 Macros can be defined that will later be expanded in context.
 Macro names must start with a letter, digit or underscore and may
 contain any of those characters.
+Macros names may not be reserved words.
 Macros are not expanded inside quotes.
 .Pp
 For example: