home.social

#notmuch — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #notmuch, aggregated by home.social.

  1. Follow up on this, we have planned to use #notmuch to index and clean the mail inbox.

  2. Getting more comfy with the email patch workflow again.

    I also wrote some utilities for applying patchsets with #notmuch and #b4 -> codeberg.org/matthiasbeyer/not

  3. Getting more comfy with the email patch workflow again.

    I also wrote some utilities for applying patchsets with #notmuch and #b4 -> codeberg.org/matthiasbeyer/not

  4. Getting more comfy with the email patch workflow again.

    I also wrote some utilities for applying patchsets with #notmuch and #b4 -> codeberg.org/matthiasbeyer/not

  5. Getting more comfy with the email patch workflow again.

    I also wrote some utilities for applying patchsets with #notmuch and #b4 -> codeberg.org/matthiasbeyer/not

  6. Getting more comfy with the email patch workflow again.

    I also wrote some utilities for applying patchsets with #notmuch and #b4 -> codeberg.org/matthiasbeyer/not

  7. ....and 🎶 One More Cup 🎶 .....as Bob Dylan's number soothing in my ears 🎧

    while sipping the damn coffee ☕

    Staring at these 😜

  8. Hello Fediverse!

    Is there anyone out there still integrating #mutt in #orgmode with #notmuch
    as described here: upsilon.cc/~zack/blog/posts/20

    I once had a working environment and as life happened I stopped using it at some point. Now it doesn't work anymore and I don't know where to start.

    The links to emails from back then still work, but the remember-mail portion doesn't.

    Grateful for any pointers. Thanks!

  9. OK, I'm going to give it another try to make #emacs, #msmtp, #mbsync, #notmuch work for taming email. I'm looking (sternly 😡 ) at you, gmail forced down my throat by my <insert-employer-entity-here>...

    My ideal setup would likely be simple: edit messages from emacs, store messages locally, fuzzy search available, viewing email threads, and completion for filling *to* and *from* fields.

    How hard could it be? -- Wish me luck.

  10. OK, I'm going to give it another try to make #emacs, #msmtp, #mbsync, #notmuch work for taming email. I'm looking (sternly 😡 ) at you, gmail forced down my throat by my <insert-employer-entity-here>...

    My ideal setup would likely be simple: edit messages from emacs, store messages locally, fuzzy search available, viewing email threads, and completion for filling *to* and *from* fields.

    How hard could it be? -- Wish me luck.

  11. OK, I'm going to give it another try to make #emacs, #msmtp, #mbsync, #notmuch work for taming email. I'm looking (sternly 😡 ) at you, gmail forced down my throat by my <insert-employer-entity-here>...

    My ideal setup would likely be simple: edit messages from emacs, store messages locally, fuzzy search available, viewing email threads, and completion for filling *to* and *from* fields.

    How hard could it be? -- Wish me luck.

  12. OK, I'm going to give it another try to make #emacs, #msmtp, #mbsync, #notmuch work for taming email. I'm looking (sternly 😡 ) at you, gmail forced down my throat by my <insert-employer-entity-here>...

    My ideal setup would likely be simple: edit messages from emacs, store messages locally, fuzzy search available, viewing email threads, and completion for filling *to* and *from* fields.

    How hard could it be? -- Wish me luck.

  13. OK, I'm going to give it another try to make #emacs, #msmtp, #mbsync, #notmuch work for taming email. I'm looking (sternly 😡 ) at you, gmail forced down my throat by my <insert-employer-entity-here>...

    My ideal setup would likely be simple: edit messages from emacs, store messages locally, fuzzy search available, viewing email threads, and completion for filling *to* and *from* fields.

    How hard could it be? -- Wish me luck.

  14. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  15. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  16. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  17. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  18. Thinking of revisiting and decluttering my #emacs configuration, little by little. If I carve out the time, I'd love to document the process of finding what I no longer use and tuning the what I already need. Might be fun.

    I mostly use #orgmode #auctex #notmuch #ledgermode. Also do some programming in #python #bash and #c . This might be an exciting opportunity to check out what's up in the emacs world!

  19. I've been installing on a fresh computer this week.
    For some reason I decided to install #mu4e on #emacs last night. I don't know what I was thinking.
    Mu4e is famous for its horrible install experience.

    I finally hit a last straw. I had two choices, find a better way or switch to #notmuch. I found a better way, but I might still switch just on principle. Mu4e has been a pain for almost 10 years. Seems like decades.

    I wrote a makefile and a bit of elisp. I called it mu4e.
    I hope it relieves some pain for all mu4e users everywhere.

    codeberg.org/ZeniesQis/mu4e

  20. While sipping hot lemon tea 🍋 ☕ and staring at this damn thing ....

  21. I wrote a new blog post about how to setup #neomutt #email with Office 365, using #mbsync #msmtp and #notmuch, along with how to make it work with multiple accounts:

    cosroe.com/2025/04/neomutt-not

  22. I wrote a new blog post about how to setup #neomutt #email with Office 365, using #mbsync #msmtp and #notmuch, along with how to make it work with multiple accounts:

    cosroe.com/2025/04/neomutt-not

  23. I wrote a new blog post about how to setup #neomutt #email with Office 365, using #mbsync #msmtp and #notmuch, along with how to make it work with multiple accounts:

    cosroe.com/2025/04/neomutt-not

  24. While sipping my chilled Tropical drink 🍹 and staring at the damn thing ...😜

  25. I tried + + which is cool, but weirdly only one-way and only really works when run from a single machine as it's stateful. I can't move around mails and make folders etc and git annex drop mails and keep others to decide what's on the server and what's not. It gets messy. Feels like it's a very nice solution to grab mail from the server and then manage it only locally and sync it around with git annex, but not if you want your mails e.g. on your phone client as well.