aboutsummaryrefslogtreecommitdiffhomepage
path: root/checker/check.mllib
diff options
context:
space:
mode:
authorGravatar gareuselesinge <gareuselesinge@85f007b7-540e-0410-9357-904b9bb8a0f7>2013-08-20 12:43:43 +0000
committerGravatar gareuselesinge <gareuselesinge@85f007b7-540e-0410-9357-904b9bb8a0f7>2013-08-20 12:43:43 +0000
commita928ebd8fe429c9208586b7ca21e9f75a6c77dd7 (patch)
treee851b245d74977b670bb7f92eb6b863594adff58 /checker/check.mllib
parent645d960c5267b7b79ed0623a494588f7043ccce4 (diff)
CoqIDE: fixed detection of edits in the locked zone
Trying to understand if the edit concernes the processed zone from the begin_user_action callback was a bad idea, the callback cannot reliably know where the edit takes place (E.g. insert mark means nothing: one can copy from the insert point but paste elsewhere). The callbacks delete_range and insert_text do know where the edit is and can ask coq to backtrack if needed. If coq is busy, the user action is cancelled (the locked zone cannot be unlocked). git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/coq/trunk@16715 85f007b7-540e-0410-9357-904b9bb8a0f7
Diffstat (limited to 'checker/check.mllib')
0 files changed, 0 insertions, 0 deletions