tqdm: add examples

[BuonOmo]

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The page(s) follow the style guide.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known): v4.67.1

[Managor]

I think it's time to return to this PR now that a lot of things have been resolved.

[Managor]

Suggested change

	`zip -r {{backup.zip}} {{dir}} | tqdm --total $(find {{dir}} | wc -l) --unit files --null`
	`zip -r {{path/to/archive.zip}} {{path/to/directory}} | tqdm --total $(find {{path/to/directory}} | wc -l) --unit files --null`

Sadly this makes the command longer but hopefully it clarifies things

[Managor]

Suggested change

	`{{seq 10000000}} | tqdm --total 10000000 | {{command}}`
	`{{seq 10000000}} | tqdm --total {{10000000}} | {{command}}`

[Managor]

We could use tar as the fourth example and use tricks to pipe stderr into stdout together to make it platform agnostic (not sure if 2>&1 or |& is available on all platforms).

Also it would be good if the description noted that it is platform agnostic.

[Managor]

Suggested change

	`zip -r {{backup.zip}} {{dir}} | tqdm --total $(find {{dir}} | wc -l) --unit files --null`
	`zip -r {{backup.zip}} {{dir}} | tqdm --total $(find {{dir}} | wc -l) --unit files --null`
	- Create an archive with tar and create a progress bar (system agnostic, GNU tar uses `stdout` while BSD tar uses `stderr`):
	`tar vzcf {{path/to/archive.tar.gz}} {{path/to/directory}} 2>&1 | tqdm --total $(find {{path/to/directory}} | wc -l) --unit files --null`

Suggested change

	`zip -r {{backup.zip}} {{dir}} | tqdm --total $(find {{dir}} | wc -l) --unit files --null`
	`zip -r {{backup.zip}} {{dir}} | tqdm --total $(find {{dir}} | wc -l) --unit files --null`
	- Create an archive with tar and create a progress bar (system agnostic, GNU tar uses `stdout` while BSD tar uses `stderr`):
	`tar vzcf {{path/to/archive.tar.gz}} {{path/to/directory}} |& tqdm --total $(find {{path/to/directory}} | wc -l) --unit files --null`

I wasn't able to find any compiled info on this on its own (search engines suck), but chatgpt told me that |& is not supported on POSIX sh, pre-4.0 bash, dash or busybox sh. The unsupported shells are so minimal that in my opinion we could use |& , but I want to hear your guys opinion.

[acuteenvy]

2>&1 | also works on busybox sh and dash, |& doesn't.

[Managor]

Yeah sorry, that's what I implied to say. I was asking for opinions if the unsupported landscape is small enough so that we can use use |& for simplicity or if we should go with the option that works everywhere.