Lairucrem_: A simple and useful text-base interactive interface for mercurial_
It is a text-base interactive interface that helps developpers on their dayly usage of mercurial. Because it is a text-base interface, it can be used over ssh tunnel which is helpful when working on a remote machine.
lairucrem displays the changeset tree and the patch content of the focused changeset. You can interactively inspect the repository history by changing the focused changeset. We put some effort to make it quite responsive, even on huge repositories whith big patches.
lairucrem can propose a set of actions that can be applied to the focused chageset, like rebase, update, addremove, etc. A small set of actions are available in the actual version but later releases will propose more actions and a plugin system which will allow you to add your own actions. You do not have to mess with complex UI, just the actions you need.
lairucrem uses the command line interface of Mercurial. So it just performs the commands you commonly run. It activates extensions (the “official” ones) when there are needed.
We still work on lairucrem, fill issues if you think something could be improved.
pip install lairucrem
pip install --user lairucrem
You may want to use virtualenv to create an isolated Python environment.
virtualenv /path/to/envs/lairucremenv source /path/to/envs/lairucremenv/bin/activate
Clone the repository:
hg clone http://bitbucket.org/aleufroy/lairucrem cd lairucrem
Install dev dependencies and lairucrem (in development mode):
pip install -r dev-requirements.txt -e .
py.test --doctest-modules --pylint -q
--pylint option enables coding standards checks. Take a
look at the
pylintrc file for detailed coding rules used in
py.test --doctest-modules --cov=lairucrem --cov-report term-missing
pip install docutils python setup.py --long-description | rst2html --strict -
dev_requirements.txt which allows
py.test to watch for file system changes with the
Please check the followings before sending your pull request:
Add yourself to the
Check the new feature/fix by add new tests or by adapting existing tests (test coverage is useful here). If your change does not need test change, tell it in the commit message.
Check that tests are all green, including the
--pylint options. Note that you can disable falsy warnings
from pylint (with caution) by adding a comment like:
Help me understand your patch with few lines of description in the commit message (do not translate your code in english :P). This makes the patch integration easier and quicker than it could be without it. You can also refer to an existing issue from the tracker – I’m not a github/bitbucket addict, so let the commit message self consistant.
In the meantime, you can send me a message on twitter (alainleufroy) or on the #mercurial IRC channel (aleufroy).
|LICENSE:||[http://sam.zoy.org/wtfpl/](WTFPL) see LICENSE.txt|