Yeah, I'd write this as a single update script with options to update vimplugins or update pkg or update all.
I see that you want it to be a function so you can get the chdir as a side effect, but mixing that with updating doesn't make sense to me.
More people should be like you.
I look forward to the day that Synapse is deprecated in favor of Dendrite or Conduit.
keyctl then
Nice work! I would have done some things differently, but this is very readable.
Two recommendations for reading the file:
(z) and (Q) flags so that instead of using tabs to separate the targets, simply quoting each argument works.map[$link]=$target. Then you can check for duplicate links while reading the list.linksfile=$1
typeset -gA linkmap
while read -r line
do
# -- fields
fields=(${(Q)${(z)line}})
# -- link
link=${(e)~fields[1]}
# -- target
target=${(e)~fields[2]}
# -- check if we've already seen this link
if (( $+linkmap[$link] )); then
echo "'$link' targets both '$linkmap[$link]' and '$target', aborting"
exit 1
fi
if [ -z "$target" ] || [ -z "$link" ]; then
echo "Empty link or target provided, skipping"
continue
fi
linkmap[$link]=$target
done < $linksfile
Then later, you can iterate over each key-value pair:
for link target in "${(@kv)linkmap}"; do
...
doneCorrections
First, a look at man termcap:
ch Move cursor horizontally only to column %1
ct Clear tabs
(j::) actually joins with no seperator. The character following the j is used to capture the separator. Nearly any character or paired bracket can be used, but colons are common. Other ways to write this which might have been more obvious: (j''), (j[]), (j<>). To actually join with colons, something like (j.:.) would have been used.
Full context
Zsh agressively sets tabstops to every 8 characters. This is in a function which I trap to the WINCH signal, to set the termstops to 4 using the $termcap sequences rather than the external command tput:
.on_winch(){
# tabs
local -a s
repeat COLUMNS/$1 s+=(${termcap[RI]/\%p1\%d/$1}$termcap[st])
# final
print -rn $termcap[sc]${termcap[ch]//(\%i|\%p1|\%d)}$termcap[ct]${(j::)s}$termcap[rc]
}
.on_winch 4
trap '.on_winch 4' WINCH
Corrections
ascending order
O is descending order. o is ascending order. In particular (Oa) keeps the array order, but flips it.
The
@symbol is used to indicate the array vriableargv.
Not here. As a PE flag, @ puts array elements in separate words, even if the parameter is enclosed in quotes.
The #MATCH gives the codepoint of the (first) character in $MATCH. The (#) flag turns codepoints into characters.
Full context
This is in a joke function called ], which is like [ but you have to specify the elements in reverse order and end it with a [. This uses bit-fiddling to swap [ and ] in the last parameter because I'm a masochist.
I do the same, but I include shebangs anyway out of habit.
I'm on EndeavourOS, but my laptop will be moving to Fedora Sericea (Silverblue, but Sway) to try that out.
pv, which is like cat, simply copying files or stdin to stdout, but prints statistics to the terminal.
A related tip: dd isn't special in the way most people use it. This works too, if you're root: pv my-fav-distro.iso > /dev/sdc
Relevant except below, bolded is the key point.