[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53702] GUI editor break points use out-of-dat

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #53702] GUI editor break points use out-of-date line numbers when a file is modified
Date: Sat, 7 Sep 2019 10:09:03 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #11, bug #53702 (project octave):

I've been looking at GUI<->interpreter threading issues and came across this
bug report.

A newline at the command prompt "fixes" the problem because it updates the
value of the Vlast_prompt_time variable and that is used to determine whether
to check for out of date functions.  Skipping that check between prompts is
done for efficiency.

I think we need a way to bypass that check when updating breakpoints for a
specific file.  I was initially tempted to simply to update the last prompt
timestamp when saving a file, but then saving a file in the editor while the
interpreter is busy would cause any functions to be checked and possibly
parsed again, which could result in different behavior from what would happen
if you saved a file with an external editor.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]