update obds note

content/notes/openbsd/index.md

@@ -1,12 +1,15 @@
 ---
 title: OpenBSD notes
 date: 2023-11-29T20:33:48+0100
-lastmod: 2023-12-30T22:03:53+0000
+lastmod: 2024-01-18T15:24:17+0000
 tags:
   - openbsd
   - python
   - cloudlog
   - zsh-shell
+  - git
+  - rust
+  - neovim
 
 #showDate: false
 showReadingTime: false
@@ -26,11 +29,11 @@ operating systems in some way...
 
 ## Get some filesystem information
 
-```console
+~~~console
 $ dumpfs /dev/rsd1a
 magic	19540119 (FFS2)	time	Thu Nov 16 21:14:34 2023
 [...] (snip; lots of output...)
-```
+~~~
 
 This can be helpful if you want to know, which filesystem you actually
 use on your OpenBSD box.
@@ -187,9 +190,9 @@ Use of the online logging tool Cloudlog on my OpenBSD machine.
 First off, connect the TX-500 with the computer (CAT cable) and
 start `rigctld`:
 
-```console
+~~~console
 $ rigctld -m 2014 -r /dev/cuaU0 -s 9600 -v
-```
+~~~
 
 I use `2014` which is actually a Kenwood TS-2000 -- but on OpenBSD hamlib is currently
 at version 4.4 and the TX-500 is only available on
@@ -197,16 +200,16 @@ at version 4.4 and the TX-500 is only available on
 
 For newer hamlib versions (≥4.5) use the rig 2050 like:
 
-```console
+~~~console
 $ rigctld -m 2050 -r /dev/cuaU0 -s 9600 -v
-```
+~~~
 
 In combination with Digirig I would probably use something like this,
 because otherwise Digirig would instantly key the transceiver:
 
-```console
+~~~console
 $ rigctld -m 2014 -r /dev/cuaU0 -s 9600 --set-conf=rts_state=OFF -v
-```
+~~~
 
 Well, I tested this on my desk at home but never used my Laptop for
 doing digital modes with my TX-500 though -- but I want this to be noted
@@ -214,9 +217,9 @@ here just in case I should need it someday.
 
 On another terminal start [`cloudlogbashcat.sh`](https://github.com/g0wfv/CloudlogBashCat):
 
-```console
+~~~console
 $ cloudlogbashcat.sh
-```
+~~~
 
 Now, if you open the website of your Cloudlog installation (and if you have
 setup your rigs) and select the radio that uses cloudlogbashcat.
@@ -278,6 +281,29 @@ $ zmv -n -W '59-*' '*'
 mv -- 59-pat-winlink-on-openbsd pat-winlink-on-openbsd
 ~~~
 
+## Neovim
+
+### Update plugins that use `make`
+
+GNU make and BSD make are not compatible, and it is kind of annoying if people
+think everybody has installed the same tools to compile software on their boxes.
+
+In this example I often get some errors when I try to update plugins from withing
+AstroNvim, a plugin-packaged neovim confgiuration framework.
+
+- Open Neovim and initiate the update procedure (<kbd>space</kbd>, <kbd>p</kbd>, <kbd>a</kbd>)
+- Remember what folder the errors occur
+- Visit those folders and update the file `Makefile` (usually)
+- in `Makefile` replace `make` with `gmake`  
+  (you need that installed, `pkg_add gmake`)
+- run the update procedure again
+
+If that does not work, it is mostly a submodule. You can try to update and compile by hand.
+Switch to the folder, update `make` with `gmake` and finally run `gmake` in that folder.
+That will produce a compiled output (a library) and the updated procedure will pick that up
+at the next run and the submodule will usually be ignored unless the main repo has new commits
+in its tree. You may then stash the local changes and re-run the update procedure again. 
+
 ## Concatenate sound files (.wav)
 
 ~~~console