Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread Ralph Seichter
* Daniel Kahn Gillmor: > as far as maildir goes, i think notmuch probably *shouldn't* be > looking at stuff in …/tmp/ -- right? You're right, I don't see why Notmuch would peek into "tmp". > I'd be sad if those files went away, but perhaps you're right that > we should only be looking at are

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread Ralph Seichter
* David Bremner: > So the leading '/' isn't there to match for top level files. That's unexpected, so quite in tune with the thread subject. ;-) > ignore=/(^|/)dovecot[-.]/;/(maildirfolder|subscriptions)$/; I'll try that, thanks. -Ralph ___ notmuch

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread David Bremner
Daniel Kahn Gillmor writes: > I've personally done the (maybe bad) thing where i just drop a folder > full of RFC5322 .eml files anywhere inside my message store and run > "notmuch new" to ingest them. I'd be sad if those files went away, but > perhaps you're right that we should only be

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread Daniel Kahn Gillmor
On Fri 2019-04-19 15:55:27 +0200, Ralph Seichter wrote: > * Daniel Kahn Gillmor: > >> Why is "non-mail file found" in my maildir such a low priority? > > Because I do not agree with Notmuch's notion of what a non-mail file > is. All files the Dovecot server uses for its own metadata are placed >

[PATCH] python: support relative path in default database

2019-04-19 Thread Doan Tran Cong Danh
>From notmuch 0.28, notmuch support relative database path in notmuch-config(1), but python binding haven't taught this yet. afew denied to work with a perfectly fine notmuch-config due to this. --- bindings/python/notmuch/database.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-)

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread David Bremner
Ralph Seichter writes: > * Ralph Seichter: > >> ignore=//dovecot[[:punct:]]/;/(maildirfolder|subscriptions)$/; > > Odd. I am currently adding this entry to some users' config files, and > the expression //dovecot[[:punct:]]/ does not seem to work in all > cases. Based on notmuch-search-terms(7)

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread Ralph Seichter
* Daniel Kahn Gillmor: > Why is "non-mail file found" in my maildir such a low priority? Because I do not agree with Notmuch's notion of what a non-mail file is. All files the Dovecot server uses for its own metadata are placed outside of "cur", "new", and "tmp". My understanding of the Maildir

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread Daniel Kahn Gillmor
On Thu 2019-04-18 15:52:19 +0200, Ralph Seichter wrote: > Personally, I'd go with these decreasing levels of severity: > > Fatal: Execution must stop immediately to prevent damage, error > message may or may not be displayed before exiting the process. > > Error: Serious trouble, program may

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread Ralph Seichter
* Ralph Seichter: > ignore=//dovecot[[:punct:]]/;/(maildirfolder|subscriptions)$/; Odd. I am currently adding this entry to some users' config files, and the expression //dovecot[[:punct:]]/ does not seem to work in all cases. Based on notmuch-search-terms(7) I assumed that Notmuch used POSIX.2

Re: Unexpected output of "notmuch new --quiet"

2019-04-19 Thread Ralph Seichter
* David Bremner: > Are there warnings that you want to suppress that are not handleable > with the new.ignore facility? Sorry, I misunderstood your question, and new.ignore is sufficient for my current purposes: [new] ignore=//dovecot[[:punct:]]/;/(maildirfolder|subscriptions)$/; Thank you