Sorry for th slow answer, I’ve been away. There is a way, if it’s still useful to you:

First, create a named fifo, you only need to do this once:

mkfifo logview

Run your rsync in one pane, with a filtered view in the second:

tmux new 'rsync ...options... |& tee logview' \; split-window -h 'grep "denied" logview'

Replace ...options... with your normal rsync command line.

That should give you a split view, with all the normal messages on the left, and only messages containing ‘denied’ on the right.

The |& makes sure we capture both stdout and stderr, tee then writes them to the fifo and displays them. split-window tells tmux to create a second pane, and display the output of grep.

Tmux is a very helpful terminal multiplexer, meaning it can split your terminal into multiple panes. So, create two side by side panes, then one way of doing it is:

• on the left, run your cmd | tee >(grep 'denied' > error.log)
• on the right, run tail -f error.log

The tee process takes it’s standard in, and writes itbto both standard out, so you see all the lines, and the path it’s been given. The >(...) operator runs the grep in a subprocess, and returns the path to it’s standard input pipe, so grep receives every line, and writes the denied lines to a log file which you display with tail in the other pane.

Rather than using a file for error.log you could also use a named pipe in much the same way.

I’m not sure if you’ll see this, as federation seems to be playing up on lemm.ee, but first I wanted to congratulate you on your attitude to life, it’s an inspiration.

As to your question; I think Obsidian is an excellent tool for you to do this in. As it uses a fairly standard type of markdown for formatting you have plenty of options.

I’d suggest a two pronged approach to make sure your writing is accessible. In the first place, for the more personal stuff, just print it out. Put the printout in an envelope, write instructions on it that it is only to be opened after you pass away and then mail, or give it someone you trust (a friend, family member, solicitor etc). You can update it by jyst giving then a new copy, or just extra pages to add. I’d suggest making a couple of copies to be sure they get to the people who you want to read them.

For the general stuff, as Obsidian uses markdown and so does the wiki function on github, you should be able to just commit the vault to your wiki repository and have it rendered reasonably. That way it’ll reflect your changes with little effort. If you’re worried you might do something to it, ask a friend, or acquaintance to fork the repository and regularly sync it. That way you can’t remove all the copies.

Let me know if you need more detail.