options key parsing
OPTIONS=menu_previous_page:\mv BINDINGS=M-v:menu_previous_page both worked, but OPTIONS=menu_previous_page:M-v BINDINGS=\mv:menu_previous_page both failed. Make all four variations work. Tiny change made large by the need to move some things around. The option definition for menu_first_page had a couple of its flag bits swapped. I didn't try to figure out whether that had any impact.
This commit is contained in:
@@ -398,6 +398,11 @@ hero would be blinded and stunned by an Archon's radiance (gaze attack) even
|
||||
applying a polearm to attempt to attack a hidden monster would report "wait!
|
||||
there's a monster hidden there" and display the "remembered, unseen
|
||||
monster" glyph but only use a turn if polearm wasn't already wielded
|
||||
key parsing during options processing was inconsistent between OPTIONS=foo:k
|
||||
BINDINGS=k:foo where k represents a key designation; the OPTIONS form
|
||||
recognized backslash escape sequences but not M-x meta characters,
|
||||
vice versa for BINDINGS (most noticeable for menu interaction keys
|
||||
such as menu_next_page because those can be set via either directive)
|
||||
|
||||
|
||||
Fixes to 3.7.0-x Problems that Were Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user