From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kyle@kyleam.com>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS16276 91.121.0.0/16
X-Spam-Status: No, score=-3.7 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_HELO_NONE,
	SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from out1.migadu.com (out1.migadu.com [91.121.223.63])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 701FC1F953
	for <meta@public-inbox.org>; Fri,  7 Jan 2022 01:40:13 +0000 (UTC)
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1;
	t=1641519610;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=L3p3Xs0k0JqkZa/TG6qQgQybj859kkG32P/HhA7S1rg=;
	b=cmDsOQHzw/baWNYtPct7VAVVxbTWXgXumrqw8QNLkqcl3HThupnDBRoCLVYxBsAu15IeIH
	YclDsEDpgEYdyONH0wTugxHj+iU0oAwblWZtlWzQ8Y7yL2lkLYbWDkE3IoxYmAVLx6+Npx
	P/KBk9DTyu24Vknj6PrKuX2POpKQg19xjNQSOPvWcyqNQJ/t3rtxE3+VeSuA5/SeFgBw11
	ZsFo9nz2HXu1SVLopxxv0SfXLQzsmhxG6DOn+30K8EeqE+bufjtXLMTl+9fi1ROYMoNnEe
	q3PM0LT9mu8EYMDOiJeUlzvWvQYrD+23QAuZXQnq2M/+MQNpJqFkOamOCDytzw==
From: Kyle Meyer <kyle@kyleam.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: meta@public-inbox.org
Subject: Re: MH & thread support
In-Reply-To: <20220106101020.09638bd8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
References: <20220106101020.09638bd8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Thu, 06 Jan 2022 20:40:09 -0500
Message-ID: <877dbc5nnq.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Migadu-Flow: FLOW_OUT
X-Migadu-Auth-User: kyleam.com
List-Id: <meta.public-inbox.org>

Jakub Kicinski writes:

> Hi!
>
> Two questions:
>
>  - how do the plans for MH email format support look? It'd be great to
>    fetch emails with lei directly to claws-mail (which seems to be used
>    by a number of kernel devs, at least)

I don't have any informed opinions on this and don't know what Eric's
thoughts are, but fwiw this is what he wrote in lei-mail-formats(5):

  MH
         Not yet supported, locking semantics (or lack thereof) appear to make
         it unsuitable for parallel access.  It is widely-supported by a variety
         of MUAs and mailing list managers, however.

>  - is there a way to get lei to fetch a particular thread? It seems
>    like using a bare msg-id as the search term mostly works, but it 
>    also fetches in any threads which were referring to the thread of
>    interest by posting a link

You can search with the "mid:" prefix and then pull in the entire thread
with -t/--threads:

  $ lei q -f ldjson \
    mid:20211119204916.grergcuzj5gcic6c@meerkat.local | \
    jq '[.blob,.s,.f[0][0]]'
  [
    "7e49832370e95afb54298d21ea4c10d338bb3a7b",
    "RFC: should lei inject its own \"Received:\" header?",
    "Konstantin Ryabitsev"
  ]


  $ lei q -t -f ldjson \
    mid:20211119204916.grergcuzj5gcic6c@meerkat.local | \
    jq '[.blob,.s,.f[0][0]]'
  [
    "7e49832370e95afb54298d21ea4c10d338bb3a7b",
    "RFC: should lei inject its own \"Received:\" header?",
    "Konstantin Ryabitsev"
  ]
  [
    "70c49f363594e94d89a14bcb57c45d45cac49172",
    "Re: RFC: should lei inject its own \"Received:\" header?",
    "Eric Wong"
  ]