This is a good point. I'll take another look at the pg locks patches
soon.

Thanks!

To git.sr.ht:~sircmpwn/paste.sr.ht
   c5e3f55..d6d143a  master -> master
 * [new tag]         0.6.1 -> 0.6.1

Thanks!

To git.sr.ht:~sircmpwn/aerc
   f1b365d..48a88fe  master -> master

Thanks!

To git.sr.ht:~sircmpwn/aerc
   f1b365d..48a88fe  master -> master

Thanks!

To git.sr.ht:~sircmpwn/aerc
   f1b365d..48a88fe  master -> master

On Thu Oct 10, 2019 at 9:19 AM Srivathsan Murali wrote:
> I agree that going with this approach makes templates more useful and
> clears up a lot of things about how we can make templates work for 
> replies and forwards.
> 
> I am happy to continue working on a implementation inside the
> composer using golang text templates. But I am still getting my head
> around golang and how aerc works.
> 
> I will read up and ask more questions on some parts if that is fine.

No problem, take your time.

It seems that thanks to your email, you've helped me circumvent a future
fuck-up, so thank you for that. There is one project that I cut release
branches for (sway) and the updated semver script is going to break for
it. I'll update the script with an override when I ship the next sway
release.

Hey Merlin, thanks for sharing your feedback. Have you seen my follow-up
article?

https://drewdevault.com/2019/10/10/RaptorCS-redemption.html

In short, Raptor corrected all of my issues, including the poor support
experience. I agree that the original article may have been harmful -
but I think in the long run, with this follow-up taken into
consideration, the effects are positive. Raptor's support system was
totally broken, and they've overhauled it and implemented more
self-service options. I see that as a win.

To help offset the negative effects of the first article, I also reached
out to the Hacker News moderators and asked for a little help putting

I plan on moving to migadu once they finish the improvements they've
been working on.

Yes, that's what I'm saying.