Configured #emacs #email today for 2 google accounts...

Configured #emacs #email today for 2 google accounts of mine. I postponed this action for almost 2 years. It took me ~5 hours of pain. And I am happy to use almost completely pluggable Andrew's (@abcdw) #rde features setup (via #guix :guix:)

I need it to work with git-patch + email-based workflow as an amateur hacker. ✉️ :git:

I just couldn't force myself to do it for so long cos I am so internally against "editor as email/irc/etc-client".

Text input systems should raise.

Like 17 August at 18:26 | Open on fosstodon.org

5 comments

Bounga ⌨️ 🎸🚲

@shegeley @abcdw

> I need it to work with git-patch + email-based workflow as an amateur hacker. ✉️ :git:

Working with Sourcehut?

What email client are you using?

I’m using mu4e that I really like but I still haven’t found how to effectively use an email based workflow.

It’s not related to mu4e but rather to how to pipe diff to magit and work with it.

17 August at 18:47 | Open on ruby.social

Bounga ⌨️ 🎸🚲

@shegeley @abcdw I don’t have any problem using email based workflow if I use the classic tooling (ie: git am / git email) in the terminal but it doesn’t feel the right way to do it using emacs.

17 August at 18:53 | Open on ruby.social

Grigory Shepelev

@bounga using notmuch. but I don't like that kind of "context switch" when applying, not only sending patches. having to launch other mail client (what? browser gmail, thunderbird, etc), having to save them as files inside that context and them applying.

I'm not against good UIs that minimizes context switching, but against all-in-one stuff

17 August at 19:16 | Open on fosstodon.org

Andrew Tropin

@bounga @shegeley For applying single straightforward patches I either use notmuch-show-pipe-message (|) and `git am -3s` or piem in case of patch series and non-trivial patches.

18 August at 4:07 | Open on fosstodon.org

Grigory Shepelev

And I don't completely understand how it works. Yet.

17 August at 19:44 | Open on fosstodon.org