Giter Club home page Giter Club logo

coreutils's People

Contributors

allevo avatar argentite avatar bojan88 avatar bors[bot] avatar caseyb avatar dvermd avatar envp avatar federicoponzi avatar fossabot avatar gahag avatar grayjack avatar jeremyvii avatar kaindljulian avatar kegesch avatar ladysamantha avatar marcospb19 avatar michelkansou avatar mkindahl avatar palfrey avatar reastyn avatar rodrigocam avatar silverweed avatar tl-john-vincent avatar tobbez avatar twe4ked avatar zshzero avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

coreutils's Issues

Implement chmod

This is a tracking issue for the chmod util.

Required options and flags in the POSIX standard:

  • R (long: recursive)

Required extension options and flags:

  • ² (long: no-preserve-root)
  • ² (long: preserve-root)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name.
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose a short name.

References

POSIX standard text

Unresolved questions:

None yet

History

Implement cp

This is a tracking issue for the cp util.

Required options and flags in the POSIX standard:

  • f (long: force)
  • H (long: ¹)
  • i (long: interactive)
  • L (long: dereference)
  • P (long: no-dereference)
  • p (long: preserve)
  • R (long: recursive-compat)

Required extension options and flags:

  • r (long: recursive)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name.
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose. a short name

References

POSIX standard text

Unresolved questions:

None yet

History

Implement head

This is a tracking issue for the head utility.

Required options and flags in the POSIX standard:

  • c (long: bytes)
  • f (long: follow)
  • n (long: lines)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name.
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose. a short name

References

POSIX standard text

Unresolved questions:

None yet

History

Options -c and -n implemented by #85

Implement cat

This is a tracking issue for the cat utility.

Required options and flags in the POSIX standard:

  • u (long: ¹)

Required extension options and flags:

  • b (long: number-nonblank)
  • e (long: ²)
  • E (long: show-ends)
  • n (long: number)
  • s (long: squeeze_blank)
  • T (long: show-tabs)
  • t (long: ²)
  • v (long: show-nonprinting)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name.
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose. a short name

References

POSIX standard text
FreeBSD Manual
NetBSD Manual
OpenBSD Manual
DragonFlyBSD Manual

Unresolved questions:

All extension options/flags required are only there because most implementations also do. But there is just another two extensions left for all major versions of the utility, -A, -B and -f. Should those last three be implemented as well?

History

-n, -b, -E and -s implemented by #106

Implement seq

This is a tracking issue for the seq util.

Required options and flags:

  • f (long: format)
  • s (long: separator)
  • t (long: terminator)
  • w (long: equal-width, visible-alias: fixed-width)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name.
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose. a short name

References

Seq Linux
Seq FreeBSD
Seq NetBSD
Seq DragonflyBSD

Unresolved questions:

None yet

History

The -w and -s were implemented by #125
Open issue for -f: #127

Use CString::new instead of CStr::from_bytes_with_nul

Is your feature request related to a problem? Please describe.

let gr_name = CStr::from_bytes_with_nul(string_name.as_str().as_bytes()).expect("failed");

Describe the solution you'd like
Use https://doc.rust-lang.org/std/ffi/struct.CString.html#method.new

It will reduce your code because you will no longer have to construct a Rust string with a \0:

        let string_name = {
            let mut s = name.to_string();
            s.push('\0');
            s
        };

It's already done inside CString::new

Implement tee

This is a tracking issue for the tee utility.

Required options and flags in the POSIX standard:

  • a (long: append)
  • i (long: ignore-interrupts)

References

POSIX standard text

Unresolved questions:

None yet

History

The tool was implemented in the PR #137 with both required options/flags

Implement tail

This is a tracking issue for the tail utility.

Required options and flags in the POSIX standard:

  • c (long: bytes)
  • f (long: follow)
  • n (long: lines)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name.
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose. a short name

References

POSIX standard text

Unresolved questions:

None yet

History

Options -c and -n implemented in #136

Implement chgrp

This is a tracking issue for the chgrp util.

Required options and flags in the POSIX standard

  • h (long: no-dereference)
  • R (long: recursive )
  • H (long: ¹)
  • L (long: ¹)
  • P (long: ¹)

Required extension options and flags:

  • ² (long: dereference)
  • ² (long: no-preserce-root)
  • ² (long: preserve-root)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose a short name

References

POSIX standard text

Unresolved questions:

None yet

History

Implement comm

This is a tracking issue for the comm util.

Required options and flags in the POSIX standard:

  • 1 (long: ¹)
  • 2 (long: ¹)
  • 3 (long: ¹)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose a short name

References

POSIX standard text

Unresolved questions:

None

History

Coreutils_core: Improve docs

We lack examples in the documentation of methods and structures, and also a better module level documentation

Implement wc

Good for beginners, don't require dealing with unsafe.

Implement chown

This is a tracking issue for the chown util.

Required options and flags in the POSIX standard:

  • h (long: no-dereference)
  • H (long: ¹)
  • L (long: ¹)
  • P (long: ¹)
  • R (long: recursive)

Required extension options and flags:

  • ² (long: dereference)
  • ² (long: no-preserve-root)
  • ² (long: preserve-root)

Notes:
¹ : Long name not defined on other implementation of this utility. Implementer must choose a long name.
² : Short name (one letter) not defined on other implementation of this utility. Implementer must choose. a short name

References

POSIX standard text

Unresolved questions:

None yet

History

[BUG] Groups utility not getting some system users that DO exist

Describe the bug
Sometimes, when specifying a user to display it's groups, it error's out cause didn't found the user

To Reproduce
Steps to reproduce the behavior:

  1. groups bin
  2. Unknown user bin

Expected behavior
Should show the groups that the specified user belongs

Screenshots
02-06-2019-16-47

Desktop (please complete the following information):

  • OS: Linux
  • Version: dev branch

Additional context
May be a problem with getgrouplist function on libc crate

[BUG] Pwd don't get logical path

Describe the bug
Pwd is getting physical path instead of logical with --logical parameter

To Reproduce
Steps to reproduce the behavior:

  1. Run pwd with --logical
  2. See error

Expected behavior
For example: Assume that /bin is a link to /usr/bin:
One should get /bin if --logical parameter is specified, /usr/bin otherwise

Desktop (please complete the following information):

  • OS: Linux
  • 0.0.0

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.