Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
On Sun, 25 Jun 2017, David Bremner wrote: > Daniel Kahn Gillmor writes: > >> >> For example, would it make sense to have "notmuch new" (and "notmuch >> insert") do "thread-based propagation" of specific tags? for example, >> consider the following (i've just made up the config options): >> >> notmuch config set new.from_self_tags participated >> notmuch config set new.propagate_thread_tags participated >> >> the idea is that "new.from_self_tags" would be applied by "notmuch new" or >> "notmuch insert" if the message was explicitly from: user.primary_email >> or user.other_email. > > At the moment I'm more inclined to work on "doing things right" by > adding xapian documents (database items) for threads. Many of the ideas > in this thread amount to working around their absence. OTOH, it's > certainly true that this last idea (unlike some of the query ideas) > would be relatively straightforward to impliment. I admit I didn't thoroughly read the entire thread... but I think there's an alternative to adding thread documents, with reasonable design, to address the original problem in this thread. Have a new prefix that evaluates to the threads of the sub-query passed as the prefix value, say thread-of: that you could use as part of the query. (Or, make thread: work on queries as well as thread IDs.) The original query in this thread becomes: thread-of:"from:me" and thread-of:"from:jian" and not thread-of:"from:dave". As a side effect, this also makes thread: queries portable across databases via thread-of:"id:". I think this should be doable in current Xapian that supports custom prefix handlers. IIRC the idea was suggested by Austin ages ago. BR, Jani. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
On Mon, 26 Jun 2017, Matt Armstrong wrote: > David Bremner writes: > >> Daniel Kahn Gillmor writes: >> >>> >>> For example, would it make sense to have "notmuch new" (and "notmuch >>> insert") do "thread-based propagation" of specific tags? for example, >>> consider the following (i've just made up the config options): >>> >>> notmuch config set new.from_self_tags participated >>> notmuch config set new.propagate_thread_tags participated >>> >>> the idea is that "new.from_self_tags" would be applied by "notmuch new" or >>> "notmuch insert" if the message was explicitly from: user.primary_email >>> or user.other_email. >> >> At the moment I'm more inclined to work on "doing things right" by >> adding xapian documents (database items) for threads. Many of the >> ideas in this thread amount to working around their absence. OTOH, >> it's certainly true that this last idea (unlike some of the query >> ideas) would be relatively straightforward to impliment. > > David, that makes a lot of sense. > > Take two other examples from my post-hook: > > # Unmute all threads with new messages sent to me. > notmuch search --output=threads tag:new AND tag:me | \ > xargs --no-run-if-empty notmuch tag -muted -- > > # Remove all muted threads from the inbox and mark > # every message in them muted. > notmuch search --output=threads tag:muted | \ > xargs --no-run-if-empty notmuch tag -inbox +muted -- > > Above I'm just operating on all the messages in a thread as a unit. If > notmuch had a 'database item' for each thread, I could potentially tag > just that to achieve similar results with simpler commands. FWIW, this is my approach to "thread tags", from my post-new hook: # Propagate thread tags THREAD_TAGS="muted" for tag in $THREAD_TAGS; do notmuch tag +$tag $(notmuch search --output=threads tag:$tag) done Basically if I tag a message muted, all messages in the thread will get the tag on next post-new. This may or may not be related to the problems people in this thread are trying to solve. ;) BR, Jani. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
Matt Armstrong writes: > David Bremner writes: > > It has some subtle implications. E.g. when I tag through a particular > UI do I mean to tag a particular message or the thread? Is it worth > making the user think about the difference? Is there some way to > express this such that they never do? Are some tags configured to > always apply to the thread? Are these the only tags that do? Or do > "thread tags" always contain the union of all associated message tags? My initial thinking is that thread documents would just have the union of the terms (tags and otherwise) of all messages in the thread. So they'd be visible only when querying, and not need to be dumped and restored. Before I get too worried about the UI (i.e. how does one specify that a query is meant to be applied threadwise), I want to have some idea about the time and space costs of maintaining those extra documents in the database. d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
Daniel Kahn Gillmor writes:
> Hey all--
>
> I really appreciate the thought and experimentation and research that's
> gone into this thread!
>
> On Thu 2017-06-22 17:00:58 -0700, Matt Armstrong wrote:
>> # All threads in which I participate get tag:participated
>> # 1) Find all threads with a message tagged new
>> # (finding all 'today' messages helps during testing,
>> # but isn't necessary)
>> # 2) Run through "xargs -s 2048 echo" to to group threads
>> # lines of about 2K in size.
>> # 3) For each line (2) produces, narrow the threads to
>> # those containing a message from me.
>> # 4) For each such thread, tag every message with +participated.
>> notmuch search --output=threads tag:new OR date:today | \
>> xargs -s 2048 echo | \
>> xargs -I '{}' notmuch search \
>> --output=threads from:marmstrong AND \( '{}' \) | \
>> sed -e 's,^,+participated -- ,' | \
>> notmuch tag --batch
>
> This makes sense to me, modulo the split into 2048-octet lines (magic
> numbers make me nervous, though i think i understand why you've included
> it).
Yes, the two xargs commands and "2048 business" is just a hack to work
around the documented limitations of "xargs -I". I'd love to come up
with a simpler way to do this. I suspect there is one, but when it
comes to this kind of Unix shell hackery, I usually stop once I get to
something that works. :)
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
David Bremner writes: > Daniel Kahn Gillmor writes: > >> >> For example, would it make sense to have "notmuch new" (and "notmuch >> insert") do "thread-based propagation" of specific tags? for example, >> consider the following (i've just made up the config options): >> >> notmuch config set new.from_self_tags participated >> notmuch config set new.propagate_thread_tags participated >> >> the idea is that "new.from_self_tags" would be applied by "notmuch new" or >> "notmuch insert" if the message was explicitly from: user.primary_email >> or user.other_email. > > At the moment I'm more inclined to work on "doing things right" by > adding xapian documents (database items) for threads. Many of the > ideas in this thread amount to working around their absence. OTOH, > it's certainly true that this last idea (unlike some of the query > ideas) would be relatively straightforward to impliment. David, that makes a lot of sense. Take two other examples from my post-hook: # Unmute all threads with new messages sent to me. notmuch search --output=threads tag:new AND tag:me | \ xargs --no-run-if-empty notmuch tag -muted -- # Remove all muted threads from the inbox and mark # every message in them muted. notmuch search --output=threads tag:muted | \ xargs --no-run-if-empty notmuch tag -inbox +muted -- Above I'm just operating on all the messages in a thread as a unit. If notmuch had a 'database item' for each thread, I could potentially tag just that to achieve similar results with simpler commands. It has some subtle implications. E.g. when I tag through a particular UI do I mean to tag a particular message or the thread? Is it worth making the user think about the difference? Is there some way to express this such that they never do? Are some tags configured to always apply to the thread? Are these the only tags that do? Or do "thread tags" always contain the union of all associated message tags? Fun stuff. :) ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
Well, it's not quite *away* from Turing complete configuration... but it sounds
like you might like the program that computes tags for new messages to get not
only the message but also its thread id and read-only access to the database?
Then both filtering "participated" and computing "participated" from "sent"
become easy. And fancier ideas like computing tags from senders, list-id, the
rest.
--
Brian Sniffen
> On Jun 25, 2017, at 11:46 AM, Daniel Kahn Gillmor
> wrote:
>
> Hey all--
>
> I really appreciate the thought and experimentation and research that's
> gone into this thread!
>
>> On Thu 2017-06-22 17:00:58 -0700, Matt Armstrong wrote:
>> # All threads in which I participate get tag:participated
>> # 1) Find all threads with a message tagged new
>> # (finding all 'today' messages helps during testing,
>> # but isn't necessary)
>> # 2) Run through "xargs -s 2048 echo" to to group threads
>> # lines of about 2K in size.
>> # 3) For each line (2) produces, narrow the threads to
>> # those containing a message from me.
>> # 4) For each such thread, tag every message with +participated.
>> notmuch search --output=threads tag:new OR date:today | \
>> xargs -s 2048 echo | \
>> xargs -I '{}' notmuch search \
>> --output=threads from:marmstrong AND \( '{}' \) | \
>> sed -e 's,^,+participated -- ,' | \
>> notmuch tag --batch
>
> This makes sense to me, modulo the split into 2048-octet lines (magic
> numbers make me nervous, though i think i understand why you've included
> it).
>
> That said, i've been trying to think lately about how to make notmuch a
> tool that's usable by normal humans, who probably won't want to
> understand all the moving pieces here. I don't want yet another MUA
> that requires you to edit a turing-complete config file to get useful
> functionality -- we already have mutt for that :)
>
> Is there a way that we can push this idea/functionality further into
> the core of notmuch in a way that makes it easier to use?
>
> For example, would it make sense to have "notmuch new" (and "notmuch
> insert") do "thread-based propagation" of specific tags? for example,
> consider the following (i've just made up the config options):
>
>notmuch config set new.from_self_tags participated
>notmuch config set new.propagate_thread_tags participated
>
> the idea is that "new.from_self_tags" would be applied by "notmuch new" or
> "notmuch insert" if the message was explicitly from: user.primary_email
> or user.other_email.
>
> and additionally, if a message was inserted into a thread which has any
> of the new.propagated_thread_tags applied, the new message would also
> get those tags.
>
> What do y'all think?
>
>--dkg
> ___
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
Daniel Kahn Gillmor writes: > > For example, would it make sense to have "notmuch new" (and "notmuch > insert") do "thread-based propagation" of specific tags? for example, > consider the following (i've just made up the config options): > > notmuch config set new.from_self_tags participated > notmuch config set new.propagate_thread_tags participated > > the idea is that "new.from_self_tags" would be applied by "notmuch new" or > "notmuch insert" if the message was explicitly from: user.primary_email > or user.other_email. At the moment I'm more inclined to work on "doing things right" by adding xapian documents (database items) for threads. Many of the ideas in this thread amount to working around their absence. OTOH, it's certainly true that this last idea (unlike some of the query ideas) would be relatively straightforward to impliment. d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
finding incoming messages in threads in which i've participated [was: Re: find threads where I and Jian participated but not Dave]
Hey all--
I really appreciate the thought and experimentation and research that's
gone into this thread!
On Thu 2017-06-22 17:00:58 -0700, Matt Armstrong wrote:
> # All threads in which I participate get tag:participated
> # 1) Find all threads with a message tagged new
> # (finding all 'today' messages helps during testing,
> # but isn't necessary)
> # 2) Run through "xargs -s 2048 echo" to to group threads
> # lines of about 2K in size.
> # 3) For each line (2) produces, narrow the threads to
> # those containing a message from me.
> # 4) For each such thread, tag every message with +participated.
> notmuch search --output=threads tag:new OR date:today | \
> xargs -s 2048 echo | \
> xargs -I '{}' notmuch search \
> --output=threads from:marmstrong AND \( '{}' \) | \
> sed -e 's,^,+participated -- ,' | \
> notmuch tag --batch
This makes sense to me, modulo the split into 2048-octet lines (magic
numbers make me nervous, though i think i understand why you've included
it).
That said, i've been trying to think lately about how to make notmuch a
tool that's usable by normal humans, who probably won't want to
understand all the moving pieces here. I don't want yet another MUA
that requires you to edit a turing-complete config file to get useful
functionality -- we already have mutt for that :)
Is there a way that we can push this idea/functionality further into
the core of notmuch in a way that makes it easier to use?
For example, would it make sense to have "notmuch new" (and "notmuch
insert") do "thread-based propagation" of specific tags? for example,
consider the following (i've just made up the config options):
notmuch config set new.from_self_tags participated
notmuch config set new.propagate_thread_tags participated
the idea is that "new.from_self_tags" would be applied by "notmuch new" or
"notmuch insert" if the message was explicitly from: user.primary_email
or user.other_email.
and additionally, if a message was inserted into a thread which has any
of the new.propagated_thread_tags applied, the new message would also
get those tags.
What do y'all think?
--dkg
signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
Gaute Hope writes:
> Gaute Hope writes on juni 22, 2017 8:08:
>> Daniel Kahn Gillmor writes on juni 21, 2017 23:30:
>>> On Wed 2017-06-21 13:04:53 -0700, Matt Armstrong wrote:
For what it is worth, I've found this idea from Daniel intriguing and
pretty useful in practice:
"show me threads in which i've participated, where there are some
messages flagged with 'inbox'"
I implement it like this in my post-new hook:
# All messages in threads in which I participate get tag:participated
notmuch search --output=threads from:marmstrong | \
sed -e 's,^,+participated -- ,' | \
notmuch tag --batch
>>>
>>> cool, thx for the suggestion.
>>>
>>> the "notmuch search" part of the pipeline alone takes ~19s (wall time,
>>> and actual CPU time) for me though :/ It returns 30504 threads! how
>>> many threads do you get?
>>
>> Is there any reason why you do not filter on a tag 'new' as well?
>>
>> notmuch search --output=threads from:marmstrong and tag:new | \
>>sed -e 's,^,+participated -- ,' | \
>>notmuch tag --batch
>>
>
> Nevermind, I get it - it might be possible to add a temporary tag
> new-tag to the whole thread first and not just new messages. That might
> be faster. As long as all sent messages get the new tag as well.
Gaute, I took this as a challenge and came up with what I think is an
equivalent but more efficient approach. The disadvantage is that it is
much more complex. The advantage is that it runs in under 0.2 seconds
to process a day's worth of my "new" mail.
I now have this in my notmuch post-hook. I believe I could change the
"tag:new OR date:today" query to just "tag:new". The "OR date:today"
helped during interactive development.
# All threads in which I participate get tag:participated
# 1) Find all threads with a message tagged new
# (finding all 'today' messages helps during testing,
# but isn't necessary)
# 2) Run through "xargs -s 2048 echo" to to group threads
# lines of about 2K in size.
# 3) For each line (2) produces, narrow the threads to
# those containing a message from me.
# 4) For each such thread, tag every message with +participated.
notmuch search --output=threads tag:new OR date:today | \
xargs -s 2048 echo | \
xargs -I '{}' notmuch search \
--output=threads from:marmstrong AND \( '{}' \) | \
sed -e 's,^,+participated -- ,' | \
notmuch tag --batch
The basic idea is that each run of the notmuch post-hook will
incorporate relatively little mail, so the number of unique threads will
be relatively small. So, we just list them all by thread ID.
Then for each thread with new messages, we figure out which threads have
a message from:marmstrong (it need not be the new message).
We then tag all messages in each of those threads with +participated.
You said "it might be possible to add a temporary tag new-tag to the
whole thread first and not just new messages." -- Yes, and that is
implicitly what I am doing, except that each such thread is instead
tracked in an ephemeral way through the xargs based shell pipeline.
I did try an approach of explicitly labeling all messages in "new"
threads, temporarily, but that was slower.
You said "As long as all sent messages get the new tag as well." --
true, and I'm not sure about that. My primary use for this is to
discover new activity from others *after* I've participated in a thread,
so I don't much care if a thread that is "participated in" is not tagged
that way until some mail from somebody else arrives.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
Daniel Kahn Gillmor writes: > On Wed 2017-06-21 13:04:53 -0700, Matt Armstrong wrote: >> For what it is worth, I've found this idea from Daniel intriguing and >> pretty useful in practice: >> >> "show me threads in which i've participated, where there are some >>messages flagged with 'inbox'" >> >> I implement it like this in my post-new hook: >> >> # All messages in threads in which I participate get tag:participated >> notmuch search --output=threads from:marmstrong | \ >> sed -e 's,^,+participated -- ,' | \ >> notmuch tag --batch > > cool, thx for the suggestion. > > the "notmuch search" part of the pipeline alone takes ~19s (wall time, > and actual CPU time) for me though :/ It returns 30504 threads! how > many threads do you get? The query returns 6600 threads. I'm getting 2 seconds wall clock time. > you're effectively re-tagging every single message in every participated > thread every time you run "notmuch new", right? Yeah, the "batch script" that the above search+sed creates and pipes into "notmuch tag --batch" is 265K, but it only takes 0.5 seconds to execute. My understanding is that "notmuch tag" is smart enough to do no work if the tag is already present on a message, so the only changes happening in the database are actually for new stuff. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
Gaute Hope writes on juni 22, 2017 8:08: Daniel Kahn Gillmor writes on juni 21, 2017 23:30: On Wed 2017-06-21 13:04:53 -0700, Matt Armstrong wrote: For what it is worth, I've found this idea from Daniel intriguing and pretty useful in practice: "show me threads in which i've participated, where there are some messages flagged with 'inbox'" I implement it like this in my post-new hook: # All messages in threads in which I participate get tag:participated notmuch search --output=threads from:marmstrong | \ sed -e 's,^,+participated -- ,' | \ notmuch tag --batch cool, thx for the suggestion. the "notmuch search" part of the pipeline alone takes ~19s (wall time, and actual CPU time) for me though :/ It returns 30504 threads! how many threads do you get? Is there any reason why you do not filter on a tag 'new' as well? notmuch search --output=threads from:marmstrong and tag:new | \ sed -e 's,^,+participated -- ,' | \ notmuch tag --batch Nevermind, I get it - it might be possible to add a temporary tag new-tag to the whole thread first and not just new messages. That might be faster. As long as all sent messages get the new tag as well. pgpIkGDZ3Jptl.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
Daniel Kahn Gillmor writes on juni 21, 2017 23:30: On Wed 2017-06-21 13:04:53 -0700, Matt Armstrong wrote: For what it is worth, I've found this idea from Daniel intriguing and pretty useful in practice: "show me threads in which i've participated, where there are some messages flagged with 'inbox'" I implement it like this in my post-new hook: # All messages in threads in which I participate get tag:participated notmuch search --output=threads from:marmstrong | \ sed -e 's,^,+participated -- ,' | \ notmuch tag --batch cool, thx for the suggestion. the "notmuch search" part of the pipeline alone takes ~19s (wall time, and actual CPU time) for me though :/ It returns 30504 threads! how many threads do you get? Is there any reason why you do not filter on a tag 'new' as well? notmuch search --output=threads from:marmstrong and tag:new | \ sed -e 's,^,+participated -- ,' | \ notmuch tag --batch Regards, Gaute pgpUmguMAhigd.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
On Wed 2017-06-21 13:04:53 -0700, Matt Armstrong wrote: > For what it is worth, I've found this idea from Daniel intriguing and > pretty useful in practice: > > "show me threads in which i've participated, where there are some >messages flagged with 'inbox'" > > I implement it like this in my post-new hook: > > # All messages in threads in which I participate get tag:participated > notmuch search --output=threads from:marmstrong | \ > sed -e 's,^,+participated -- ,' | \ > notmuch tag --batch cool, thx for the suggestion. the "notmuch search" part of the pipeline alone takes ~19s (wall time, and actual CPU time) for me though :/ It returns 30504 threads! how many threads do you get? you're effectively re-tagging every single message in every participated thread every time you run "notmuch new", right? > On my database the query takes about two seconds to run, and lets me to > searches like "tag:inbox and tag:participated". The set of threads > found is typically a subset of "tag:inbox and to:marmstrong", but not > always, and I now have two canned "inbox" searches: > > "participated" -> "tag:inbox and tag:participated" > "me" -> "tag:inbox and to:marmstrong and not tag:participated" > > The "me" search tends to be new stuff, bot-generated notifications, and > such. The "participated" is typically active conversations and stuff > I've already engaged with, or initiated myself. I like this outcome! I'm just looking for a way to do it that wouldn't cost me so many cycles -- Maybe if i only run "notmuch new" once a day :) --dkg signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
Gaute Hope writes: > David Bremner writes on juni 15, 2017 22:20: >> Daniel Kahn Gillmor writes: >>> >>> One of my long-standing wishes is to be able to say "show me mails in my >>> inbox from people who have replied to messages i've sent them". >>> >>> This could be re-framed as "show me threads in which i've participated, >>> where there are some messages flagged with 'inbox'". but generating a >>> huge list of all threads in which i've participated, just to be able to >>> do an intersection operation with a (much smaller) list of all threads >>> that have a message with the inbox flag seems like a pretty gross >>> inefficiency. >> >> At the moment the best we could do is essentially the same algorithm, >> but in C instead of shell / python. Threads are not documents in the >> database, so they can't efficiently be searched for. Of course we could >> change that, but those kind of changes take a fair amount of effort, and >> some careful design work. > > There are probably multiple earlier references to this, but here's one: > > id:1471858269.x2m28lgosh.astroid@strange > > matching against the whole thread vs the individual messages would be > very useful! For what it is worth, I've found this idea from Daniel intriguing and pretty useful in practice: "show me threads in which i've participated, where there are some messages flagged with 'inbox'" I implement it like this in my post-new hook: # All messages in threads in which I participate get tag:participated notmuch search --output=threads from:marmstrong | \ sed -e 's,^,+participated -- ,' | \ notmuch tag --batch On my database the query takes about two seconds to run, and lets me to searches like "tag:inbox and tag:participated". The set of threads found is typically a subset of "tag:inbox and to:marmstrong", but not always, and I now have two canned "inbox" searches: "participated" -> "tag:inbox and tag:participated" "me" -> "tag:inbox and to:marmstrong and not tag:participated" The "me" search tends to be new stuff, bot-generated notifications, and such. The "participated" is typically active conversations and stuff I've already engaged with, or initiated myself. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
David Bremner writes on juni 15, 2017 22:20: Daniel Kahn Gillmor writes: One of my long-standing wishes is to be able to say "show me mails in my inbox from people who have replied to messages i've sent them". This could be re-framed as "show me threads in which i've participated, where there are some messages flagged with 'inbox'". but generating a huge list of all threads in which i've participated, just to be able to do an intersection operation with a (much smaller) list of all threads that have a message with the inbox flag seems like a pretty gross inefficiency. At the moment the best we could do is essentially the same algorithm, but in C instead of shell / python. Threads are not documents in the database, so they can't efficiently be searched for. Of course we could change that, but those kind of changes take a fair amount of effort, and some careful design work. There are probably multiple earlier references to this, but here's one: id:1471858269.x2m28lgosh.astroid@strange matching against the whole thread vs the individual messages would be very useful! Regards, Gaute ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
David Bremner writes: > Daniel Kahn Gillmor writes: > >> >> One of my long-standing wishes is to be able to say "show me mails in my >> inbox from people who have replied to messages i've sent them". >> >> This could be re-framed as "show me threads in which i've participated, >> where there are some messages flagged with 'inbox'". but generating a >> huge list of all threads in which i've participated, just to be able to >> do an intersection operation with a (much smaller) list of all threads >> that have a message with the inbox flag seems like a pretty gross >> inefficiency. > > At the moment the best we could do is essentially the same algorithm, > but in C instead of shell / python. Threads are not documents in the > database, so they can't efficiently be searched for. Of course we could > change that, but those kind of changes take a fair amount of effort, and > some careful design work. Even if the C level does the same algorithm, it may be able to do some optimizations on behalf of the "scripting layer" queries. I suspect that a separate "thread based" query language may be an interesting area of investigation. Taking Daniel's last example, "show me mails in my inbox from people who have replied to messages I've sent them". That isn't even an entirely unambiguous query specification. What is *actually* desired: a) show me messages from X that are part of threads where at least one message is in the inbox and for which at least one message is from me. or, b) same as (a) but the "message from X" must be in the inbox (not just any other message in the thread) or, c) same as (a) or (b) but the "message from X" is a reply (e.g. dated after, or in-reply-to) a message from me. or, d) same as (c) but "message from X" is "unread", etc. Like David's 'comm -12 A B' solution, these pretty quickly start looking like multi-pass, or structed/nested, queries. They are a lot more like relational database queries (SQL) than the single-pass, flat (NoSQL) queries we typically use with notmuch. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
Daniel Kahn Gillmor writes: > > One of my long-standing wishes is to be able to say "show me mails in my > inbox from people who have replied to messages i've sent them". > > This could be re-framed as "show me threads in which i've participated, > where there are some messages flagged with 'inbox'". but generating a > huge list of all threads in which i've participated, just to be able to > do an intersection operation with a (much smaller) list of all threads > that have a message with the inbox flag seems like a pretty gross > inefficiency. At the moment the best we could do is essentially the same algorithm, but in C instead of shell / python. Threads are not documents in the database, so they can't efficiently be searched for. Of course we could change that, but those kind of changes take a fair amount of effort, and some careful design work. d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
On Tue 2017-06-13 20:31:19 -0300, David Bremner wrote: > Xu Wang writes: > >> I bump this. Actually more simple than that, how to search for thread >> in which I have participated and Jian has participated? Excluding >> threads in which Dave participated is perhaps more complicated. > > I don't know of an efficient way to do this. You could write a script > something like > > notmuch search --output=threads from:Xu > A > notmuch search --output=threads from:Jian > B > comm -12 A B > > I think the output is sorted, but you might also have to sort A and B that said, it'd be really nice to have something like this in notmuch core. One of my long-standing wishes is to be able to say "show me mails in my inbox from people who have replied to messages i've sent them". This could be re-framed as "show me threads in which i've participated, where there are some messages flagged with 'inbox'". but generating a huge list of all threads in which i've participated, just to be able to do an intersection operation with a (much smaller) list of all threads that have a message with the inbox flag seems like a pretty gross inefficiency. --dkg signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
David Bremner writes: > Xu Wang writes: > >> I bump this. Actually more simple than that, how to search for thread >> in which I have participated and Jian has participated? Excluding >> threads in which Dave participated is perhaps more complicated. > > I don't know of an efficient way to do this. You could write a script > something like > > notmuch search --output=threads from:Xu > A > notmuch search --output=threads from:Jian > B > comm -12 A B > > I think the output is sorted, but you might also have to sort A and B I did test that part before posting mine, and the output is inverted. --sort=oldest-first *also* gets it wrong, though in more subtle ways. Piping through `sort -u` is the only way to be sure (I can't imagine the -u helping, but I also can't imagine it hurting and it's cheap). ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
ooo that is nice also. I will look into that. I think it is a good approach. Kind regards to everyone! Xu On Tue, Jun 13, 2017 at 7:31 PM, David Bremner wrote: > Xu Wang writes: > >> I bump this. Actually more simple than that, how to search for thread >> in which I have participated and Jian has participated? Excluding >> threads in which Dave participated is perhaps more complicated. > > I don't know of an efficient way to do this. You could write a script > something like > > notmuch search --output=threads from:Xu > A > notmuch search --output=threads from:Jian > B > comm -12 A B > > I think the output is sorted, but you might also have to sort A and B > ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
Xu Wang writes: > I bump this. Actually more simple than that, how to search for thread > in which I have participated and Jian has participated? Excluding > threads in which Dave participated is perhaps more complicated. I don't know of an efficient way to do this. You could write a script something like notmuch search --output=threads from:Xu > A notmuch search --output=threads from:Jian > B comm -12 A B I think the output is sorted, but you might also have to sort A and B ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: find threads where I and Jian participated but not Dave
I bump this. Actually more simple than that, how to search for thread in which I have participated and Jian has participated? Excluding threads in which Dave participated is perhaps more complicated. kind regards, Xu On Sat, Jan 9, 2016 at 4:55 PM, Xu Wang wrote: > Has someone a notmuch-based script by which to search for threads in > which I have participated and Jian has participated, but Dave has not > participated? > > Kind regards, > > Xu ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
find threads where I and Jian participated but not Dave
Has someone a notmuch-based script by which to search for threads in which I have participated and Jian has participated, but Dave has not participated? Kind regards, Xu ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
