You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anyone have thoughts about how to improve it while not duplicating work? From my personal use, I most care about command-line usage (non-tui), and stability of maintenence (when first written, if actively maintained). Occasionally I care about implementation language if it means I have to install an especially modern scripting language on a production machine, or use non-system packaging.
One thing about the Stack Overflow responses is that most of them have example files and commands, is it insane to imagine a standard usage example for each tool?
If you think no action on either side is appropriate, this is the one sort of ticket where that +1 response makes sense.
The text was updated successfully, but these errors were encountered:
is it insane to imagine a standard usage example for each tool?
Do you mean in this repository? I think that would be too much initial work and ongoing maintenance for the value it would deliver. A standard example compatible with a lot of tools would necessarily have to be simple (lowest common denominator). It would also take up space, making the document harder to scan.
Making examples easier to get to is a good idea! What one could do is link to the examples section of the manual for every tool that has one. I'll gladly merge PRs doing that. E.g.:
Howdy! Pretty much the only thing I do on stack overflow any more is update https://stackoverflow.com/questions/91791/grep-and-sed-equivalent-for-xml-command-line-processing about once a year.
Anyone have thoughts about how to improve it while not duplicating work? From my personal use, I most care about command-line usage (non-tui), and stability of maintenence (when first written, if actively maintained). Occasionally I care about implementation language if it means I have to install an especially modern scripting language on a production machine, or use non-system packaging.
One thing about the Stack Overflow responses is that most of them have example files and commands, is it insane to imagine a standard usage example for each tool?
If you think no action on either side is appropriate, this is the one sort of ticket where that +1 response makes sense.
The text was updated successfully, but these errors were encountered: