From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=0.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,RCVD_IN_DNSWL_HI,RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=no autolearn_force=no version=3.4.6 Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id D6E4C1F628 for ; Mon, 13 Feb 2023 16:06:41 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=lpl7S74O; dkim-atps=neutral Received: by mail-ej1-x632.google.com with SMTP id k16so1553296ejv.10 for ; Mon, 13 Feb 2023 08:06:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :from:to:cc:subject:date:message-id:reply-to; bh=n5MLWeU25TFreOr4edswHTWKYmM+pfPWPmrHyAPClAo=; b=lpl7S74OQhh7K4YKVdLygRf22HpFz+MHInT4QbV0yw+Yv2CnsbgWI1ZhavW0x1iMhL vRCLGUCHMd03ZWyLIgHhncbl/KPeLqbw8mQ5UF75X3okFxyTJ4KueF87TRQNi0troDGk h7XQeBZ6olAVe/eNLb+/UX+HxpVvc3SpGb3waReu5i7fDG3vzklVGH0/D4J3VOwgZjd1 y9iWhsK4rtH/ys5v2kAOnElS2RYOXgsNCcpWjVZMrShUS1u3tW8n/u2eiiCb5Sba7JyM LeExrTSClm2w8cW78Bq2SNqE2egAbodj7o/WwzX25KsyzAkObpZ2YSK6jsyhqT+Zo3JY bMRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-disposition:mime-version:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=n5MLWeU25TFreOr4edswHTWKYmM+pfPWPmrHyAPClAo=; b=Enk7PRquvna/74c1xt6yJWmJmNoArmeCIX4yrZZ9cXE6tk7wyaEchY1mSjHZJNPc/S d+ecNL6NKuGzxnNKfmM3171lHIyVmz9zJadZ4uX01etJvSQFhrCfu4rPDL60FhWp8vGa ryw27OwQ0Y9/vZ5svPUWn3E0S0g7S2SzH7TLSwgIJoTHum3GdfrPXwn+gctAJqsSyw0g z6pqhlem/RYfY1rTtct+Wp8sl2Kz3krEMxl9OBFpCnZvhPtyI5bT1vNYzFHpj+mKgTH1 13snLWoakI8dY+U/Ya47O+wtSDmUavJs/UAxfOxCWWMC1Ym+XCEmn4DNh1IgrGfgwFxe o9sQ== X-Gm-Message-State: AO0yUKVhBosrjgtPui0FpzQuyWBqkwxbzXuTO5Elta5W3F2VC7eFHtCL MdW4ND3KTmcAKyaUw8wxEFaYqGpqpgrPsQ== X-Google-Smtp-Source: AK7set88EayYBVmkPuF8Pf81jn2NLNV6D4eYJCWaI01bN/6Lx9MJ/j9C9q0KMQ1E//ZAU7etWzKixQ== X-Received: by 2002:a17:907:720b:b0:8b0:26b6:3f2b with SMTP id dr11-20020a170907720b00b008b026b63f2bmr11569490ejc.53.1676304399648; Mon, 13 Feb 2023 08:06:39 -0800 (PST) Received: from localhost ([23.154.177.6]) by smtp.gmail.com with ESMTPSA id k7-20020a17090666c700b0088e5f3e1faesm6928776ejp.36.2023.02.13.08.06.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Feb 2023 08:06:39 -0800 (PST) Date: Mon, 13 Feb 2023 18:06:30 +0200 From: Maxim Mikityanskiy To: meta@public-inbox.org Cc: Eric Wong , Kyle Meyer Subject: lei q -tt doesn't work properly? Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: Hello, I'm trying to use the -tt flag to download the whole thread, but mark the actual matching emails as important. I'm not sure if I'm doing it incorrectly, or maybe there is a bug in lei. According to the man page: --cut-- -t Return all messages in the same thread as the actual match(es). Using this twice ("-tt") sets the "flagged" (AKA "important") on messages which were actual matches. This is useful to distinguish messages which were direct hits from messages which were merely part of the same thread. --cut-- I'm using this command, for example: lei q --no-save -a -o /tmp/lei-test -I 'https://lore.kernel.org/all' \ -tt 'a:syzbot AND rt:2023-01-01..2023-01-07' What I expect to see is at least one flagged email in each thread (otherwise why would this thread by downloaded), however, instead, most of the emails are not flagged, that is, the whole threads don't have any flagged email (although they clearly have emails from syzbot, which caused the match). Occasionally, some emails are flagged, for example, these two: https://lore.kernel.org/all/87wn621hmp.fsf@toke.dk/ https://lore.kernel.org/all/20230103081308.942805751@linuxfoundation.org/ It looks as if the match works correctly, but the -tt option fails to mark most of the matched emails as important, except a few that actually got marked (I couldn't find a pattern here). It's also not consistent, for example, after I removed /tmp/lei-test and restarted the lei q command, I got many more important emails, almost in each thread, but there were still threads without flagged emails. I'm checking the flags with mutt. Does anyone know what could be the reason for such behavior? Thanks, Max