bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: read -e allows execution of commands (edit-and-execute-command) as t


From: tetsujin
Subject: Re: read -e allows execution of commands (edit-and-execute-command) as the shell's process user
Date: Tue, 30 May 2017 11:05:39 -0400


----- Original Message -----
From: "dualbus" <address@hidden>
To:"George" <address@hidden>
Cc:<address@hidden>, <address@hidden>
Sent:Tue, 30 May 2017 09:19:46 -0500
Subject:Re: read -e allows execution of commands
(edit-and-execute-command) as the shell's process user

 On Mon, May 29, 2017 at 11:40:54PM -0400, George wrote:
 [...]
 > You misunderstand. Being able to use Readline in "read" is great!
And
 > "edit-and-execute-command" may have its uses when invoked from an
 > interactive
 > shell session. But why is "edit-and-execute-command" useful or in
any
 > way desirable in "read"?
 > If you were using "read -e" in a script, and someone wanted to run
 > some commands, they could suspend the script with job control, or
open
 > another
 > terminal window to run some commands. The feature is unnecessary,
and
 > has no business being a part of "read".

 If that's how you feel, then by all means send a patch with your
 proposed changes (i.e. disable "unsafe" Readline functions under
 `read').

If I can't convince the package maintainers that such a code change is
the right thing to do, there's no sense writing a patch for it.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]