Let's document: plan9 - Githubissues

tldr-pages / tldr

📚 Collaborative cheatsheets for console commands

https://tldr.sh

Other

51.56k stars 4.24k forks source link

Let's document: plan9 #5657

Open tansiret opened 3 years ago

tansiret commented 3 years ago

plan 9 is not dead, its just resting.

[ ] ascii
[ ] awk
[ ] basename
[ ] bc
[ ] cal
[ ] cat
[ ] cleanname
[ ] cmp
[ ] date
[ ] dc
[ ] du
[ ] dd
[ ] diff
[ ] echo
[ ] ed
[ ] factor
[ ] fortune
[ ] fmt
[ ] freq
[ ] getflags
[ ] grep
[ ] hoc
[ ] join
[ ] look
[ ] ls
[ ] mk
[ ] mkdir
[ ] mtime
[ ] pbd
[ ] primes
[ ] rc
[ ] read
[ ] sam
[ ] sha1sum
[ ] sed
[ ] seq
[ ] sleep
[ ] sort
[ ] split
[ ] strings
[ ] tail
[ ] tee
[ ] test
[ ] touch
[ ] tr
[ ] troff
[ ] unicode
[ ] uniq
[ ] unutf

sbrl commented 3 years ago

Thanks for requesting this set of pages! Do you want to have a go yourself?

Pages are best created by people who understand the command they are about.

If you do, take a quick read of CONTRIBUTING.md, which guides you through the process of creating a new page here. Then, just simply send a pull request to this repository - and if you need any assistance, just ask :-)

Waples commented 3 years ago

@yutyo do you know https://tools.suckless.org/9base/ ? ^^

tansiret commented 3 years ago

@yutyo do you know https://tools.suckless.org/9base/ ? ^^

I heard Plan 9 from User Space but didn't know Suckless had a variation. Would you suggest to add 9base commands to common instead of opening a different page for plan9?

tansiret commented 3 years ago

It seems like some plan9 commands seem nearly identical to those that already exist in *nix systems, yet their capacity is different. So I am asking you:

Would you prefer a page for plan9 or shall we document the commands in commons?

bl-ue commented 3 years ago

@yutyo I'd say put plan9-specific commands (not available on any other systems) in a new plan9 folder. Otherwise, put them in common, but if they already exist there, do nothing.

sbrl commented 3 years ago

If a command is specific to a single platform, then it belongs in its' own platform directory
If a command is identical across multiple platforms, then it belongs in common
If a command is identical across multiple platforms except 1, then put a version in common for the platforms that are identical, and another version in the specific platform folder for the platform where it is different.

Managor commented 1 month ago

What is the reason that there hasn't been any progress on this front? Are these pages not needed?