Portugal
Passionate Computer Science student. I mostly work with Python, Kotlin and some Lua, but I'm learning Rust.
Check my "unsorted" git repositories here.
(recently changed e-mail address from tmpod@pm.me and due to sourcehut not yet supporting multiple addresses per account, my old commits will not be linked to this account)
From tmpod to ~rjarry/aerc-discuss
This release is *huuuge*! Good job to everyone involved, and thank you so much for the quality work <3 Cheers!
From tmpod to ~rjarry/aerc-discuss
PS: Sorry for the lack of wrapping! Wrote that on K-9 and forgot it doesn't hardwrap .-.
From tmpod to ~rjarry/aerc-discuss
Hello! Whenever I'm doing my periodic inbox sorting or when I'm trying to find a message in my archive, something that always bugs me is that aerc's search only looks for matches in titles, making it fairly difficult to quickly identify e-mails from a specific sender. I know I could (and probably should) use a more advanced and featureful tool for this (have yet to get my hands into stuff like notmuch), but it would certainly be cool to have it built in aerc. Is it already possible to do this? If not, would you be open to a patch implementing it? Cheers! ~tmpod
From tmpod to ~rjarry/aerc-discuss
SOCKS is a proxy protocol, and socksify redirects all internet traffic from a program to the specified proxy server (passed as an env var, for example). In this case, the HTML filter is redirecting all potential requests to localhost, which most likely will fail, thus preventing any phoning home from e-mails. So, to make your lynx filter, you should keep the socksify wrapper and only change the w3m call. I hope this helps! :)
From tmpod to ~tmpod/eigen-devel
Applied, thank you! Quickly amended the commit to reflow the paragraphs, and save a roundtrip :P To git@git.sr.ht:~tmpod/eigen .. master -> master
From tmpod to ~tmpod/eigen-devel
Applied and pushed, thank you! :3 I made a small commit after yours just to reflow the paragraphs to the 100 char limit (which wasn't specfied anywhere, my bad!). To git@git.sr.ht:~tmpod/eigen .. master -> master
From tmpod to ~tmpod/eigen-devel
Lovely!
From tmpod to ~tmpod/eigen-devel
> I've managed to build Eigen and run it successfully with a bit of > setup with KWallet. I've found that KWallet used with Eigen requires > libqca-ossl which is a plugin to QCA, a Qt library that KWallet uses. I hadn't noticed that, the plugin seems to have come already bundled with my system's QCA package. Nice find! > Detail how to build Eigen with cargo and how to run the program. > Outline the dependencies needed to run it and the the issues one > might run into when using Eigen without a keyring, or using KWallet > without libqca-ossl. This will guide future users away from making > the mistakes I did.
From tmpod to ~tmpod/eigen-devel
> Improves a lot of the language in the readme so that it can be better > understood. Yes, this is great, thank you so much! > I have one question though: in the section titled "Why > just desktop?", what is meant by "form factor transitions" and > "paradigm translations"? What I meant to say was that, typically, single-codebase apps tend to apply the same concepts across form factors, e.g, big touch-ready components being used in desktop applications.
From tmpod to ~tmpod/eigen-devel
Hello Jeremy, First of all, thank you for reaching out! You're the first person to see eigen and to use the mailing lists :D This could have been sent to eigen-discuss, as eigen-devel is more for patches, but it's all good. Now, eigen was, indeed, not compilable at that commit, because of a couple of my mistakes doing previous commits. Since eigen is still *very much* in an early stage, I'm still often changing a lot of files when working on a specific feature, and often end up working on multiple features too! When it comes time to commit something, I end up doing a lot of partial selection, and splitting my changes into multiple commits.