opened
NNRepos
username_0
added more useful examples and removed some old ones. fixes #3504

- [x] The page (if new), does not already exist in the repo.
- [x] The page is in the correct platform directory (`common/`, `linux/`, etc.)
- [x] The page has 8 or fewer examples.
- [x] The PR title conforms to the recommended [templates](/tldr-pages/tldr/blob/master/CONTRIBUTING.md#commit-message).
- [x] The page follows the [content guidelines](/tldr-pages/tldr/blob/master/CONTRIBUTING.md#guidelines).
- [x] The page description includes a link to documentation or a homepage (if applicable).
findstr: edit-page
issue
created
NNRepos
username_0
I haven't completely removed them - I've grouped them into one example. I think it's more concise, and also emphasizes that opts can be grouped.
comment
created
mebeim
username_1
I noticed, still that's not how TLDR pages are meant to be written IMHO. Of course someone could infer the behavior of single command-line options from a long and more complex command, but I've never seen this done. I'd like to see what other more experienced maintainers think. Ping @waldyrious @username_2 :eyes:
comment
created
agnivade
username_2
I agree with @username_1. We always introduce options one by one and let user build them up and combine them as they get familiarized with it. Adding a new option if you think it is very common is fine. But not at the expense of making a page more complicated.

I would suggest you to choose something that you think can be removed and use that space for `{{dir}} | findstr "{{query}}"`
comment
created
NNRepos
username_0
@username_2  your wish is my command
comment
created
NNRepos
username_0
@username_2 good to merge?
comment