shellopts 2.0.0.pre.14 → 2.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f1e9e2f138c476cb6af3184dd5e43f8a0f82108d05e4170491c5c46dfb547627
-  data.tar.gz: 9990bee10ffe5c6c5db537a416f366ed70c4577a8a3a07658281d9485225d438
+  metadata.gz: 013afe67b6f86e17d37bfbd1b18f3b4b7e7e5026d3249900326b23d1ed75ed95
+  data.tar.gz: 7ccfcca5ef44d9958e3f03ea23ea211893357ff32c7c5e5fdc4953ec61548306
 SHA512:
-  metadata.gz: 5a57589ccaf3b2f516727cd6e7b066044d13a49d2c5280a478de162e42574e1eca03c2b013133d9b0ce50b4ac037fef15d12a01f5893b32ec6132d03c121e08f
-  data.tar.gz: bc338066a99d6470bd434d26cf994159ec926c4eb7f3a7d1d8b358303d5850bcdf058b56447ebf6c581bb2295de2d5f57f5637db5ab82fbd47ba618b8988afe6
+  metadata.gz: 5a50d291b69952d04bc054ea09cf292f6df414a4d6e1df69ac47cb3d2489626301c7eba4f66edd268f1c486463d6c37a1fd0b3cd431060c7100da980272c2b9e
+  data.tar.gz: 0bd422a52a4b11f69ade0d744df2a0bf8db6a05d67e282bfadb6a1a72af6f1ebe21ec0dd24b8ce663379d9e69db643036606e2fc1e502995e24f2f7b5c8bdea3

data/.gitignore

@@ -1,7 +1,6 @@
 /.bundle/
 /.yardoc
 /_yardoc/
-/doc/
 /rdoc/
 /pkg/
 /spec/reports/
@@ -27,3 +26,5 @@ tt.*
 s
 s.*
 
+# Ignore temporary directory
+/spec/tmpdir/

data/.ruby-version

@@ -1 +1 @@
-ruby-2.6.6
+ruby-2.7.1

data/README.md

@@ -1,345 +1,289 @@
 # Shellopts
 
-`ShellOpts` is a simple Linux command line parsing libray that covers most modern use
-cases incl. sub-commands. Options and commands are specified using a
-getopt(1)-like string that is interpreted by the library to process the command
-line
+`ShellOpts` is a command line processing library. It supports short
+and long options and subcommands, and has built-in help and error messages
+
 
 ## Usage
 
-The following program accepts the options -a or --all, --count, --file, and -v
-or --verbose. It expects `--count` to have an optional integer argument,
-`--file` to have a mandatory argument, and allows `-v` and `--verbose` to be
-repeated:
+ShellOpts use a string to specify legal options and documentation. The
+following program accepts the options --alpha and --beta with an argument. -a
+and -b are option aliases:
 
 ```ruby
- 
-# Define options
-USAGE = "a,all count=#? file= +v,verbose -- FILE..."
-
-# Define default values
-all = false
-count = nil
-file = nil
-verbosity_level = 0
-
-# Process command line and return remaining non-option arguments
-args = ShellOpts.process(USAGE, ARGV) do |opt, arg|
-  case opt
-    when '-a', '--all';    all = true
-    when '--count';        count = arg || 42
-    when '--file';         file = arg # never nil
-    when '-v, '--verbose'; verbosity_level += 1
-  else
-    fail "Internal Error: Unmatched option: '#{opt}'"
-  end
-end
-
-# Process remaining command line arguments
-args.each { |arg| ... }
-```
-
-Note that the `else` clause catches legal but unhandled options; it is not an
-user error. It typically happens because of a missing or misspelled option name
-in the `when` clauses
+require 'shellopts'
 
-If there is an error in the command line options, the program will exit with
-status 1 and print an error message and a short usage description on standard
-error
+SPEC = "-a,alpha -b,beta=VAL -- ARG1 ARG2"
 
-## Processing
+opts, args = ShellOpts.process(SPEC, ARGV)
 
-`ShellOpts.process` compiles a usage definition string into a grammar and use
-that to parse the command line. If given a block, the block is called with a
-name/value pair for each option or command and return a list of the remaining
-non-option arguments
+alpha = opts.alpha?   # True if -a or --alpha are present
+beta = opts.beta      # The value of the -b or --beta option
 
-```ruby
-args = ShellOpts.process(USAGE, ARGV) do |opt, arg|
-  case opt
-    when ...
-  end
-end
 ```
 
-This calls the block for each option in the same order as on the command line
-and return the remaining non-option args. It also sets up the `ShellOpts.error` and
-`ShellOpts.fail` methods. Please note that you need to call `ShellOpts.reset`
-if you want to process another command line
-
-If `ShellOpts.process` is called without a block it returns a
-`ShellOpts::ShellOpts` object. It can be used to process more than one command
-line at a time and to inspect the grammar and AST
-
 ```ruby
-shellopts = ShellOpts.process(USAGE, ARGV)  # Returns a ShellOpts::ShellOpts object
-shellopts.each { |opt, arg| ... }           # Access options
-args = shellopts.args                       # Access remaining arguments
-shellopts.error "Something went wrong"      # Emit an error message and exit
 ```
 
-## Usage string
+ShellOpts also allow multi-line definitions with comments that are used as part
+of help messages
 
-A usage string, typically named `USAGE`, is a list of option and command
-definitions separated by whitespace. It can span multiple lines. A double
-dash (`--`) marks the end of the definition, anything after that is not
-interpreted but copied verbatim in error messages
+```ruby
+require 'shellopts'
 
-The general [syntax](https://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_form) is
+SPEC = %(
+  -a,alpha @ Brief comment for -a and --alpha options
+  -b,beta=VAL
+      @ Alternative style of brief comment
+  -- ARG1 ARG2
+)
 
-```EBNF
-options { command options } [ "--" anything ]
+opts, args = ShellOpts.process(SPEC, ARGV)
+ShellOpts::ShellOpts.brief
 ```
 
-## Options
+prints
 
-An option is defined by a list of comma-separated names optionally prefixed by a
-`+` and/or followed by a `=` and a set of flags. The syntax is
+```
+Usage
+  main --alpha --beta=VAL ARG1 ARG2
 
-```EBNF
-[ "+" ] name-list [ "=" [ "#" | "$" ] [ label ] [ "?" ] ]
+Options
+  -a, --alpha     Brief comment for -a and --alpha options
+  -b, --beta=VAL  Alternative style of brief comment
 ```
 
-#### Flags
+There is also a `ShellOpts.help` method that prints a more detailed
+documentation, and a `ShellOpts.usage` method that prints a compact usage
+string
 
-There are the following flags:
+If there is an error in the command line options, the program will exit with
+status 1 and print an error message and usage on standard error.  If there is
+an error in the specification, a message to the developer with the origin of
+the error is printed on standard error
 
-|Flag|Effect|
-|---|---|
-|+|Repeated option (prefix)|
-|=|Argument. Mandatory unless `?` is also used|
-|#|Integer argument|
-|$|Floating point argument|
-|?|Optional argument|
+## Processing
 
-#### Repeated options
+`ShellOpts.process` creates a `ShellOpts::ShellOpts` object and use it to
+compile the specification and process the command line. It returns a tuple of a
+Program object and an array of the remaining arguments
 
-Options are unique by default and the user will get an error if an option is
-used more than once. You can tell the parser to allow several instances of the
-same option by prefixing the option names with a `+`. A typical use case is to
-let the user repeat a 'verbose' option to increase verbosity: `+v,verbose`
-allows `-vvv` or `--verbose --verbose --verbose`. `ShellOpts::process` yields
-an entry for each usage so should handle repeated options like this
+The Program object has accessor methods for each defined option and sub-command
+to check presence and return an optional argument. Given the options "--alpha
+--beta=ARG" then the following accessor methods are available:
 
 ```ruby
-verbosity_level = 0
+  # Returns true if the option is present and false otherwise
+  opts.alpha?()     
+  opts.beta?()
 
-args = ShellOpts.process(USAGE, ARGV) do |opt, arg|
-  case opt
-    when '-v', '--verbose'; verbosity_level += 1
-    # other options
-  end
-end
+  # Returns the argument of the beta option or nil if missing
+  opts.beta()       
 ```
 
-#### Option names
+Given the commands "cmd1! cmd2!" the following methods are available:
 
-Option names are a comma-separated list of names. Names can consist of one or more
-ASCII letters (a-zA-Z), digits, underscores ('\_') and dashes ('-').  A name
-can't start with a dash, though
+```ruby
+  # Returns the sub-command object or nil if not present
+  opts.cmd1!
+  opts.cmd2!
+  
+  opts.subcommand!  # Returns the sub-command object or nil if not present
+  opts.subcommand   # Returns the sub-command's identifier (eg. :cmd1!)
+```
 
-Names that are one character long are considered 'short options' and are
-prefixed with a single dash on the command line (eg. '-a'). Names with two or
-more characters are 'long options' and are used with two dashes (eg. '--all').
-Note that short and long names handles arguments differently
+It is used like this
 
-Examples:
-```
-a               # -a
-all             # --all
-a,all           # -a or --all
-r,R,recursive   # -r, -R, or --recursive
+```ruby
+  case opts.subcommand
+    when :cmd1 
+      # opts.cmd1 is defined here
+    when :cmd2
+      # opts.cmd2 is defined here
+    end
+  end
 ```
 
-#### Option argument
+Sub-commands have options and even sub-sub-commands of their own. They can be
+nested to any depth (which is not recommended, btw.)
 
-An option that takes an an argument is declared with a `=` after the name list.
-By default the type of an option is a `String` but a integer argument can be
-specified by the `#` flag and a float argument by the `$` flag.  
+The module methods `::usage`, `::brief`, and `::help` prints documentation with
+increasing detail. `::usage` lists the options and commands without any comments,
+`::brief` includes source text that starts with a '@', and `::help` the full
+documentation in a man-page like format. Example
 
-You can label a option value that will be used in help texts and error
-messages. A usage string like `file=FILE` will be displayed as `--file=FILE`
-and `file=FILE?` like `--file[=FILE]`. If no label is given, `INT` will be used
-for integer arguments, `FLOAT` for floating point, and else `ARG`
+```ruby
+  SPEC = "-h --help"
+  opts, args = ShellOpts.process(SPEC, ARGV)
+
+  if opts.h?
+    ShellOpts.brief
+    exit
+  elsif opts.help?
+    ShellOpts.help
+    exit
+  end
+```
 
-Arguments are mandatory by default but can be made optional by suffixing a `?`
+The module methods `::error` and `::failure` are used to report errors in a common
+format and then terminate the program with status 1. `::error` is used to report
+errors that the user can correct and prints a usage description as a reminder.
+`::failure` is used to report errors within the program so the usage descriptionn
+is not printed:
 
-## Commands
+```ruby
+  SPEC = "--var=VAR"
+  opts, args = ShellOpts.process(SPEC, ARGV)
 
-Sub-commands (like `git clone`) are defined by a name (or a dot-separated list
-of names) followed by an exclamation mark. All options following a command are
-local to that command. It is not possible to 'reset' this behaviour so global
-options should always come before the first command. Nested commands are
-specified using a dot-separated "path" to the nested sub-command
+  # --var is a mandatory 'option'
+  opts.var? or error "Missing --var 'option'"
 
-Examples
-```
-g,global clone! t,template=
-g,global clone! t,template= clone.list! v,verbose
+  # later during processing
+  condition or failure "Memory overflow"
 ```
 
-The last example could be called like `program -g clone list -v`. You may split
-the usage string to improve readability:
 
-```
-g,global 
-    clone! t,template= 
-        clone.list! v,verbose
-```
+## Specification
 
-#### Command processing
+The specification is possibly multi-line string, typically named `SPEC`, that
+is a mix of option or command definitions and related documentation.
+Indentation is used to nest the elements and '@' is used to tag an option or
+command with a brief description
 
-Commands are treated like options but with a value that is an array of options (and 
-sub-commands) to the command:
+The specifiction is parsed line-by-line: Lines matching and initial '-', or
+'--' are considered option definitions and lines starting with a word
+immediately followed by an exclamation mark is a command definition (like 'cmd!
+...'). Text following a '@' (except in paragraphs) is a brief comment, the rest
+is paragraphs
 
-```ruby
-USAGE = "a cmd! b c"
-
-args = ShellOpts.process(USAGE, ARGV) { |opt, arg|
-  case opt
-    when '-a'; # Handle -a
-    when 'cmd'
-      arg.each { |opt, arg|
-        case opt
-          when '-b'; # Handle -b
-          when '-c'; # Handle -c
-        end
-      }
-  end
-}
 ```
+  -a,alpha @ Brief comment for -a and --alpha options
+    Longer description of the option that is used by `::help`
 
-## Parsing
+  cmd! 
+    @ Alternative style of brief comment
 
-Parsing of the command line follows the UNIX traditions for short and long
-options. Short options are one letter long and prefixed by a `-`. Short options
-can be grouped so that `-abc` is the same as `-a -b -c`.  Long options are
-prefixed with a `--` and can't be grouped
+    Longer description of the command
+```
 
-Mandatory arguments to short options can be separated by a whitespace (`-f
-/path/to/file`) but optional arguments needs to come immediately after the
-option: `-f/path/to/file`. Long options also allow a space separator for
-mandatory arguments but use `=` to separate the option from optional arguments:
-`--file=/path/to/file`
+Text starting with '--' follow by a blank character is a free-text description
+of the command-line arguments. It is not parsed but used in documentation and
+error messages:
 
-Examples
+```ruby
+  SPEC = "-a cmd! -- ARG1 ARG2"
 ```
-f=              # -farg or -f arg
-f=?             # -farg
 
-file=           # --file=arg or --file arg
-file=?          # --file=arg
-```
+## Options
 
-#### Error handling
+The general syntax for options is
 
-If the command line is invalid, it's a user error and the program exits with
-status 1 and prints an error message on STDERR 
+```
+  <prefix><optionlist>[=argspec][?]
+```
 
-If there is an error in the usage string, ShellOpts raises a
-`ShellOpts::CompileError`. Note that this exception signals an error by the
-application developer and shouldn't be catched. If there is an internal error
-in the library, a ShellOpts::InternalError is raised and you should look for a
-newer version of `ShellOpts` or file a bug-report
+The option list is a comma-separated list of option names. It is prefixed with
+a '-' if the option list starts with a short option name and '--' if the option
+list starts with a long name. '-' and '--' can be replaced with '+' or '++' to
+indicate that the option can be repeated
 
-All ShellOpt exceptions derive from ShellOpt::Error
+```
+  -a,alpha      @ -a and --alpha
+  ++beta        @ --beta, can be repeated
+  --gamma=ARG?  @ --gamma, takes an optional argument
+```
 
-#### Error handling methods
 
-ShellOpts provides two methods that can be used by the application to
-generate error messages in the style of ShellOpts: `ShellOpts.error` and
-`ShellOpts.fail`. Both write an error message on STDERR and terminates the
-program with status 1. 
+An option argument has a name and a type. The type can be specified as '#'
+(integer), '$' (float), or as a comma-separated list of allowed values. It can
+also be defined by a keyword that expects a file or directory argument:
 
-`error` is intended to respond to user errors (like giving a file name that
-doesn't exist) and prints a short usage summary to remind the user:
+  | Keyword   | Type |
+  | --------- | ---- |
+  | FILE      | A file if present or in an existing directory if not |
+  | DIR       | A directory if present or in an existing directory if not |
+  | PATH      | Either a FILE or DIR |
+  | EFILE     | An existing file |
+  | EDIR      | An existing directory |
+  | EPATH     | Either an EFILE or EDIR |
+  | NFILE     | A new file |
+  | NDIR      | A new directory |
+  | NPATH     | A new file or  directory |
 
-```
-<PROGRAM>: <MESSAGE>
-Usage: <PROGRAM> <USAGE>
-```
-The usage string is a prettyfied version of the usage definition given to
-ShellOpts
+By default the option name is inferred from the type but it can be specified explicitly by separating it from the type with a ':'. Examples:
 
-`fail` is used to report that something is wrong with the assumptions about the
-system (eg. disk full) and omits the usage summary
 ```
-<PROGRAM>: <MESSAGE>
+  -a=#                  @ -a takes an integer argument
+  -b=MONEY:$            @ -b takes a float argument. Is shown as '-b=MONEY' in messages
+  -c=red,blue,green     @ -c takes one of the listed words
+  -d=FILE               @ Fails if file exists and is not a file
+  -d=EDIR               @ Fails if directory doesn't exist or is not a directory
+  -d=INPUT:EFILE        @ Takes and existing file. Shown as '-d=INPUT' in messages
 ```
 
-The methods are defined as instance methods on `ShellOpts::ShellOpts` and as
-class methods on `ShellOpts`. They can also be included in the global scope by
-`include ShellOpts::Utils`
+## Commands
 
-#### Usage string
+Commands are specified as lines starting with the name of the command
+immediately followed by a '!' like `cmd!`. Commands can have options and even
+subcommands of their own, in the multi-line format they're indented under the
+command line like this
 
-The error handling methods prints a prettified version of the usage string
-given to `ShellOpts.parse`. The usage string can be overridden by assigning to
-`ShellOpts.usage`. A typical use case is when you want to split the usage
-description over multiple lines:
+```
+  -a @ Program level option
+  cmd!
+    -b @ Command level option
+    subcmd!
+      -c @ Sub-command level option 
+```
 
-```ruby
+In single-line format, subcommands are specified by prefixing the supercommand's name:
 
-USAGE="long-and-complex-usage-string"
-ShellOpts.usage = <<~EOD
-  usage explanation
-  split over
-  multiple lines
-EOD
 ```
-
-Note that this only affects the module-level `ShellOpts.error` method and not
-object-level `ShellOpts::ShellOpts#error` method. This is considered a bug and
-will fixed at some point
+  -a cmd! -b cmd.subcmd! -c
+```
 
 ## Example
 
-The rm(1) command could be implemented like this
+The rm(1) command could be specified like this:
+
 ```ruby
 
 require 'shellopts'
 
 # Define options
-USAGE = %{
-  f,force i I interactive=WHEN? r,R,recusive d,dir 
-  one-file-system no-preserve-root preserve-root 
-  v,verbose help version
-}
-
-# Define defaults
-force = false
-prompt = false
-prompt_once = false
-interactive = false
-interactive_when = nil
-recursive = false
-remove_empty_dirs = false
-one_file_system = false
-preserve_root = true
-verbose = false
-
-# Process command line
-args = ShellOpts.process(USAGE, ARGV) { |opt, arg|
-  case opt
-    when '-f', '--force';           force = true
-    when '-i';                      prompt = true
-    when '-I';                      prompt_once = true
-    when '--interactive';           interactive = true; interactive_when = arg
-    when '-r', '-R', '--recursive'; recursive = true
-    when '-d', '--dir';             remove_empty_dirs = true
-    when '--one-file-system';       one_file_system = true
-    when '--preserve-root';         preserve_root = true
-    when '--no-preserve-root';      preserve_root = false
-    when '--verbose';               verbose = true
-    when '--help';                  print_help; exit
-    when '--version';               puts VERSION; exit
-  end
-end
+SPEC = %(
+  -f,force            @ ignore nonexisten files and arguments, never prompt
+  -i                  @ prompt before every removal
 
-# Remaining arguments are files or directories
-files = args
-```
+  -I                  
+      @ prompt once
+
+      prompt once before removing more than three files, or when  removing
+      recursively;  less  intrusive than -i, while still giving protection
+      against most mistakes
+
+  --interactive=WHEN:never,once,always
+      @ prompt according to WHEN
 
+      prompt according to WHEN: never, once (-I), or always (-i); without WHEN, prompt always
+
+  --one-file-system
+      @ stay on fuile system
+
+      when  removing  a hierarchy recursively, skip any directory that is on a file system different from
+      that of the corresponding command line argument
+
+  --no-preserve-root    @ do not treat '/' specially
+  --preserve-root       @ do not remove '/' (default)
+  -r,R,recursive        @ remove directories and their contents recursively
+  -d,dir                @ remove empty directories
+  -v,verbose            @ explain what is being done
+  --help                @ display this help and exit
+  --version             @ output version information and exit
+
+  -- FILE...
+)
+```
 
 ## See also
 
@@ -378,16 +322,6 @@ release a new version, update the version number in `version.rb`, and then run
 git commits and tags, and push the `.gem` file to
 [rubygems.org](https://rubygems.org).
 
-## Implementation
-
-FIXME
-# ShellOpts is a library for parsing command line options and commands. It
-# consists of the interface module {ShellOpts}, the implementation class
-# {ShellOpts::ShellOpts} and the representation classes
-# {ShellOpts::OptionsHash} and {ShellOpts::OptionsStruct}.
-# {ShellOpts::Messenger} is used for error messages
-
-
 ## Contributing
 
 Bug reports and pull requests are welcome on GitHub at

data/TODO

@@ -1,8 +1,16 @@
-o Somehow escape comments where a line starts with an option name
-o 'help' should list commands in declaration order
-o 'help' should use all levels by default
-o 'help' should always include top-level options (try setting levels: 10 and
-  see top-level options are gone
+
+o Ignore all text after ' # ' (doesn't conflict with option flag)
+o Command aliases
+o Add user-defined setions
+o Add a SOURCE section with link to git repo
+o Bullet-lists
+o Allow a USAGE section (and NAME)
+o Find source in code an adjust line number in error messages 
+o Rename line and char to lineno and charno
+o Client-defined argument types
+o Rename Expr -> ?
+o Find clean(er) procedural object model
+o Allow assignment to options (this makes practical stuff easier)
 o Special handling of --help arguments so that '--help command' is possible
 o Support for paging of help:
     begin 
@@ -14,3 +22,27 @@ o Support for paging of help:
       file.close 
     end 
 
++ Bold text output
++ Recursive format of commands
++ Rename Compiler -> Interpreter
+
+
+OLD
+
+o Fix that it is near unsable when the user doesn't do 'include ShellOpts'
+o Subcommands can be parsed as well: 
+    opts, args = Shellopts.process(OPTIONS, ARGV)
+    ...
+    opts, command = opts.process
+    case command
+      when ...
+    end
+o 'help' should list commands in declaration order
+o 'help' should use all levels by default
+o 'help' should always include top-level options (try setting levels: 10 and
+  see top-level options are gone
+o A ShellOpts#shift command that makes it possible for Array#expect to emit
+  relevant error messages
+
++ Somehow escape comments where a line starts with an option name
++ Parse and check enumeration arguments ('--debug=tokens|ast|idr|...')