I've started a mailing list for users of ruby-based libraries and
frameworks that join ruby scripts with shells like bash/zsh or irb or
the rails console. A place to ask questions and trade tips.
So far I've been a big fan of the hackery of cldwalker and his boson,
hirb, bond, lightning and ripl libraries. I use them all the time and
have a great time building my own stuff up with them.
However I'm curious and eager to learn more of what others are using in
their command line and console lives. All users of other libraries like
thor, irbtools, etc. are more than welcome.
The mailing list is on librelist. Right now I'm having a little bit of a
problem with the archive interface but I expect to get it ironed out
soon. This problem shouldn't interfere with normal mailing list
operation.
+1 for ruby commandline apps. I'd like to exchange tips for building
commandline apps. Would be interested to know eople use for command gems
i.e. thor vs rake vs boson, for option parsing etc..
+1 for ruby commandline apps. I'd like to exchange tips for building
commandline apps. Would be interested to know eople use for command gems
i.e. thor vs rake vs boson, for option parsing etc..
For command line parsing, the stock optparse. The others take over the
app (such as thor, main, gli) etc.
For parsing of subcommands, i wrote a small gem called subcommand which
does not take over. And it does lazy loading as per suggestions on this
forum.
@rahul would subcommand be something like git cli, it yes it would be
a good idea to add that in the README as it would make it easy to
identify. Also what does lazy loading of commands mean and how does it
play with ARGF?
cheers,
deepak
···
On Dec 7, 9:18 pm, Rahul Kumar <sentinel1...@gmail.com> wrote:
Gabriel Horner wrote in post #966770:
> +1 for ruby commandline apps. I'd like to exchange tips for building
> commandline apps. Would be interested to know eople use for command gems
> i.e. thor vs rake vs boson, for option parsing etc..
For command line parsing, the stock optparse. The others take over the
app (such as thor, main, gli) etc.
For parsing of subcommands, i wrote a small gem called subcommand which
does not take over. And it does lazy loading as per suggestions on this
forum.
+1 for ruby commandline apps. I'd like to exchange tips for building
commandline apps. Would be interested to know eople use for command gems
i.e. thor vs rake vs boson, for option parsing etc..
For command line parsing, the stock optparse. The others take over the
app (such as thor, main, gli) etc.
For parsing of subcommands, i wrote a small gem called subcommand which
does not take over. And it does lazy loading as per suggestions on this
forum.
hi, @rahul would subcommand be something like git cli, it yes it would be
a good idea to add that in the README as it would make it easy to
identify. Also what does lazy loading of commands mean and how does it
play with ARGF?
cheers,
deepak
I am quoting from the home page.
A tiny wrapper over ruby’s awesome OptionParser (standard) which gives
easy facility of subcommands. It has a similar interface to git and
prints subcommands summary as well.
Options parsers are lazy-loaded thanks to a suggestion and sample code
by Robert Klemme on ruby-forum.org. If your program already uses
OptionParser, then one merely needs to add a line above each option
declaration — no rewriting required since all OptionParser syntax is
valid syntax for `subcommand`.
This wrapper adds the `description` attr to what OptionParser already
provides.
···
--------------------
I have not looked at the code for some months, will have to do so to
answer your question properly.
@rahul would subcommand be something like git cli, it yes it would be
a good idea to add that in the README as it would make it easy to
identify. Also what does lazy loading of commands mean and how does it
play with ARGF?
cheers,
deepak
Yes, I'm sorry about that. It can't be helped unfortunately. If you want
to read those e-mails you can use the rsync interface, e.g.:
Of course you can also subscribe to list and you will receive any future
mails. Just send an e-mail to ruby.cmd.line@librelist.com and you'll get
a confirmation e-mail. Thanks for looking.