unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Ian <saturns_rings@protonmail.com>
To: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: [BUG] Minor: config list adds a semi-colon to lists with a single item until set
Date: Tue, 14 Nov 2017 16:17:56 -0500	[thread overview]
Message-ID: <6O3LTUhoXlrnkPWCtPJCP4cagU7mFVEdyTpcC_37BoSzStlARXDBa7oczy6hB0jyjGjBQvgj_jFV58cw0aNx-jUg1h1O-FQ7820k68C0X4M=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 837 bytes --]

It seems on first config some settings are listed by "config list" with a semicolon suffix even if they are a single item. If they are subsequently set to another/the same single value they will then appear in config list WITHOUT the semicolon suffix. See output below. This is a very minor inconsistency but has affected one downstream script: [https://github.com/mturquette/ghar-email/issues/6.](https://github.com/mturquette/ghar-email/issues/6)

---------------------------------------

$ notmuch config list
...
search.exclude_tags=spam

;

<-- Semi-colon
...
$ notmuch config get search.exclude_tags
spam
$ notmuch config

set

search.exclude_tags spam
$ notmuch config get search.exclude_tags
spam
$ notmuch config list
...
search.exclude_tags=spam                        <-- No semi-colon

---------------------------------------

[-- Attachment #2: Type: text/html, Size: 1023 bytes --]

             reply	other threads:[~2017-11-14 21:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 21:17 Ian [this message]
2017-11-18 20:13 ` [BUG] Minor: config list adds a semi-colon to lists with a single item until set David Bremner
2022-01-17 23:54 ` [PATCH 1/2] test/setup: add known broken test for single items David Bremner
2022-01-17 23:54   ` [PATCH 2/2] CLI/setup: special case single item lists David Bremner
2022-01-24 13:35     ` David Bremner
2022-01-24 13:37 ` [BUG] Minor: config list adds a semi-colon to lists with a single item until set David Bremner
2022-03-31  9:14   ` Ian

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='6O3LTUhoXlrnkPWCtPJCP4cagU7mFVEdyTpcC_37BoSzStlARXDBa7oczy6hB0jyjGjBQvgj_jFV58cw0aNx-jUg1h1O-FQ7820k68C0X4M=@protonmail.com' \
    --to=saturns_rings@protonmail.com \
    --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).