From 2b761e450fc0b49d02901716bdc0f47e4f4c1bf9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20Mr=C3=A1zek?= Date: Thu, 23 Feb 2012 08:57:11 +0100 Subject: [PATCH] Add the init file to builds, mention it in readme. --- README.rst | 5 + Readme.html | 353 +++++++++++++++++++++-------------------- library/CMakeLists.txt | 3 + 3 files changed, 187 insertions(+), 174 deletions(-) diff --git a/README.rst b/README.rst index 2b462a88c..74d78bd7b 100644 --- a/README.rst +++ b/README.rst @@ -75,6 +75,11 @@ Something doesn't work, help! First, don't panic :) Second, dfhack keeps a few log files in DF's folder - stderr.log and stdout.log. You can look at those and possibly find out what's happening. If you found a bug, you can either report it in the bay12 DFHack thread, the issues tracker on github, contact me (peterix@gmail.com) or visit the #dfhack IRC channel on freenode. +============= +The init file +============= +If your DF folder contains a file named dfhack.init, its contents will be run every time you start DF. This allows setting up keybindings. An example file is provided as dfhack.init-example - you can tweak it and rename to dfhack.init if you want to use this functionality. + ======== Commands ======== diff --git a/Readme.html b/Readme.html index b4d9db96f..d9620a5ac 100644 --- a/Readme.html +++ b/Readme.html @@ -332,125 +332,126 @@ access DF memory and allow for easier development of new tools.

  • Installation/Removal
  • Using DFHack
  • Something doesn't work, help!
    • -
  • Commands