Incidencia #36327

SIGINT should interrupt line-editing

Abrir Fecha: 2016-05-19 00:17 Última actualización: 2016-06-17 23:38

Informador:
Propietario:
Tipo:
Estado:
Cerrado
Componente:
Prioridad:
5 - Medium
Gravedad:
5 - Medium
Resolución:
Fixed
Fichero:
Ninguno
Vote
Score: 0
No votes
0.0% (0/0)
0.0% (0/0)

Details

POSIX 2013 requires SIGINT to interrupt line-editing. Yash 2.41 is just ignoring SIGINT.

http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sh.html#tag_20_117_13_03

If sh receives a SIGINT signal in command mode (whether generated by typing the interrupt character or by other means), it shall terminate command line editing on the current command line, reissue the prompt on the next line of the terminal, and reset the command history (see fc) so that the most recently executed command is the previous command (that is, the command that was being edited when it was interrupted is not re-entered into the history).

http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sh.html#tag_20_117_13_04

If sh receives a SIGINT signal in insert mode (whether generated by typing the interrupt character or by other means), it shall terminate command line editing with the same effects as described for interrupting command mode; ...

cf. http://austingroupbugs.net/view.php?id=347

Ticket History (3/5 Histories)

2016-05-19 00:17 Updated by: magicant
  • New Ticket "SIGINT should interrupt line-editing" created
2016-05-19 00:18 Updated by: magicant
  • Details Updated
2016-06-01 09:01 Updated by: None
2016-06-01 22:47 Updated by: magicant
2016-06-17 23:38 Updated by: magicant
  • Resolución Update from Ninguno to Fixed
  • Ticket Close date is changed to 2016-06-17 23:38
  • Estado Update from Open to Cerrado
Comentario

Fixed in r3633

Attachment File List

No attachments

Editar

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Entrar