Sat 12 Oct 2013 07:36:41 PM UTC, comment #9:
From my tests a year ago it can be concluded that this is in no way a crash. The Del key had unexpected/undesired effects on MinGW => "Incorrect result" would be a better description.
Presently, with an MXE (= MingW) built Octave 3.7.7+ (17644:b26499314482, from this afternoon), on Win7 & WinXP:
-octave-cli.exe catches Del (that is: I hear the system bell and Octave is otherwise unaffected)
-octave (GUI): Del works as it should (deletes char under cursor, left shift all chars to the right)
We can conclude that this bug has "somehow been fixed".
Closing report....
|
Sat 12 Oct 2013 04:50:40 AM UTC, comment #8:
This is listed as a crash, but against an old version of Octave (3.6.2).
Philip,
Do you still have this problem with the delete key and MinGW on the development branch?
|
Sat 03 Nov 2012 04:48:40 PM UTC, comment #7:
Some tests:
- MinGW (MSYS) shell: <Del> doesn't end the shell, <Ctrl>-d does;
(on a blank line:)
- Octave-3.4.3_gcc4.5.2: <Ctrl>-d closes Octave, <Del> does nothing.
- Octave-3.6.2_MSVC2010 (both GUI and CLI): <Ctrl>-d closes Octave, <Del> does nothing.
- Octave-3.6.1_gcc4.6.2: both <Del> and <Ctrl>-d close Octave;
- Octave-3.6.2_gcc4.6.2: both <Del> and <Ctrl>-d close Octave;
Starting an MSYS shell using
<Octave3.6.2_gcc4.6.2>/msys/msys.bat
gives me a shell that doesn't close on <Del>
So, apparently for the 3.6.x MinGW versions the Octave terminal should be adapted to catch <Del>. Maybe this is an easy fix, but I wouldn't know where to search.
BTW I'd rather mark this bug as "postponed" (= until someone finds time & priority to fix this) than "won't fix"
Adapted title so that it is clear that only MinGW binaries are affected.
|
Tue 30 Oct 2012 09:15:08 PM UTC, comment #6:
It seems to me that allowing delete to exit Octave
on Windows systems is high risk for those users.
Is there any way to trap the delete character before
it causes exit? This would only be needed for Windows.
|
Tue 30 Oct 2012 07:33:28 PM UTC, comment #5:
> However key mappings are done in Windows should
> be able to produce the same behavior.
It may be impossible to distinguish delete and ctrl-d on Windows depending on the terminal emulator. We might be able to do this on the GUI since that's our own terminal emulator.
I'm tempted to mark this bug as wontfix since we can't control cmd.exe.
|
Tue 30 Oct 2012 05:52:37 PM UTC, comment #4:
In linux delete in a blank line does nothing,
ctrl-d terminates Octave as it should.
However key mappings are done in Windows should
be able to produce the same behavior.
|
Tue 30 Oct 2012 05:46:31 PM UTC, comment #3:
It is expected with ctrl-d, which is an alias to delete. Try it, you can do ctrl-d or hit delete to delete. With a blank line you're sending an end-of-file character to Octave which is a signal to exit.
|
Tue 30 Oct 2012 05:32:42 PM UTC, comment #2:
Yes, this also happens when holding the Ctrl key down and pushing the "d" key. Expected behavior??
|
Tue 30 Oct 2012 05:19:41 PM UTC, comment #1:
Does this happen if you hit "ctrl-d" too? If so, this may be expected behaviour.
|
Tue 30 Oct 2012 05:10:37 PM UTC, original submission:
Pushing the keyboard "Delete" key on a blank line causes Octave to immediately exit. Other than that, command line editing works as expected, including the function of the Delete key. Using a
diary file shows everything in the session up to and including the last Octave prompt, with no error messages. An "octave-core" files is not written.
Windows XP SP3 32 bit, up-to-date.
Octave installed from MinGW file:
Octave3.6.2_gcc4.6.2_20120609.7z
|