getoptions
getoptions copied to clipboard
An elegant option/argument parser for shell scripts (full support for bash and all POSIX shells)
Overall, it looks like a good tool, with many features, but learning how to use it is very time intensive. While there are some examples, there is hardly any explanation...
getoptions を日頃より利用させてもらっております。開発者の皆様ありがとうございます。 以下のような ShellScript コードを作成し、 `gengetoptions embed --overwrite` を利用して、オプション解析のコードを追加した後実行すると、オプション `-a` のバックスラッシュが自動的にエスケープされるようです。 ~~~ # @getoptions parser_definition() { setup REST param a -a init:='\\' } # @end # @gengetoptions parser -i parser_definition...
I'm often writing scripts that require some parameters to be provided when calling the script, while others are (and that seems to be the reasonable standard when using `getoptions`) completely...
My use case is something like this: I have an sh file that is used as a proxy for a binary. However I want to only parse "some" options while...
AURにgetoptionsのPKGBUILDを書いて投稿しました。 これによりArchユーザーはpacmanの管理下でgetoptionsを使用できます。 https://aur.archlinux.org/packages/getoptions-git/ https://aur.archlinux.org/packages/getoptions/ READMEにこれを追記することでArchユーザーは簡単にインストールできるようになります。
the optional grammar is below for current: -ovalue or -o=value can it support -o value?
Is there an example of using the embed options while there are multiple subcmds involved?
The basic getoptions is designed for use with shell scripts but is not fully compatible for use with functions. The generated parser initializes the parameters in the outer shell rather...