logo

drewdevault.com

[mirror] blog and personal website of Drew DeVault git clone https://hacktivis.me/git/mirror/drewdevault.com.git

Configuring-aerc-for-git.md (2444B)

    

  1. ---
  2. date: 2020-04-20
  3. layout: post
  4. title: Configuring aerc for git via email
  5. tags: ["workflow", "aerc", "git"]
  6. ---
  8. I use [aerc](https://aerc-mail.org) as my email client (naturally — I
  9. wrote it, after all), and I use [git send-email](https://git-send-email.io) to
  10. receive patches to many of my projects. I designed aerc specifically to be
  11. productive for this workflow, but there are a few extra things that I use in my
  12. personal aerc configuration that I thought were worth sharing briefly. This blog
  13. post will be boring and clerical, feel free to skip it unless it's something
  14. you're interested in.
  16. When I want to review a patch, I first tell aerc to `:cd sources/<that
  17. project>`, then I open up the patch and give it a read. If it needs work, I'll
  18. use "rq" ("reply quoted"), a keybinding which is available by default, to open
  19. my editor with the patch pre-quoted to trim down and reply with feedback inline.
  20. If it looks good, I use the first of my custom keybindings: "ga", short for git
  21. am. The entry in `~/.config/aerc/binds.conf` is:
  23. ```
  24. ga = :pipe -mb git am -3<Enter>
  25. ```
  27. This pipes the entire message (-m, in case I'm viewing a message part) into `git
  28. am -3` (-3 uses a three-way merge, in case of conflicts), in the background
  29. (-b). Then I'll use C-t (ctrl-T), another keybinding which is included by
  30. default, to open a terminal tab in that directory, where I can compile the code,
  31. run the tests, and so on. When I'm done, I use the "gp" keybinding to push the
  32. changes:
  34. ```
  35. gp = :term git push<Enter>
  36. ```
  38. This runs the command in a new terminal, so I can monitor the progress. Finally,
  39. I like to reply to the patch, letting the contributor know their work was merged
  40. and thanking them for the contribution. I have a keybinding for this, too:
  42. ```
  43. rt = :reply -Tthanks<Enter>
  44. ```
  46. My "thanks" template is at `~/.config/aerc/templates/thanks` and looks like
  47. this:
  49. ```
  50. Thanks!
  52. {% raw %}
  53. {{exec "{ git remote get-url --push origin;
  54.     git reflog -2 origin/master --pretty=format:%h; }
  55.   | xargs printf 'To %s\n   %s..%s  master -> master\n'" ""}}
  56. {% endraw %}
  57. ```
  59. That git command prints a summary of the most recent push to master. The result
  60. is that my editor is pre-filled with something like this:
  62. ```
  63. Thanks!
  65. To git@git.sr.ht:~sircmpwn/builds.sr.ht
  66.    7aabe74..191f4a0  master -> master
  67. ```
  69. I occasionally append a few lines asking questions about follow-up work or
  70. clarifying the deployment schedule for the change.