Depends on whether you have a SyntaxErrorNotification or a SemanticError. For SyntaxErrorNotifications, you can wrap in a handler block raising a debugger (and will see at which index in source the error is for). Handling automatically is very kludgey without changes to the way OpalCompiler fetches source, which isn't really easily available to edit and resume from SyntaxErrorNotification handling code outside the scope of a controlling SourceEditor.
For SemanticErrors, you're currently SOL, as they have a handling block in the compiler, rather than being raised and, only if unhandled, use a default action which notifies/logs dependent on whether compilation is interactive or not. -- View this message in context: http://forum.world.st/How-to-grab-a-debug-on-Syntax-Error-tp4950809p4950951.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
