The Carbon CLI is really awesome and I love that it's possible to store and reuse a configuration as preset. One thing I'd love to add to the config though is the actual "theme colors" (i.e. what color e.g. variables, operators, keywords, comments, ...).

Basically these options from the Carbon web UI:

![Screenshot 2019-03-26 at 10 39 45](https://user-images.githubusercontent.com/4058327/5498

The Pipfile lists many version pinned requirements.
IMHO requirements should ideally never be version pinned (only if really really required).
Please remove the version pinning, where not needed!
It's hard to do proper packaging with this (especially for distributions, that follow upstream closely, such as Arch Linux).

$ git repo --help
No manual entry for git-repo
$ git-repo --help
....

• https://pyrocore.readthedocs.io/en/latest/howto.html#host-migration-of-data-state
• pyroscope/rtorrent-ps#102

Yasha is heavily based on Pallets Projects (Jinja2 and Click). I have also seen that there is (some) need for the Yasha kind of tool among the users of Jinja2. Thus, it would be nice to have the project listed in Pallets. Before making a proposal, make sure that at least the following requirements are met.

• Configuration, https://github.com/pallets/meta/i

As specified here. I think it'd make sense to accept a range of dates but I'm not sure yet about what's the best format. Right now we parse dates in the format YYYY-MM-DD which is a good starting point but it doesn't contain time information.

To reproduce issue install node v6.0.0, nvm, and faker-cli, then issue the following command:

faker-cli uuid help

Maybe an update to the README for node version compatibility would be helpful :)

Available options for undefined:
/Users/user.name/.nvm/versions/node/v6.0.0/lib/node_modules/faker-cli/index.js:207
  return Object.keys(faker[which]);
                ^

TypeError: Cannot conver

Thanks for porting and maintaining autojump! I had the same idea and now I'm glad that I don't have to do it myself.

It seems that not all the installation instructions are present in this repo, namely function definitions, completion setup and shell integration. Are you planning to provide those?

You should be able to do something like add an alias:

stars : list stars

Or

stl : list stars -l

These aliases would be stored in your configuration file, and could be set up/edited via a configure command.

This ticket will sit for a while.. I need to decide what to do about the existing man page, it hasn't been fully reviewed or updated in a while. I don't know how necessary a complete man page is for a project like rmw.

I just experimented with po4a.. pretty straightforward it seems, but all I tried so far was to create the .pot (template) file.

Best case would be that so

Cool tool! It might be educational to include in the README mention of McIlroy's 2004 Functional Pearl "Enumerating the strings of regular languages" http://www.cs.dartmouth.edu/~doug/nfa.ps.gz