unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
To: notmuch@notmuchmail.org
Subject: [BUG] Putting "tags=;" into .notmuch-config will create empty tags
Date: Sat, 22 Feb 2014 20:29:28 -0600	[thread overview]
Message-ID: <87ha7qfto7.fsf@trouble.defaultvalue.org> (raw)


In the [new] section, "tags=;" will cause notmuch to create empty tags
that are fairly hard to remove from the command line.

After some help on #bup, here's what I came up with to remove them,
though it assumes that the empty tag "+ " will always be first in dump's
output:

  notmuch dump --format=batch-tag 'tag:""' | perl -pe 's/^\+ //' \
    | notmuch restore --format=batch-tag

And note that you have to use restore, "notmuch tag --batch" doesn't
appear to accept "- " as a tag, even though dump will produce "+ ".

Hope this helps
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

             reply	other threads:[~2014-02-23  2:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  2:29 Rob Browning [this message]
2014-02-23 16:55 ` [PATCH 0/3] check new.tags for invalid tags Jani Nikula
2014-02-23 16:55   ` [PATCH 1/3] cli: export function for illegal tag checking Jani Nikula
2014-02-23 16:55   ` [PATCH 2/3] cli: make sure notmuch new and insert don't add invalid tags Jani Nikula
2014-02-23 16:55   ` [PATCH 3/3] test: add tests for invalid new.tags Jani Nikula
2014-02-23 18:21   ` [PATCH 0/3] check new.tags for invalid tags Tomi Ollila
2014-03-04 16:51     ` [PATCH] cli: add missing \n in error message Jani Nikula
2014-03-06 11:51   ` [PATCH 0/3] check new.tags for invalid tags David Bremner

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87ha7qfto7.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).