Australia
https://adigitoleo.srht.site/about/
a digito cognoscitur leo
Ask me about my projects via my public inbox, unless they have a dedicated mailing list.
NeoVim plugins: haunt.nvim | quark.nvim | overview.nvim
From adigitoleo to ~adigitoleo/public-inbox
This has been resolved. Also, my neovim plugins grew a todo tracker: https://todo.sr.ht/~adigitoleo/nvim-plugins
From adigitoleo to ~rjarry/aerc-discuss
I don't use the internal keyring nor bother with encrypted mail, but I did have to cast spells at gpg to get it to work for my outgoing-cred-cmd in accounts.conf. Because nobody else has responded, I'll just pass on what little I know: yes, aerc will block stdin, so I think you will need to set up a GUI pinentry method. For example, there is `pinentry-qt` for some linux distributions. I had to further set up a pipeline from pinentry-qt to my password manager, and tell it to use the gpg flag `--passphrase-fd=0` to read from the pipe. I'm not an expert on the security implications of moving secrets around in pipes though... I remember having a hard time finding out how to even use `pinentry-qt`, so this example might also be useful. It should prompt for the gpg passphrase and then print it to stdout (among other messages):
From adigitoleo (Leon) to ~rjarry/aerc-discuss
Hi, Lately I'm using my laptop more where I develop inside WSL. However, I still run the browser in Windows directly. I don't think it is possible to get Windows to somehow open mailto: links in a running aerc instance inside WSL and some layers of terminal multiplexers etc. Instead, I wanted to just copy the mailto link and use a TUI command to start a compose window in aerc pre-filled with the appropriate parameters. But it seems that the only way to do this would be to parse the mailto link into a template file first. I wonder if it would make sense to provide a way for :compose to do that work for me, since I guess it already understands mailto syntax. I did try to do `aerc -a <account> '<long_mailto_link>'` as well but got
From adigitoleo (Leon) to ~rjarry/aerc-discuss
Oh I see! This was shadowed by my zellij shortcut. But even then, I can to ^G first to allow passthrough. Indeed, it is right there on the welcome page... Sorry for the noise.
From adigitoleo (Leon) to ~rjarry/aerc-discuss
I recently swapped the last of my machines over to Void linux and went through the process of reconfiguring the system. During this process, I mistakenly ran `aerc` at some point before `scp`ing my `accouts.conf` file from the other machine. I was prompted to setup my account, but since I didn't want to do that, I tried ^C or ^D but wasn't able to abort the setup page. There were no relevant TUI buttons to do so either. It's quite a minor point, but I wonder if it would make sense to allow users to abort at the setup page. Cheers, Leon
From adigitoleo (Leon) to ~adigitoleo/public-inbox
If socklog logs are not being stored, e.g. in Void Linux on WSL2 where runit is not working, then we should not be printing "insufficient permissions" errors. BTW, a good command to use instead of axe in such cases is sudo dmesg -Hwl err+
From adigitoleo (Leon) to ~rjarry/aerc-discuss
> I'm not sure when it started but the home or the end key don't behave > correctly when I write an email in aerc. Precisely, the home key emits > Ctrl-a, and the end key emits Ctrl-d. I'm still on aerc 0.17 and it works fine (with NeoVim 0.10) so it could be a vaxis issue, if you are on aerc 0.18.
From adigitoleo (Leon) to ~martanne/devel
> I'm pretty sure wl-copy does not take the daemon approach I think this is generally correct, there is no OS-level daemon process that owns clipboard data under Wayland. This blog post has some more details: [1]. It was discussed on hacker news [2]. [1]: https://whynothugo.nl/journal/2022/10/21/how-the-clipboard-works/ [2]: https://news.ycombinator.com/item?id=33326523
From adigitoleo (Leon) to ~adigitoleo/public-inbox
Currently, doing `:HauntHelp` or `:HauntMan` twice in a row doesn't work as it should. It is necessary to close the first help/man window before opening a new one, otherwise all hell breaks loose with the autocommands. I've been implementing a test suite in quark.nvim and now also in haunt.nvim which might help in diagnosing the issue.
From adigitoleo (Leon) to ~adigitoleo/public-inbox
The lua module itself is simply `quark` without the `.nvim` suffix. If that still doesn't work, I'd need to test with whichever plugin manager you're using, is it lazy.nvim?