From 921feefb12e7f93c0925188b9b11f2e1fd775e33 Mon Sep 17 00:00:00 2001 From: Eric Blake Date: Sat, 27 Dec 2008 09:38:09 -0700 Subject: doc: mention long option abbreviation * doc/coreutils.texi (Common options): Give example of abbreviating options. * THANKS: Update. Reported by Adam Jimerson. --- doc/coreutils.texi | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/coreutils.texi b/doc/coreutils.texi index 387377345..c2713eb91 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -673,8 +673,15 @@ program description. For example, the @command{env} command's options must appear before its operands, since in some cases the operands specify a command that itself contains options. +Most programs that accept long options recognize unambiguous +abbreviations of those options. For example, @samp{rmdir +--ignore-fail-on-non-empty} can be invoked as @samp{rmdir +--ignore-fail} or even @samp{rmdir --i}. Ambiguous options, such as +@samp{ls --h}, are identified as such. + Some of these programs recognize the @option{--help} and @option{--version} -options only when one of them is the sole command line argument. +options only when one of them is the sole command line argument. For +these programs, abbreviations of the long options are not recognized. @table @samp -- cgit v1.2.3-54-g00ecf