Etienne

Custom parser supported?

1

Hi, is there support for adding a custom parser by manually specializing a template function? E.g.; ``` struct Foobar { ... }; template const std::vector &cxxopts::OptionValue::as() const { ... }...

lib.rs: restore default SIGPIPE signal handler

8

Rust's start-up code sets the SIGPIPE signal handler to ignored. However the vast majority of the utilities should use the default signal handler for SIGPIPE rather than ignore SIGPIPE. (in...

env: fix regression of `--ignore-signal=PIPE`

2

- revert https://github.com/uutils/coreutils/pull/9614 because `Command::exec()` resets the default signal handler for SIGPIPE, interfering with the option `--ignore-signal=PIPE` - add regression-test for --ignore-signal=PIPE - add FIXME comment about execvp() Fixes https://github.com/uutils/coreutils/issues/9617

stdbuf: use exec instead of forking

15

forking creates a new PID and it not compatible with GNU coreutils implementation. - use `Command::exec()` instead of `Command::spawn()` which forks - add stdbuf test verifying that no forking happens...

After https://github.com/uutils/coreutils/pull/9614 there is a regression in env: ignoring SIGPIPE doesn't work any more, because the rust implementation of `Command::exec()` resets the SIGPIPE signal handler to its default handler (see...

runcon: use `Command::exec()` instead of `libc::execvp()`

2

No need to use the unsafe `libc::execvp()`, the standard rust library provides the functionality via `Command::exec()`.

nice: use Command::exec() instead of libc::execvp()

3

No need to use the unsafe `libc::execvp()`, the standard rust library provides the functionality via `Command::exec()`.