|
From: | Ruslan |
Subject: | [Octave-bug-tracker] [bug #47295] Keep existing breakpoints after editing file in GUI |
Date: | Mon, 29 Feb 2016 04:47:31 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux i686 (x86_64)) AppleWebKit/537.33 (KHTML, like Gecko) Chrome/27.0.1433.0 Safari/537.33 |
Follow-up Comment #6, bug #47295 (project octave): Well, I'd agree if it only removed the breakpoints when the file was changed externally. But if the file was edited in Octave's own editor, Octave can have tracked where the lines were added or removed and move/delete the breakpoints correspondingly in the process of editing instead of deleting them all. I seem to remember from past experience with Matlab that it did exactly this. It never removed all the breakpoints just because I saved the file. This issue report was actually the result of such painful difference of Octave behavior from Matlab's. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?47295> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |