<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/test/T050-new.sh, branch 0.35</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.35</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.35'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2022-01-16T14:52:13Z</updated>
<entry>
<title>cli/new: only ignore .notmuch at top level</title>
<updated>2022-01-16T14:52:13Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-12-26T12:24:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=6472dbf4b7fdec3bd59d7622ef477a035e34c67a'/>
<id>urn:sha1:6472dbf4b7fdec3bd59d7622ef477a035e34c67a</id>
<content type='text'>
Since the bug was first reported in [1], notmuch has gained the
ability to have the database located outside the mail root, hence this
this change differs slightly from Jani's proposed solution [2] in not
using notmuch_database_get_path, but rather the already retrieved
mail_root.

[1]: id:87mwhifu9a.fsf@trouble.defaultvalue.org
[2]: id:87ios5v59p.fsf@nikula.org
</content>
</entry>
<entry>
<title>test: add known broken test for ignoring non-toplevel .notmuch</title>
<updated>2022-01-16T14:47:16Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-12-26T12:24:09Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=fd6d50b38f8d8529191f6c9b637ecb458018baa3'/>
<id>urn:sha1:fd6d50b38f8d8529191f6c9b637ecb458018baa3</id>
<content type='text'>
In [1] Rob observed that notmuch new ignored directories called
.notmuch everywhere in the tree, where they should only (and now, with
split configs, at most) be ignored at the top level. Add a test to
demonstrate the problem.

[1]: id:87mwhifu9a.fsf@trouble.defaultvalue.org
</content>
</entry>
<entry>
<title>test/new: replace use of gdb in vanishing file test</title>
<updated>2021-12-04T16:36:08Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-10-25T01:15:15Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=efa7f35d4a28bd8af20cc5dee3195dc8f2d142bc'/>
<id>urn:sha1:efa7f35d4a28bd8af20cc5dee3195dc8f2d142bc</id>
<content type='text'>
Unlike the similar change in T060-new, no symlink creation is needed
here.
</content>
</entry>
<entry>
<title>config: ignore leading/trailing spaces in ';'-delimited lists</title>
<updated>2021-12-04T16:16:12Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-09-30T17:17:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=bab633d3ac87167dc214094f9d340655885a01b1'/>
<id>urn:sha1:bab633d3ac87167dc214094f9d340655885a01b1</id>
<content type='text'>
In [1] Ciprian observed that it was easy for users to mistakenly
introduce leading and trailing space to new.tags when editing a
notmuch config file. This commit strips spaces on either side of the
';' delimiter when splitting.

In principle it would be possible to support tags (or other config
values) with leading or trailing spaces by processing '\s' escapes in
the input string. Currently such processing is not done.

[1]: id:CA+Tk8fzjPLaEd3vL1f9ebk_bF_RV8PDTLzDupraTkCLCpJAmCg@mail.gmail.com
</content>
</entry>
<entry>
<title>test: known broken tests for leading/trailing ws in config</title>
<updated>2021-12-04T16:15:49Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-09-30T17:17:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e22bbb124e4f9191880e80d6517346f35bf7e2a9'/>
<id>urn:sha1:e22bbb124e4f9191880e80d6517346f35bf7e2a9</id>
<content type='text'>
These tests duplicate the bug/misfeature reported in

      id:CA+Tk8fzjPLaEd3vL1f9ebk_bF_RV8PDTLzDupraTkCLCpJAmCg@mail.gmail.com
</content>
</entry>
<entry>
<title>test: add known broken test for indexing RFC822 group names</title>
<updated>2021-06-05T18:31:03Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-03-24T00:24:05Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=2c85cc29bd8c29792acacc65cf9c5810d7f4791e'/>
<id>urn:sha1:2c85cc29bd8c29792acacc65cf9c5810d7f4791e</id>
<content type='text'>
Austin Clements diagnosed this indexing problem in [1].

[1]: id:20130711215207.GR2214@mit.edu
</content>
</entry>
<entry>
<title>lib/config: expand relative paths when reading from database</title>
<updated>2021-05-10T14:12:58Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-05-07T10:27:37Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=1040e7aa077197e5295180ef54576ea39c298a36'/>
<id>urn:sha1:1040e7aa077197e5295180ef54576ea39c298a36</id>
<content type='text'>
This makes the treatment of relative paths consistent between the
database and config files.
</content>
</entry>
<entry>
<title>test: add known broken test for relative setting of mail_root</title>
<updated>2021-05-10T14:11:42Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-05-07T10:17:43Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=322a492c77725b265cb7f5c1d0bed5dee6999743'/>
<id>urn:sha1:322a492c77725b265cb7f5c1d0bed5dee6999743</id>
<content type='text'>
The behaviour should not change depending on where the configuration
is stored.
</content>
</entry>
<entry>
<title>lib/config: canonicalize paths relative to $HOME.</title>
<updated>2021-05-10T14:08:18Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-05-07T00:16:38Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=31098c4ae40511ffda9788a6654adbf898063d7f'/>
<id>urn:sha1:31098c4ae40511ffda9788a6654adbf898063d7f</id>
<content type='text'>
Prior to 0.32, notmuch had the (undocumented) behaviour that it
expanded a relative value of database.path with respect to $HOME. In
0.32 this was special cased for database.path but broken for
database.mail_root, which causes problems for at least notmuch-new
when database.path is set to a relative path.

The change in T030-config.sh reflects a user visible, but hopefully
harmless behaviour change; the expanded form of the paths will now be
printed by notmuch config.
</content>
</entry>
<entry>
<title>test: add known broken test for relative database path in new</title>
<updated>2021-05-10T14:06:40Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2021-05-06T22:55:07Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ef0b1266190141b108a338ba06348e335ec4957b'/>
<id>urn:sha1:ef0b1266190141b108a338ba06348e335ec4957b</id>
<content type='text'>
This test highlights a bug introduced in 0.32. The new split between
path and mail_root does not properly canonicalize relative paths in
the latter.
</content>
</entry>
</feed>
