You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
kill accepts signal names regardless of the casing: #6217
timeout accepts signal names regardless of the casing (this issue):
$ cargo run -q --features timeout timeout -s TeRm 0.1 sleep 999timeout: 'TeRm': invalid signalTry 'target/debug/coreutils timeout --help' for more information.[$? = 125]
$ timeout -s TeRm 0.1 sleep 999[$? = 124]
env accepts signal names regardless of the casing (found while reviewing #6377):
$ env --ignore-signal=tErM sleep 0.1
$ env --ignore-signal=invalid sleep 0.1 # and it really tries to parse it!env: 'invalid': invalid signalTry 'env --help' for more information.[$? = 125]
That's all current (and probably all future) callers of uucore::signals::signal_by_name_or_value (uucore/src/lib/features/signals.rs:342). Therefore, I suggest that we change the implementation of signal_by_name_or_value to accept any casing, which would simplify kill, fix timeout, and prevent a bug in env.
The text was updated successfully, but these errors were encountered:
kill
accepts signal names regardless of the casing: #6217timeout
accepts signal names regardless of the casing (this issue):env
accepts signal names regardless of the casing (found while reviewing #6377):That's all current (and probably all future) callers of
uucore::signals::signal_by_name_or_value
(uucore/src/lib/features/signals.rs:342
). Therefore, I suggest that we change the implementation ofsignal_by_name_or_value
to accept any casing, which would simplifykill
, fixtimeout
, and prevent a bug inenv
.The text was updated successfully, but these errors were encountered: