From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id C5C3D1F462; Mon, 10 Jun 2019 18:02:17 +0000 (UTC) Date: Mon, 10 Jun 2019 18:02:17 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: [PATCH 11/11] edit: new tool to perform edits Message-ID: <20190610180217.omgorucbqwjmeyua@dcvr> References: <20190609025147.24966-1-e@80x24.org> <20190609025147.24966-12-e@80x24.org> <20190610160610.GB16418@chatter.i7.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20190610160610.GB16418@chatter.i7.local> List-Id: Konstantin Ryabitsev wrote: > A quick RFE that's beyond the scope of this work, but would be handy from > the usability perspective -- pass a search term in case multiple messages > need to be edited. E.g.: > > public-inbox-edit -s "johndoe@example.com" INBOX_DIR > > The way I see it working, that would: > > 1. find all matching messages and put them into an mbox file > 2. fire off "mutt -f" to start the editing session > 3. do a batch replace of all messages in the edited mbox file The UI perspective could get a little hairy; especially with mutt not purging messages from mboxes by default. Or at least I was missing prompts while testing this. I noticed one more small bug w.r.t Status/Content-Length/Lines header changes from mutt causing no-op changes to get missed which I can fix quick; but I need to deal with a bug problem of the insect variety today :<