[Octave-bug-tracker] [bug #50106] [GUI] Editor keeps track of files even when it is closed

[Philip Nienhuis]

Follow-up Comment #9, bug #50106 (project octave):

@Torsten:
Your first user preference suggestion in comment #7 looks like a good idea; it
at least gives users a choice to make Octave behave Matlab-compatible  (I'm no
ML-compatibility fan beyond pure code compatibility but in this case Matlab
behaves as -IMO- an unwary user would expect)

Your second suggestion makes sense to me, but only if the first preference you
suggest has been set to "keep files open".

The pref for silently reloading externally changed files merely leads to more
confusion, I think. At least, I do not like things happening behind my back.


@Dan: A few observations.

Indeed some confusion comes from the Close button that doesn't close but
merely hides a pane. On Matlab it closes the pane (that's also what the popup
says when hovering over it with the mouse cursor).
More of the confusion can partly be attributed to some sort of ambiguity
between "hidden" and "minimized" editor panes, partly depending on whether
they are docked or not.

In Matlab closing the editor disconnects the open files. Similarly, closing
its Variable Editor also closes the display of those variables - restoring it
doesn't "re-open" variables.

Unlike Octave, Matlab's layout prefs (to be compared to Octave's Window drop
down list) doesn't have a "show editor" setting like there is for workspace
etc.

Another thing is that Octave doesn't seem to open files "exclusively" like
e.g., word processors do. This whole bug report wouldn't be there if Octave
would lock its open editor files as well (or should *that* be a user pref?) -
of course, leaving opening files "read-only" if they were in use/locked by
other processes.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?50106>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/