Open GoogleCodeExporter opened 9 years ago
I don't have a strong opinion on this. It's fairly easy to extend the default
garglk.ini to disable the Glk abbreviations by default:
# Adrift game types
[ *.taf ]
terp scare -na
This doesn't address the advantage of removing the aliases at the SCARE level,
though. How common are the conflicts between the short commands and custom game
commands?
Original comment by bcressey@gmail.com
on 14 Jun 2012 at 8:28
Not very common, but I did encounter a problem with one game that required a
phrase starting with "I " to be entered and that triggered the inventory
instead, so it is not just a theoretical problem.
From the user's perspective, I think it would be best to disable the
abbreviations in SCARE, since the abbreviation handling at the Glk level is
superior (visible expansion, bypass and enable/disable).
It seems that SCARE still has active upstream development, so from a
maintainer's perspective I can imagine it's easier to minimize changes to the
interpreter.
Would it be an option to add a #define for disabling the SCARE abbreviations at
compile time and commit that patch for garglk as well as offering the patch to
the upstream project?
Original comment by mthuu...@gmail.com
on 14 Jun 2012 at 9:57
Yes, the #define option sounds like the best approach.
Original comment by bcressey@gmail.com
on 14 Jun 2012 at 11:28
Original issue reported on code.google.com by
mthuu...@gmail.com
on 7 Feb 2012 at 10:16