2022-07-18 11:58:35 -06:00
|
|
|
enable
|
2022-07-20 00:01:25 -06:00
|
|
|
======
|
sync tags spreadsheet to git
spreadsheet - https://docs.google.com/spreadsheets/d/1hiDlo8M_bB_1jE-5HRs2RrrA_VZ4cRu9VXaTctX_nwk/edit#gid=170388995
sync command - for fname in *rst; do name=$(echo $fname | sed 's/[.]rst//'); tagline=$(egrep ",$name," ~/Downloads/DFHack\ taxonomy\ -\ Tool\ tags.csv | ~/Downloads/csvtotags.sh); sed -ri "s;[*]*Tags:.*;$tagline;" $fname; done
contents of csvtotags.sh -
fgrep . | sed -r 's/^[^,]+,([^,]+),[^.]+[.]"?,/\1,/' | awk -F, '
function tag(idx, tagname) {
if ($idx == "TRUE") {
if (hastag == 1) {printf(", ")}
printf("`tag/%s`", tagname)
hastag = 1
}
}
{
printf("%s", "**Tags:** ")
hastag = 0
tag(2, "adventure")
tag(3, "fort")
tag(4, "legends")
tag(5, "embark")
tag(6, "system")
tag(7, "dev")
tag(8, "auto")
tag(9, "productivity")
tag(10, "inspection")
tag(11, "design")
tag(12, "quickfort")
tag(13, "interface")
tag(14, "fps")
tag(15, "fix")
tag(16, "mod")
tag(17, "armok")
tag(18, "animals")
tag(19, "buildings")
tag(20, "items")
tag(21, "jobs")
tag(22, "map")
tag(23, "labors")
tag(24, "units")
tag(25, "stockpiles")
tag(26, "trees")
printf("\n")
}
'
2022-08-05 18:55:33 -06:00
|
|
|
**Tags:** `tag/system`
|
2022-07-20 00:01:25 -06:00
|
|
|
:dfhack-keybind:`enable`
|
2022-07-18 11:58:35 -06:00
|
|
|
|
2022-07-22 00:21:56 -06:00
|
|
|
:index:`Activate a DFHack tool that has some persistent effect.
|
|
|
|
|
<enable; Activate a DFHack tool that has some persistent effect.>` Many plugins
|
|
|
|
|
and scripts can be in a distinct enabled or disabled state. Some of them
|
|
|
|
|
activate and deactivate automatically depending on the contents of the world
|
|
|
|
|
raws. Others store their state in world data. However a number of them have to
|
|
|
|
|
be enabled globally, and the init file is the right place to do it.
|
2022-07-18 11:58:35 -06:00
|
|
|
|
2022-07-20 00:01:25 -06:00
|
|
|
Most such plugins or scripts support the built-in ``enable`` and `disable`
|
2022-07-18 11:58:35 -06:00
|
|
|
commands. Calling them at any time without arguments prints a list of enabled
|
|
|
|
|
and disabled plugins, and shows whether that can be changed through the same
|
|
|
|
|
commands. Passing plugin names to these commands will enable or disable the
|
2022-07-20 00:01:25 -06:00
|
|
|
specified plugins.
|
|
|
|
|
|
|
|
|
|
Usage::
|
2022-07-18 11:58:35 -06:00
|
|
|
|
2022-07-20 00:01:25 -06:00
|
|
|
enable
|
|
|
|
|
enable <plugin> [<plugin> ...]
|
2022-07-18 11:58:35 -06:00
|
|
|
|
2022-07-20 00:01:25 -06:00
|
|
|
Examples
|
|
|
|
|
--------
|
2022-07-18 11:58:35 -06:00
|
|
|
|
2022-07-23 17:03:40 -06:00
|
|
|
``enable manipulator``
|
2022-07-20 00:01:25 -06:00
|
|
|
Enable the ``manipulator`` plugin.
|
2022-07-23 17:03:40 -06:00
|
|
|
``enable manipulator search``
|
2022-07-20 00:01:25 -06:00
|
|
|
Enable multiple plugins at once.
|