Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Combining flags example, combined flags vs flag parameters #997

shervinsahba opened this issue Jul 10, 2019 · 2 comments


None yet
2 participants
Copy link

commented Jul 10, 2019

I believe only one line in the lesson addresses flag combination, giving ls -Fa as an example. (See related PR from 2016).

Could we incorporate flag combinations into an example or repeat their usage later? Practice would help users. For example, based on what users learn in this module one could demonstrate ls -h -a -l -F can be simplified to ls -halF or any other permutation of halF.

Users will undoubtedly come across these combinations if they search online, so they should distinguish them from string based flags like --help. Additionally, I am unsure if a distinction is made between standalone flags such as those above and flags that necessitate parameters like cut -d , -f 1, where combining d and f could throw errors.


(PS. I'm new to collaborating on GitHub and still learning! I'd be happy to script something up if this seems like a worthwhile addition.)


This comment has been minimized.

Copy link

commented Jul 11, 2019

Hi @shervinsahba
Thanks for the issue!

In a lesson which is already very full, what would you take out to make room for this?

My feeling is that combining single-letter options isn't a key learning objective, and the mention we have is enough. I seem to recall that at some point we went through the lesson to ensure that where examples used multiple options, each option had its own hyphen.

Regarding the cut example - I think this usage is explained quite well in the challenge.

Thoughts from the other maintainers?


This comment has been minimized.

Copy link

commented Jul 20, 2019

I'm taking the thumbs up and lack of further discussion as a green light to close this issue.

@gcapes gcapes closed this Jul 20, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.