| 1 |
# Manage dconf settings |
| 2 |
|
| 3 |
Here is an example (thanks [@gmvelencoso](https://github.com/gmvelencoso)) |
| 4 |
using dotdrop to manage dconf settings: |
| 5 |
|
| 6 |
```yaml |
| 7 |
actions: |
| 8 |
dconf_load: dconf load "{0}" < "{{@@ _dotfile_abs_src @@}}" |
| 9 |
trans_update: |
| 10 |
dconf_dump: dconf dump "{2}" > "{1}" |
| 11 |
dconf_tilix: |
| 12 |
src: config/tilix/tilix.dconf |
| 13 |
dst: /tmp/tilix.dconf |
| 14 |
actions: |
| 15 |
- dconf_load /com/gexperts/Tilix/ |
| 16 |
trans_update: dconf_dump /com/gexperts/Tilix/ |
| 17 |
link: nolink |
| 18 |
``` |
| 19 |
|
| 20 |
On `install`/`compare`, the [action](../config/config-actions.md) `dconf_load` will call `dconf` to load |
| 21 |
the configuration from the file stored in the *dotpath* under `config/tilix/tilix.dconf`. |
| 22 |
|
| 23 |
On `update`, the [transformation](../config/config-transformations.md) `trans_update` will dump the configuration |
| 24 |
entry and use it to update the file in the *dotpath*. |