[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #42705] Commands continue to be sent to the te
From: |
Lachlan Andrew |
Subject: |
[Octave-bug-tracker] [bug #42705] Commands continue to be sent to the terminal if breakpoint hit |
Date: |
Mon, 25 Jan 2016 03:20:59 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #7, bug #42705 (project octave):
I like Richard's idea of treating the selection as a script, instead of using
execute_command_in_terminal_signal. It is already easy to copy-and-paste the
selection into the command window. Being able to run text without it
cluttering the command history would be useful new functionality.
As a strawman, I've created a changeset that creates a temporary file and
executes it. It still has several weaknesses (below), but I thought I'd get
your (Torsten's) opinion before going further.
1. If the script is terminated before the end, the temporary file is not
deleted.
2. When it is deleted, a dialog box comes up mentioning that it has been
deleted. (This is related to the bug where that dialog comes up when typing
"delete". Fixing that bug should fix this.)
3. The configure process should check that mkstemp is available.
4. Some of the code should probably be put somewhere else for modularity.
As you know, breakpoints are my current pet project, so I'd like this issue
fixed :)
(file #36159)
_______________________________________________________
Additional Item Attachment:
File name: bug_42705_strawman.cset Size:2 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42705>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #42705] Commands continue to be sent to the terminal if breakpoint hit,
Lachlan Andrew <=