From: Steven Baltakatei Sandoval Date: Sun, 28 Jun 2020 15:17:22 +0000 (+0000) Subject: feat(unitproc):Add script to load dconf settings from file X-Git-Tag: 0.1.0~13 X-Git-Url: https://zdv2.bktei.com/gitweb/BK-2020-03.git/commitdiff_plain/bbe7e1653cf1aa5da882eeb6411b56093886a4b4?hp=a36416739b399ae388da41ecd86a95e848a7397b feat(unitproc):Add script to load dconf settings from file Script is `bkdconfwf` (baltakatei dconf write file). Currently, the command: bkdconfwf gnome-terminal.conf is currently functionally the same as: dconf load / < gnome-terminal.conf where `gnome-terminal.conf` is a snippet taken from: dconf dump / > dconf_backup formatted like: [org/gnome/terminal/legacy/keybindings] prev-tab='b' find='disabled' move-tab-right='f' find-previous='disabled' next-tab='f' find-next='disabled' move-tab-left='b' However, because processes each & string individually, future custom behavior may be programmed into the script. For example, it may be desireable in the future to combine the following keys: key="'['one']'" key="'['two']'" into: key="'['one' 'two']'" . --- diff --git a/unitproc/bkdconfwf b/unitproc/bkdconfwf new file mode 100644 index 0000000..dc6d8f4 --- /dev/null +++ b/unitproc/bkdconfwf @@ -0,0 +1,60 @@ +#!/bin/bash + +# Desc: Writes keys from dconf dump +# Purpose: Applying custom dconf dump without clobbering other keys +# Usage: bkdconfwf [file] +# Note: Useful if 'dconf load [file]' wipes existing settings. + +# Yell, Die, Try Three-Fingered Claw technique +# Ref/Attrib: https://stackoverflow.com/a/25515370 +yell() { echo "$0: $*" >&2; } +die() { yell "$*"; exit 111; } +try() { "$@" || die "cannot $*"; } + +#declare -A LG_AA # Associative Array for dconf and + +# Process input file - save & pairs to LG_AA +FILEIN="$1" +cat "$FILEIN" | while read line; do + yell "Begin processing of:$line"; + if [[ "$line" == "" ]]; then # Check for non-blank line + yell "Blank line detected."; + elif [[ "$line" =~ ^"["(.*)"]"$ ]]; then # Check for bracket-enclosed string (new line group) + yell "New line group detected at line:$line"; + # Note start of new line group + lgNum=0 + # Extract path + lgDir="$line"; + lgDir="${lgDir#[*}"; # See [2] + lgDir="${lgDir%*]}"; # See [2] + yell "Path is:$lgDir"; + elif [[ "$line" =~ (.*)"="(.*) ]]; then # Check for key=value pair + yell "DEBUG:Key value pair detected:$line"; + # Extract key + key="${line%%=*}"; # See [1,3] + yell "Key extracted:$key"; + # Extract value + value="${line#*=}"; # See [1,3] + yell "Value extracted:$value"; + # Add = to associative array LG_AA + #yell "DEBUG:LG_AA old:$LG_AA"; + #yell "DEBUG:lgDir:$lgDir"; + #yell "DEBUG:value:$value"; + #LG_AA["$lgDir/$key"]+="'$value' "; + #yell "DEBUG:LG_AA new:${LG_AA[@]}"; + # Apply keyvalue pair + try dconf write "/$lgDir/$key" "$value"; + else + yell "ERROR:Unrecognized string detected." + fi; + # Increment line group counter + ((lgNum++)) + yell "DEBUG:line group number:$lgNum" + yell "Finished processing of:$line"; + yell "============================="; +done + +# Ref/Attrib +# [1] How to extract substrings around specific character using parameter expansion. chepner. https://stackoverflow.com/a/15149278 https://stackoverflow.com/questions/15148796/get-string-after-character#comment43744397_15149278 +# [2] How to extract string from brackets. Alex Howansky. https://stackoverflow.com/a/7209856 +# [3] Advanced Bash-Scripting Guide, section 10.1 Manipulating Strings http://tldp.org/LDP/abs/html/string-manipulation.html