Rahul Garg

> I can add them. Need some time though. No rush, just wanted to bring it up. Thank you for agreeing to add them 🙂

Have been following this issue for a while now and was wondering if we could perhaps split it into potentially doable tasks? Just for information, there have been a few...

> Although additionally, with enhancements to nvim itself, there’s a lot of other things we could do to make the whole plugin a lot simpler. It may be worth doing...

May not be an ideal solution but can you also try removing packaged erlang and reinstalling via [asdf](https://asdf-vm.com/guide/getting-started.html). The only reason I say is because I am on the exact...

x-posting from [discord](https://discord.com/channels/404106811252408320/795832567265624095/807763374980726815) for reference: A few things: - I'm pretty sure that you can do a similar testing strategy as done in blockchain_payment_v2_SUITE, it works largely independent of the...

I forgot to mention this earlier, I don't see `blockchain_txn.erl` being updated here (yet). Basically `blockchain_txn` requires ensuring a particular txn's actor, type, wrapping, dependencies etc. (i.e. how do we...

We were discussing doing something like this at some point for `reward_v2` txns. It does the opposite of introducing a new type though. ```proto syntax = "proto3"; package helium; message...

And it still uses buildkite :man_facepalming:

> From what I understand, this is to darken the `background` of mvim-tree etc. right? Or an inactive split, I did something similar for [gruvbox](https://github.com/ellisonleao/gruvbox.nvim/pull/149) some time back for reference.

@4sa617 I no longer have this keyboard unfortunately but the biggest blocker here are the packet capture files. Hopefully someone can post those here.