bugGNU Octave - Bugs: bug #44701, external editor interactions with...

 
 

bug #44701: external editor interactions with GUI

Submitted by:  Rik <rik5>
Submitted on:  Thu 02 Apr 2015 03:34:43 PM UTC  
 
Category: GUISeverity: 3 - Normal
Priority: 5 - NormalItem Group: None
Status: FixedAssigned to: None
Originator Name: Open/Closed: Closed
Release: devOperating System: Any

Add a New Comment(Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

Fri 17 Apr 2015 06:25:32 PM UTC, comment #3:

I verified the fix just now. Thanks Torsten. Closing this report.

Rik <rik5>
Project Administrator
Fri 17 Apr 2015 06:19:13 PM UTC, comment #2:

I have pushed changeset
http://hg.savannah.gnu.org/hgweb/octave/rev/23fb65b45d8c
which should fix the issues. In a future version, we should think about a preference whether the custom editor is used during debugging or not (obvioulsy, the editor then has to use the same instance for subsequent calls).

Torsten <ttl>
Project Member
Fri 10 Apr 2015 01:42:53 AM UTC, comment #1:

Torsten, I know you're busy at work. When you get a chance, could you take a look at this. I think this will be easy to code by just checking whether the preference for external editor is set before attempting to open the Editor tab.

Rik <rik5>
Project Administrator
Thu 02 Apr 2015 03:34:43 PM UTC, original submission:

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
-verbatim-

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.

Rik <rik5>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by ttl (Posted a comment)
  • -unavailable- added by rik5
  • -unavailable- added by rik5 (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Fri 17 Apr 2015 06:25:32 PM UTCrik5StatusNone=>Fixed
      Open/ClosedOpen=>Closed
    Fri 10 Apr 2015 01:42:53 AM UTCrik5Carbon-Copy-=>Added ttl

    Back to the top


    Powered by Savane 3.1-cleanup1