we probably should not do these options for our cut-like:
-b list Cut based on a list of bytes. Each selected byte shall be
output unless the -n option is also specified. It shall not
be an error to select bytes not present in the input line.
-c list Cut based on a list of characters. Each selected character
shall be output. It shall not be an error to select
characters not present in the input line.
these seem more suited to a matching tool or finding tool like a grep-like
we probably should not do these options for our cut-like:
```
-b list Cut based on a list of bytes. Each selected byte shall be
output unless the -n option is also specified. It shall not
be an error to select bytes not present in the input line.
-c list Cut based on a list of characters. Each selected character
shall be output. It shall not be an error to select
characters not present in the input line.
```
these seem more suited to a matching tool or finding tool like a grep-like
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What should the Bonsai equivalent look like? Ripped straight from POSIX? Or should there be improvements / simplifications?
The POSIX man page for cut(1) looks complex but not terrible to implement as-is.
we probably should not do these options for our cut-like:
these seem more suited to a matching tool or finding tool like a grep-like
(-d delimiter)shouldn't be limited to one byte.cut -d " - "should be possible.Rather than cut(1p), perhaps it should be fis(1) - field isolator.
cut(1)to `cut(1p)`-like`cut(1p)`-liketo `fis(1)` – field isolator