user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: meta@public-inbox.org
Subject: Re: MH & thread support
Date: Thu, 06 Jan 2022 20:40:09 -0500	[thread overview]
Message-ID: <877dbc5nnq.fsf@kyleam.com> (raw)
In-Reply-To: <20220106101020.09638bd8@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>

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"
  ]

  reply	other threads:[~2022-01-07  1:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 18:10 MH & thread support Jakub Kicinski
2022-01-07  1:40 ` Kyle Meyer [this message]
2022-01-07  2:22   ` Jakub Kicinski
2022-02-01  9:51   ` Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877dbc5nnq.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=kuba@kernel.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).