>On 5/8/17 1:31 PM, Eduardo Bustamante wrote: >> I think `edit-and-execute-command' shouldn't be allowed under `read -e'. > >There's no compelling reason to disallow it. If a system administrator >wants to unbind certain readline commands (and unset INPUTRC!) to protect >against a specific use case, he is free to do that.
Really? Because this seems like a really needless potential death trap. It shouldn't be the responsibility of distribution maintainers or sysadmins to recognize and disable these bad design decisions. Bash's builtin function "read" has one simple job: read data, return it to the caller. There shouldn't be anything in there about executing commands. Why does read even need a function like this? Is it something that was useful in the days before job control? ##SELECTION_END##
