On Sat, May 24 2025, hob...@poukram.net wrote:

> Kristoffer Balintona <krisbalint...@gmail.com> writes:
>
>> [... 19 lines elided]
>>>
>>> I've been using mu4e for a while now, but in my gnus email days I
>>> used gnorb, and I dearly miss those features in my current
>>> workflow...
>>>
>>> https://elpa.gnu.org/packages/gnorb.html
>>>
>>> Thanks,
>>
>> Oh wow! Thanks for mentioning Gnorb. I hadn't heard of it before. (I
>> started using Emacs after the latest release of Gnorb, it seems.)
>> Going through Gnorb's manual was interesting to see how one might
>> keep track of emails via org headlines while keeping them up-to-date
>> automatically. I wonder if something similar could be done with
>> notmuch...
>
> Hmmm... gnus, notmuch, mu4e, message-mode,... all of these are just
> emacs interfaces to display (email) messages. I know notmuch only by
> name, but if it's as configurable as the others, it shouldn't be a
> problem to add a bit of information to how it displays a list of
> messages and the current message being read.

I agree.

> Now one tricky bit is to get the information to display.

Agreed again.

>mu4e and gnus both have a way to refer to a particular message
>unequivocally, I guess notmuch has a similar mechanism. That's how one
>links to a particular message in org.
>
> With the recently crafted https://github.com/meedstrom/org-mem it's
> possible and fast to get a list of org headings which include a
> particular link. Like, for example, all org headings that link to the
> current message.

I had something similar in mind too, since I use org-node.[1] But I’m
not sure org-mem collects all the org data users would like in this
case. Maybe one could use org-sql[2] instead? I haven’t used it before,
so not sure about its speed.

> Something similar to org-roam's backlinks buffer could be used to show
> those headings. And somehow a header or hint in the displayed message
> could be added to show that there are org headings linking to that
> message, so you know that you can open the backlinks buffer. Or
> display it automatically if you prefer.
>
> If there is only one backlink, you can also simply directly display it
> as a header in the message view.
>
> Then the sky is the limit to what automation one could add :-)

I think the hardest part of trying to achieve a tightly coupled
email-org-agenda workflow is deciding what the ideal workflow would be.
I think there are a lot of technically feasible things one could
program, but it isn’t clear at all which ones one would actually use and
benefit from in the long term.

For me, I think a crucial piece is figuring out how to update org tasks
(that already link to email(s)) as one receives emails, doing so in an
algorithmic way that actually approximates what I’d do manually.

> Now I can read code and sometimes understand it, but I'm not a
> developer, so this is all speculation at the moment :-) But now that a
> global schema is written down, it seems that the hard parts are
> already done, all that is missing is some glue code between them...
> and I have missed something like gnorb since I switched to mu4e... I
> might give it a try... if time permits... so don't hold your breath
> :-)

I’d be interested to see the result if you ever do.

Footnotes:
[1]  https://github.com/meedstrom/org-node
[2]  https://github.com/ndwarshuis/org-sql

-- 
Kind regards, Kristoffer

Reply via email to