~tmpod

Portugal

https://tmpod.dev/

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)

~tmpod/eigen-devel

Last active 23 hours ago

~tmpod/eigen-announce

Last active a day ago

~tmpod/eigen-discuss

Last active 27 days ago

~tmpod/lemmy.pt-discuss

Last active 7 months ago

~tmpod/lemmy.pt-devel

Last active 7 months ago

~tmpod/lemmy.pt-announce

Last active 7 months ago

~tmpod/toasty-lc3-vm

Last active 1 year, 6 months ago

~tmpod/public-inbox

Last active 1 year, 6 months ago

~tmpod/remmy

Last active 2 years ago

~tmpod/memusage-lite

Last active 3 years ago
View more

Recent activity

Re: [PATCH eigen v2 2/2] Add basic building/usage section to readme 23 hours ago

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

Re: [PATCH eigen v2 1/2] Improve language in readme 23 hours ago

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

Re: [PATCH eigen 2/2] Add basic building/usage section to readme a day ago

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.

Re: [PATCH eigen 1/2] Improve language in readme a day ago

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.

Re: Eigen fails to compile a day ago

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.

Re: Using terminal bell when composing new message through mailto: 4 days ago

From tmpod to ~rjarry/aerc-discuss

> It sounds to me like what tmpod wants is the ability to either (1)
> ring the bell in that existing aerc instance so that it can be brought
> into focus, or (2) skip the IPC and just compose the email directly in
> the new aerc instance.
>
> I also feel like the current behavior is confusing -- I sometimes
> click on a mailto link and think nothing has happened, only to
> eventually realize that I have aerc open somewhere already.

Yes, this is exactly it!

Using terminal bell when composing new message through mailto: 7 days ago

From tmpod to ~rjarry/aerc-discuss

Hello!

I've been using aerc as my daily driver for quite a while now, and
finally got around to submitting this idea to the mailing list :P

In essence, my problem is that, after clicking on `mailto:` links, I have
to go find my terminal window with aerc to start composing the message.
Since I make heavy use of workspaces (and I'm not always consistent with
window positioning; my bad!), it would help quite a bit if aerc issued a
bell command, that makes the terminal window request attention.

Another idea would be to add some flag for opening `mailto:` requests in
a separate window, loading just the compose tab (and maybe the composing
account?). That way you had a one-shot window, like you do in

Re: Loading newest email first 6 months ago

From tmpod to ~rjarry/aerc-discuss

No, how do I enable those?
I looked at the default config files[1] and couldn't find those keys.

~tmpod

[1]: https://git.sr.ht/~rjarry/aerc/tree/master/item/config