coreutils issueshttps://gitlab.redox-os.org/redox-os/coreutils/-/issues2018-06-13T19:39:51Zhttps://gitlab.redox-os.org/redox-os/coreutils/-/issues/176Last line of file not displayed by 'cat' command2018-06-13T19:39:51ZJeremy SollerLast line of file not displayed by 'cat' command*Created by: LRjunior*
Open Editor
Write two lines to a file, Save as into /home/user/test.txt
From terminal do
cat test.txt
Second line of the file not shown in terminal*Created by: LRjunior*
Open Editor
Write two lines to a file, Save as into /home/user/test.txt
From terminal do
cat test.txt
Second line of the file not shown in terminalhttps://gitlab.redox-os.org/redox-os/coreutils/-/issues/178Hard-Coded Strings2018-06-13T19:39:51ZJeremy SollerHard-Coded Strings*Created by: dabbydubby*
There are hard-coded strings everywhere in this coreutils basket. How are we supposed to localize this in the future if we want non-english-speakers to be able to use this OS?*Created by: dabbydubby*
There are hard-coded strings everywhere in this coreutils basket. How are we supposed to localize this in the future if we want non-english-speakers to be able to use this OS?https://gitlab.redox-os.org/redox-os/coreutils/-/issues/148ArgParser stripping == from the args2018-06-13T19:39:51ZJeremy SollerArgParser stripping == from the args*Created by: paezao*
Hello,
I'm sending == as args but ArgParser is removing that out of the arguments. That should not be the case because its not an option arg like, for example, color=black. It's just part o a string that Im sendi...*Created by: paezao*
Hello,
I'm sending == as args but ArgParser is removing that out of the arguments. That should not be the case because its not an option arg like, for example, color=black. It's just part o a string that Im sending in.
Ex: echo blabla == bleble
The arguments should be "blabla", "==" and "bleble".
Cheers
https://gitlab.redox-os.org/redox-os/coreutils/-/issues/137Update Readme to show list in checkbox format2018-06-13T19:39:51ZJeremy SollerUpdate Readme to show list in checkbox format*Created by: komawoyo*
Possibly update the readme to list all available/additional essential tools that are/are not included similar to https://github.com/uutils/coreutils to provide a starting point for those interested to contribute m...*Created by: komawoyo*
Possibly update the readme to list all available/additional essential tools that are/are not included similar to https://github.com/uutils/coreutils to provide a starting point for those interested to contribute missing tools
(ignore if coreutils is already feature complete)https://gitlab.redox-os.org/redox-os/coreutils/-/issues/124Fix behavior of cp -r when specifying non-existing destination2018-06-13T19:39:52ZJeremy SollerFix behavior of cp -r when specifying non-existing destination`cp -r a b` should copy a to b if b does not exist, and should copy a to b/a if b does exist, and is a directory`cp -r a b` should copy a to b if b does not exist, and should copy a to b/a if b does exist, and is a directoryhttps://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/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/195Implementing watch command2018-11-11T16:41:48ZJayakrishna SahitImplementing watch commandhttps://gitlab.redox-os.org/redox-os/coreutils/-/issues/198ln feature request: better intuitive syntax LINK=TARGET2020-06-25T03:00:34Zcypaln feature request: better intuitive syntax LINK=TARGETHi all!
ln syntax is very uncertain - every time I use ln I'm confused what is correct "`ln -s LINK TARGET`" or "`ln -s TARGET LINK`"! Of cause I can check man ln or ln --help, but what if we add unambiguous syntax, for example
`ln -s ...Hi all!
ln syntax is very uncertain - every time I use ln I'm confused what is correct "`ln -s LINK TARGET`" or "`ln -s TARGET LINK`"! Of cause I can check man ln or ln --help, but what if we add unambiguous syntax, for example
`ln -s LINK=TARGET`
Then it will be like
```
$ ln -s /lib64=usr/lib
$ file /lib64
/lib64: symbolic link to usr/lib
```
Andrej
(I tried to send this to coreutils@gnu.org mailing list but with no success so I hope you guys could understand me ;)