From 61d8183a71330e240e81f3e377a9cc463a73b234 Mon Sep 17 00:00:00 2001 From: Luke Faraone Date: Tue, 5 Feb 2013 16:00:00 -0500 Subject: [PATCH] Be more explicit as to where .humbugrc goes (imported from commit 3e229d61ebfef64e29ca45cc57eca04ec207ae86) --- api/README | 5 +++-- api/examples/humbugrc | 2 +- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/api/README b/api/README index 0c9349255a..5b41bf18ad 100644 --- a/api/README +++ b/api/README @@ -22,8 +22,9 @@ as we make any changes to them. The easiest way to use these API bindings is to base your tools off of the example tools under examples/ in this distribution. -If you place your API key in `~/.humbugrc` the Python API bindings will -automatically read it in. The format of the config file is as follows: +If you place your API key in the config file `~/.humbugrc` the Python +API bindings will automatically read it in. The format of the config +file is as follows: [api] key= diff --git a/api/examples/humbugrc b/api/examples/humbugrc index 5e2bd334c0..0636fe1b1e 100644 --- a/api/examples/humbugrc +++ b/api/examples/humbugrc @@ -1,4 +1,4 @@ -; put this file in ~/.humbugrc +; Save this file as ~/.humbugrc [api] key= email=