From 043d854e5969b29435c7a66ded253e46a0f3dc5d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rg=20Hohwiller?= Date: Fri, 23 Aug 2024 11:21:12 +0200 Subject: [PATCH] Update tool-vendor-plea.adoc --- documentation/tool-vendor-plea.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/tool-vendor-plea.adoc b/documentation/tool-vendor-plea.adoc index f22d4de3b..f9cc6207a 100644 --- a/documentation/tool-vendor-plea.adoc +++ b/documentation/tool-vendor-plea.adoc @@ -138,7 +138,7 @@ Tools typically can take parameters and options. Please consider best practices from POSIX, GNU, IEE, and Open Group (e.g. see https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html[here]) from the start. Most CLIs violate such rules for no good reason. As an example distinguish between short options (`-h`, `-v`, `-q`, `-f`) that typically can be combined (`-qf` for `-q -f`) and long-options (`--help` or `--version`). -Also a good convention is the end options argument (`--`) that e.g. allows you to delete an accidentally created file named `-f` in bash (via `rm -- -f`). +Also a good convention is the end options argument (`--`) that e.g. allows you to delete an accidentally created file named `-f` in bash (via `rm \-- -f`). === Version