[Octave-bug-tracker] [bug #44701] external editor interactions with GUI

[Rik]

URL:
  <http://savannah.gnu.org/bugs/?44701>

                 Summary: external editor interactions with GUI
                 Project: GNU Octave
            Submitted by: rik5
            Submitted on: Thu 02 Apr 2015 08:34:43 AM PDT
                Category: GUI
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

I have the GUI preferences set to use an external editor ('gvim -f').  When I
merely click away from the Command Window to the Editor tab a new blank
document is created in the external program.  I understand that it is always
nice to have a space to type in with the built-in editor, but I don't think an
external process should be launched unless the user does File->New.

Second, when I set a breakpoint the external editor is also launched
automatically.  For example:

+verbatim
dbstop ls


I don't think this is necessary either.  If I'm using the Command Window I
might just use dbwhere, dblist, dbtype to see the code.  And if I want to see
it I can always use 'edit FILENAME'.

What's worse is that the new editor windows just keep coming.  If I have an
open window created by 'dbstop ls', then running 'ls' will stop at the first
breakpoint and open up a new editor window.  And every dbnext statement after
it will open up a new window.







    _______________________________________________________

Reply to this item at:

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

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