From bdf2bbc22e587dddc0ab63487059bd41b6132841 Mon Sep 17 00:00:00 2001 From: Myk Taylor Date: Sun, 11 Oct 2020 22:15:01 -0700 Subject: [PATCH] remove reference in docs to unimplemented behavior I never implemented ignoring spaces in alias definitions, and now that I've thought more about the consequences, I don't plan to : ) Ignoring spaces would lead to conusing behavior when players attempt to give names with spaces to buildings --- dfhack-config/quickfort/aliases.txt | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/dfhack-config/quickfort/aliases.txt b/dfhack-config/quickfort/aliases.txt index c5d34ec39..2b90e67c4 100644 --- a/dfhack-config/quickfort/aliases.txt +++ b/dfhack-config/quickfort/aliases.txt @@ -22,12 +22,12 @@ # # For example, say you have the following build and place blueprints: # -# #build start(4;1;upper left corner of stockpile) build masonry workshop +# #build masonry workshop # ~, ~,~,`,`,` # ~,wm,~,`,`,` # ~, ~,~,`,`,` # -# #place start(4;1;upper left corner of stockpile) place stockpile for mason +# #place stockpile for mason # ~,~,~,s,s,s # ~,~,~,s,s,s # ~,~,~,s,s,s @@ -63,9 +63,7 @@ # keycode from the DF interface definition file (data/init/interface.txt), # enclosed in curly brackets like an alias, like: "{Right}" or "{Enter}". In # order to avoid naming conflicts between aliases and keycodes, the convention -# is to start aliases with a lowercase letter. You can add spaces in between -# keystrokes to make them easier to read. Spaces in keystroke sequences will be -# ignored. To insert a literal space, use "{Space}" +# is to start aliases with a lowercase letter. # # Anything enclosed within curly brackets can also have a number after it, # indicating how many times that alias or keycode should be repeated. For