From: jeremybobbin <jeremybobbin@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Deleting mseq selections
Date: Thu, 13 Aug 2020 13:19:58 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-182@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
New issue by jeremybobbin on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/182
Description:
Say I delete the selected thread from my inbox:
```sh
mseq -r .= | grep "Inbox" | mflag -S | xargs rm
```
After doing this, the thread will remain in `$MAILSEQ`, so I need to either "re-index" my mail and their threads:
```sh
full_thread() {
tmp="$(mktemp)"
mdirs "$@" | xargs mlist | mthread | tee "$threads" | MAILSEQ="$tmp" mseq -S >/dev/null
grep -nFf "$patterns" "$threads" | sed 's/:.*/=/' | MAILSEQ="$tmp" xargs -n1 mseq | awk '!x[$0]++'
}
mlist -s ~/.mail/*/Inbox | full_thread ~/.mail/ | mseq -S && mseq -C $
```
Or, I'd need to remove the selection from `$MAILSEQ`:
```sh
thread=$(mktemp)
old=$(mktemp)
mseq .= > "$thread"
cp "${MBLAZE:-$HOME/.mblaze}/seq" "$old"
grep -vFf "$thread" "$old" | mseq -S
```
I was curious as to whether you had any ideas on how do any of these things more effectively,
as well as your thoughts on an "invert matches" option like `grep`'s `-v`.
Thanks
next reply other threads:[~2020-08-13 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 11:19 jeremybobbin [this message]
2020-08-13 13:50 ` leahneukirchen
2020-08-13 16:55 ` Anachron
2020-08-13 16:55 ` Anachron
2020-08-13 17:08 ` Anachron
2020-08-13 17:23 ` jeremybobbin
2020-08-13 17:40 ` leahneukirchen
2020-08-13 19:33 ` jeremybobbin
2020-08-13 20:08 ` leahneukirchen
2020-08-14 0:56 ` jeremybobbin
2020-08-14 13:44 ` leahneukirchen
2020-08-15 13:04 ` [ISSUE] [CLOSED] " jeremybobbin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-182@inbox.vuxu.org \
--to=jeremybobbin@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).