coreutils issueshttps://gitlab.redox-os.org/redox-os/coreutils/-/issues2018-07-15T19:31:58Zhttps://gitlab.redox-os.org/redox-os/coreutils/-/issues/120simpler interface to ArgParser2018-07-15T19:31:58ZJeremy Sollersimpler interface to ArgParser*Created by: DaanHoogland*
ArgParser now only takes two possible arguments for one option (a &char and a string) and then you need to check for each. Does it make sense to have a list of possible arguments that are either &char or strin...*Created by: DaanHoogland*
ArgParser now only takes two possible arguments for one option (a &char and a string) and then you need to check for each. Does it make sense to have a list of possible arguments that are either &char or string and to have to only check for a symbolic name or for either of the possibilities to fill the option/set the flag?
```
parser.setflag("gurbling",&'g');
parser.setflag("gurbling","gurblingFlag");
if parser.found("gurbling") {} // == true even when --gurbling is passed on cli (or of course -g or --gurblingFlag)
```
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/118How about using this one https://github.com/uutils/coreutils?2018-07-15T19:31:58ZJeremy SollerHow about using this one https://github.com/uutils/coreutils?*Created by: lygstate*
https://github.com/uutils/coreutils
To reduce the work of redox-os,*Created by: lygstate*
https://github.com/uutils/coreutils
To reduce the work of redox-os,https://gitlab.redox-os.org/redox-os/coreutils/-/issues/102How to deal with colons in paths?2019-09-29T01:19:35ZJeremy SollerHow to deal with colons in paths?*Created by: watafalk*
Since `:` is a delimiter in `<scheme>:<reference>`, it is forbidden to create a file with a colon in its name directly:
```
$ touch a:b
error: other os error
```
but there is a way to bypass it:
```
$...*Created by: watafalk*
Since `:` is a delimiter in `<scheme>:<reference>`, it is forbidden to create a file with a colon in its name directly:
```
$ touch a:b
error: other os error
```
but there is a way to bypass it:
```
$ touch file:/root/a:b
$ ls
error: other os error
$ rm file:/root/a:b # problem solved
```
there are also files from the unix world, mostly the manpages for perl, `find /usr/share/man -name "*:*"` shows lots of files.https://gitlab.redox-os.org/redox-os/coreutils/-/issues/89Fix `mv` and `cp` with directory as source2018-07-15T19:31:58ZJeremy SollerFix `mv` and `cp` with directory as sourcemv and cp should check if each source argument is a file before continuing, or cp should implement the -R flag and both should use walkdir to mv/cp every file
mv and cp should check if each source argument is a file before continuing, or cp should implement the -R flag and both should use walkdir to mv/cp every file
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/79implement `sort` command2018-07-15T19:31:58ZJeremy Sollerimplement `sort` commandThere is no `sort` command.
It should sort alphabetically by default, and accept `-n` for sorting numerically
There is no `sort` command.
It should sort alphabetically by default, and accept `-n` for sorting numerically
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/78`sleep` should not accept negative durations2018-07-15T19:31:58ZJeremy Soller`sleep` should not accept negative durations*Created by: xTibor*
The `sleep` command currently accepts negative durations, for example `sleep -1s`, which causes the command to wait indefinitely (possibly integer wrap-around).
It should not accept these durations but should raise...*Created by: xTibor*
The `sleep` command currently accepts negative durations, for example `sleep -1s`, which causes the command to wait indefinitely (possibly integer wrap-around).
It should not accept these durations but should raise errors on them.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/76Human readable sizes2018-07-15T19:31:58ZJeremy SollerHuman readable sizesHuman readable sizes in ls and du
Human readable sizes in ls and du
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/73Date Formatting2018-07-15T19:31:58ZJeremy SollerDate Formatting*Created by: rushsteve1*
The `date` command currently just prints the unix timestamp, and while this works for basic functionality we should look into using something like [rust-chrono](https://github.com/lifthrasiir/rust-chrono) or our...*Created by: rushsteve1*
The `date` command currently just prints the unix timestamp, and while this works for basic functionality we should look into using something like [rust-chrono](https://github.com/lifthrasiir/rust-chrono) or our own implementation to format it into a human readable format.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/71Command Line Argument Parser2018-07-30T21:58:08ZJeremy SollerCommand Line Argument Parser*Created by: msehnout*
So far every utility does argument parsing on its own. It'd be nice to have one standardized way.
I found these crates:
https://github.com/kbknapp/clap-rs
https://github.com/tailhook/rust-argparse
https://github....*Created by: msehnout*
So far every utility does argument parsing on its own. It'd be nice to have one standardized way.
I found these crates:
https://github.com/kbknapp/clap-rs
https://github.com/tailhook/rust-argparse
https://github.com/docopt/docopt.rs
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/66Use clap for parsing options2018-07-15T19:31:58ZJeremy SollerUse clap for parsing options*Created by: hauleth*
It would make code much easier to read.
*Created by: hauleth*
It would make code much easier to read.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/62Adding `timeout`2019-09-29T00:38:11ZJeremy SollerAdding `timeout`*Created by: Kelnozz*
We need to have signals before that so it's related with [#585](https://github.com/redox-os/redox/issues/585) in the main repo.
*Created by: Kelnozz*
We need to have signals before that so it's related with [#585](https://github.com/redox-os/redox/issues/585) in the main repo.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/59how to write unit tests for coreutils tools?2018-07-15T19:31:58ZJeremy Sollerhow to write unit tests for coreutils tools?*Created by: Jeeppler*
how to write unit tests for coreutils tools? In which place and how?
*Created by: Jeeppler*
how to write unit tests for coreutils tools? In which place and how?
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/49`mv` should accept multiple source arguments2018-07-30T21:58:08ZJeremy Soller`mv` should accept multiple source arguments*Created by: skylerberg*
We currently support `mv SOURCE DEST`, but we don't support `mv SOURCE... DIRECTORY` in which there are multiple source arguments and the final argument is a directory. In this case, each source argument should ...*Created by: skylerberg*
We currently support `mv SOURCE DEST`, but we don't support `mv SOURCE... DIRECTORY` in which there are multiple source arguments and the final argument is a directory. In this case, each source argument should be moved to the directory. Examples of where this would be useful:
`mv foo bar baz/`
`mv foo/* bar/` This will be expanded into multiple source arguments.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/44Consider reusing rust coreutils?2018-07-15T19:31:58ZJeremy SollerConsider reusing rust coreutils?*Created by: Seldaek*
I'm not sure if you willingly reimplemented these or if you didn't know about the project but https://github.com/uutils/coreutils/tree/master/src has rust impl of many coreutils already. Using these might let you f...*Created by: Seldaek*
I'm not sure if you willingly reimplemented these or if you didn't know about the project but https://github.com/uutils/coreutils/tree/master/src has rust impl of many coreutils already. Using these might let you focus on other aspects of the os.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/43ls panics on binary file2018-07-30T21:58:08ZJeremy Sollerls panics on binary file*Created by: jhod0*
It seems that ls panics on an out-of-range error when given a binary file:
```
# ls test.wav
assertion failed: index < self.len() in rust/src/libcore/slice.rs:510
```
Obviously, this isn't ls's intended use, but I ...*Created by: jhod0*
It seems that ls panics on an out-of-range error when given a binary file:
```
# ls test.wav
assertion failed: index < self.len() in rust/src/libcore/slice.rs:510
```
Obviously, this isn't ls's intended use, but I assume it should detect test.wav is a binary file and give an informative error message.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/42Is there some communication with uutils/coreutils ?2018-07-15T19:31:58ZJeremy SollerIs there some communication with uutils/coreutils ?*Created by: allan-simon*
as their github project https://github.com/uutils/coreutils state to provide a crossplateform implementation, i wanted to know if there was some cooperation between this project and theirs ?
*Created by: allan-simon*
as their github project https://github.com/uutils/coreutils state to provide a crossplateform implementation, i wanted to know if there was some cooperation between this project and theirs ?
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/36Rm should check paths and abort if some of them are not valid2018-07-30T21:58:08ZJeremy SollerRm should check paths and abort if some of them are not valid*Created by: suhr*
This will prevent issues like [removing /usr](https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commit/a047be85247755cdbe0acce6f1dafc8beb84f2ac).
*Created by: suhr*
This will prevent issues like [removing /usr](https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commit/a047be85247755cdbe0acce6f1dafc8beb84f2ac).
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/31Working on Test Command2018-07-30T21:58:08ZMichael Aaron Murphymmstick@pm.meWorking on Test CommandI'm just posting a heads up that I have been working on the test command and will be submitting it to the repository shortly after I finish it in possibly the next 24 hours, or 48 if it takes longer than I expected. There are a lot of ar...I'm just posting a heads up that I have been working on the test command and will be submitting it to the repository shortly after I finish it in possibly the next 24 hours, or 48 if it takes longer than I expected. There are a lot of arguments so it's going to be a rather large drop of code.
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/29Consider removing `fail`s on non-fatal errors.2018-06-13T19:39:52ZJeremy SollerConsider removing `fail`s on non-fatal errors.*Created by: ticki*
*Created by: ticki*
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/24Make the `wc` output aligned.2018-07-30T21:58:08ZJeremy SollerMake the `wc` output aligned.*Created by: ticki*
*Created by: ticki*