On Tue, 15 Dec 2009 16:36:04 -0800, Carl Worth wrote:
> But yes, if you can make your links depend only on message IDs then you
> can get reliable results even before we start including thread IDs in
> the dump output. The result of "notmuch show --entire-thread id:foo" is
> quite similar to the
On Tue, 15 Dec 2009 16:36:04 -0800, Carl Worth wrote:
> But yes, if you can make your links depend only on message IDs then you
> can get reliable results even before we start including thread IDs in
> the dump output. The result of "notmuch show --entire-thread id:foo" is
> quite similar to the
On Tue, 15 Dec 2009 17:23:59 -0400, David Bremner wrote:
> I then try to visit these threads on a different machine, but of course
> that thread id doesn't exist there, since the database was reindexed and
> tags reimported.
Ah, good point.
I've wanted reproducible thread IDs also for a similar
I write links to notmuch threads into my todo list in org-mode.
I then try to visit these threads on a different machine, but of course
that thread id doesn't exist there, since the database was reindexed and
tags reimported.
I don't know if it is in any way practical, but it would be nice from
On Tue, 15 Dec 2009 17:23:59 -0400, David Bremner wrote:
> I then try to visit these threads on a different machine, but of course
> that thread id doesn't exist there, since the database was reindexed and
> tags reimported.
Ah, good point.
I've wanted reproducible thread IDs also for a similar
I write links to notmuch threads into my todo list in org-mode.
I then try to visit these threads on a different machine, but of course
that thread id doesn't exist there, since the database was reindexed and
tags reimported.
I don't know if it is in any way practical, but it would be nice from
