Thanks for elaborating on your dotfiles strategy. I was using yadm until 
now (which has served me well, thank you Tim Byrne!) and reading your 
article helped me to simplify my dotfiles even further and retire yadm 
in favour of vanilla git and use the `hostname` trick to have variants 
for each different arch or computer.


It would be interesting to know however, if you or anyone else has a 
good recommendation on storing secrets such as pass datastore or some 
personal notes in a similar simple fashion.


P.S.: for some reason TB is pushing for HTML even though I've explicitly 
set it not to do so. Sigh! I have to take more baby steps to learn and 
use mutt, aerc, etc. more effectively (terminals still don't handle my 
mother tongue/script).

On Fri Apr 16, 2021 at 3:10 PM CEST, Mehdi Sadeghi wrote:
> It would be interesting to know however, if you or anyone else has a
> good recommendation on storing secrets such as pass datastore or some
> personal notes in a similar simple fashion.
pass organizes passwords in a git repository by default.

> pass organizes passwords in a git repository by default.

Yes, you're t right. However, however the way I use it, it exposes a lot of metadata about services and websites I visit or use.  I'd appreciate any hack or thought on this.

What about configs with your email password for mutt, git send-mail and occasional secrets and tokens?

>What about configs with your email password for mutt, git send-mail and 
>occasional secrets and tokens?

I have personally moved away from including any important secrets or 
tokens in plain text. For mutt, you can use pass, GPG, or another 
keyring to store secrets and access them without exposing anything in 
plain text. See [1].

Most programs should allow config options which include a call to an 
external program.

See `man git-send-email` and `man git-credential` for info on those.

[1]: https://wiki.archlinux.org/index.php/Mutt#Passwords_management