On Tue, May 21 2019, Daniel Kahn Gillmor wrote: > Hi Tomi-- > > On Tue 2019-05-21 09:12:12 +0300, Tomi Ollila wrote: >> This looks like a good read: >> https://ftp.gnu.org/old-gnu/Manuals/gdb/html_node/gdb_21.html >> and is used to speculate below. > > Thanks for this pointer, and for the additional analysis. > > While i understand this problem much better than i did two days ago, i'm > not sure whether there is an alternate proposal here for how to handle > the situation. Do you have a suggestion for some other fix? I hope id:20190521201702.28754-1-tomi.ollila@iki.fi works Tomi > > It's tempting to remove the "controlling terminal" from the test suite > entirely (e.g. by running it under "setsid --wait"), but i'm reluctant > to do so because that is not the context in which most instances of > notmuch will themselves be run, and i don't really want the test suite > to be so alienated. Every test script itself, if not already setsid(1)ed would need to re-exec itself w/ that, then. (as I can now run e.g. ./T380-atomicity.sh directly from command line) > > So i'm unsure what to do, but i do want to try to move on beyond all > this "testing the test suite" and start getting more e-mail-related > features into notmuch again :P > > --dkg _______________________________________________ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch