^P vs sanity_check
Normally when sanity_check is enabled it will take place for every command executed. Avoid that when the command is ^P because if a sanity warning is a recurring one and the msg_window setting is single or combination (tty-only) which shows one message, ^P will just repeat each new warning without having any chance to cycle back to earlier messages.
This commit is contained in:
@@ -1187,6 +1187,9 @@ don't exclude map column 1 from consideration when rloc() picks a random spot
|
||||
for destination of a teleported monster
|
||||
covetous monster attacking another monster to acquire special item would not
|
||||
do so if positioned diagonally adjacent
|
||||
skip sanity_check handling when current command is ^P, otherwise it might
|
||||
re-trigger and show new sanity warning every time when set for
|
||||
line-at-a-line feedback
|
||||
|
||||
|
||||
Fixes to 3.7.0-x General Problems Exposed Via git Repository
|
||||
|
||||
Reference in New Issue
Block a user