[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #60079] (Windows) Ctrl-C / Ctrl-V dysfunctiona
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #60079] (Windows) Ctrl-C / Ctrl-V dysfunctional in Command Window |
Date: |
Thu, 27 May 2021 23:54:04 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 |
Update of bug #60079 (project octave):
Status: In Progress => Ready For Test
_______________________________________________________
Follow-up Comment #37:
The following changeset seems to fix the interrupt problem for me:
http://hg.savannah.gnu.org/hgweb/octave/rev/97e12df28ee6
I thought gnulib provided a kill function that accepts pid and signal
arguments but it does not and kill is not available on Windows systems. So if
kill is not available, we just use raise instead to trigger the signal
handler. As it was, nothing was happening when calling kill, so Octave never
received the interrupt signal that we were trying to send.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60079>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #60079] (Windows) Ctrl-C / Ctrl-V dysfunctional in Command Window,
John W. Eaton <=