avoid using Scintilla's SAVEPOINT mechanism altogether: fixes some destructive commands

 * the only thing gained from (partially) using that mechanism is that no explicit calls to set the dirty-status of a buffer are necessary
 * however it had many disadvantages:
  * setting the buffer clean had to be done manually anyway (see previous commits)
  * when changing Q-Registers without affecting the current document, a flag had to be used to prevent setting the current document dirty
  * last but not least, it introduced a dependency on the order of the destructive operation and its UNDO token.
  * the UNDO token could trigger a SAVEPOINTLEFT notification resulting in additional rubout tokens to be pushed on the stack which screws
    the rubout stack. this can be avoided by clever ordering of the operations
 * using an explicit ring.dirtify() is therefore much better

1 files changed, 1 insertions, 22 deletions

diff --git a/main.cpp b/main.cpp
index 0cea4e9..193d355 100644
--- a/main.cpp
+++ b/main.cpp
@@ -47,30 +47,9 @@ Interface::stdio_vmsg(MessageType type, const gchar *fmt, va_list ap)
 void
 Interface::process_notify(SCNotification *notify)
 {
-	switch (notify->nmhdr.code) {
 #ifdef DEBUG
-	case SCN_SAVEPOINTREACHED:
-		g_printf("SCINTILLA SAVEPOINT REACHED\n");
-		break;
-#endif
-	case SCN_SAVEPOINTLEFT:
-#ifdef DEBUG
-		g_printf("SCINTILLA SAVEPOINT LEFT\n");
+	g_printf("SCINTILLA NOTIFY: code=%d\n", notify->nmhdr.code);
 #endif
-
-		if (!dirty_check_enabled ||
-		    !ring.current || ring.current->dirty)
-			break;
-
-		undo.push_msg(SCI_SETSAVEPOINT);
-		undo_info_update(ring.current);
-		undo.push_var(ring.current->dirty);
-		ring.current->dirty = true;
-		info_update(ring.current);
-		break;
-	default:
-		break;
-	}
 }
 
 static inline void