aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRiccardo Spagni <ric@spagni.net>2015-12-22 10:08:10 +0200
committerRiccardo Spagni <ric@spagni.net>2015-12-22 10:10:13 +0200
commitcab57ca49d6c6fd76b8d15550d5453770287200c (patch)
treeb079ee656fdcc148559e109714e01ba2399a6ca7
parentMerge pull request #545 (diff)
parentREADME.md: mention rlwrap usage (diff)
downloadmonero-cab57ca49d6c6fd76b8d15550d5453770287200c.tar.xz
Merge pull request #546
bd15f97 README.md: mention rlwrap usage (moneromooo-monero)
-rw-r--r--README.md5
1 files changed, 5 insertions, 0 deletions
diff --git a/README.md b/README.md
index c34e0d36c..71b9a635e 100644
--- a/README.md
+++ b/README.md
@@ -177,3 +177,8 @@ See README.i18n
While Monero isn't made to integrate with Tor, it can be used wrapped with torsocks, if you add --p2p-bind-ip 127.0.0.1 to the bitmonerod command line.
Be aware that your DNS use will probably go over clearnet. These come in two flavours: request for checkpoint data, and request for OpenAlias data. The first one is mostly harmless (your ISP can tell you're using monero). The second one leaks information about your transaction recipients, so do not use OpenAlias if you want DNS privacy.
+## Using readline
+
+While bitmonerod and simplewallet do not use readline directly, most of the functionality can be obtained by running them via rlwrap. This allows command recall, edit capabilities, etc. It does not give autocompletion without an extra completion file, however. To use rlwrap, simply prepend "rlwrap " to the command line, eg:
+rlwrap bin/simplewallet --wallet-file /path/to/wallet
+