Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I would have liked to see head, tail, tr, uniq, and cut. I end up dragging over the old "gnuwin32" versions of those to a lot of Windows machines. Those are my go-to tools for quick-and-dirty log analysis.

I know I could use Powershell for those kinds of tasks, and I certainly do make a lot of use of Powershell, but the familiarity of those simple tools and the decades-old "muscle memory" of using them on various Unix, Linux, and Windows boxes makes them hard to ditch.



> I would have liked to see head, tail, tr, uniq, and cut.

The project includes all of those. Or were you talking about the past?


I'm a gigantic idiot who can't read. I was reading the table shell conflicts as all the included commands, and not just as a subset of commands that had shell conflicts.

A gigantic idiot. Sorry.


I read the readme that way too - a table with included utils with conflict status, and a list of intenationally excluded utils.

But the rest are in there:

https://github.com/microsoft/coreutils/blob/3fa7aaf832ffc81d...


Now the readme says

"Note: Any command not mentioned is included in this suite. "

which I found quite confusing. It's a very large set, potentially infinite depending on what the universe of all commands is :)

You should link to the list of all the commands in your package.


I use those commands also to filter output and fee ai agents with that. Tail and Head are my favourites to avoid wasting tokens. Wayy too many fancy build logs messages.


Windows has lacked decent ports of recent GNU tools for a while. I still use some very old ones. It would be great if MS worked on the other tool groups like textutils.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: