Re: segfault using python bindings
On Fri, Aug 23 2019, Daniel Kahn Gillmor wrote: > that matches my understanding too. i'd love to move forward with the > improved bindings, under a different name. > > if someone later figures out the compatibility layer that allows > implementation of the traditional "notmuch" module api atop the > notmuch2(?) module, then we can always reclaim the name. It would be shame if after this deprecation of the original "notmuch" bindings we're left unable to "import notmuch" to get the notmuch bindings. jamie. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: segfault using python bindings
On Fri 2019-08-23 09:07:12 -0300, David Bremner wrote: > Daniel Kahn Gillmor writes: > >> The other possibility would be to implement the old "notmuch" API on top >> of the new one with explicitly logged deprecations. But iirc, the >> semantics and object lifecycle/ownership issues are subtly different >> enough that this would be a non-trivial project. I'd be happy to be >> wrong though, perhaps someone closer to the systems (someone actively >> using the current python bindings on an ongoing project?) could look >> more closely? > > IIUC, it is precisely this compatibility layer that has stalled things > for a year or so. I don't think we can afford to wait longer. that matches my understanding too. i'd love to move forward with the improved bindings, under a different name. if someone later figures out the compatibility layer that allows implementation of the traditional "notmuch" module api atop the notmuch2(?) module, then we can always reclaim the name. --dkg signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: Threaded view would do annoying scroll
Hi David, Actually, I've had Emacs session running for a couple of weeks where I've been also hacking some elisp code - I guess I've changed something and forgot about that. Your comment prompted me to try obvious approach - to dissect my init.el file and, at the end, simple Emacs restart solved the problem. Thanks and apologies for the noise. Best regards, Sanel David Bremner writes: > Sanel Zukan writes: > >> Hi, >> >> I'm using Emacs 26.2 and Notmuch 0.28.2 and I noticed that after >> updating Emacs to 26.2, notmuch would start doing annoying (auto)scroll >> inside thraded view opened message, probably trying to center the >> message. The search is done calling `notmuch-search`. >> >> Anyone got similar behavior or knows how to mitigate it? Notmuch would >> work fine in Emacs 24.3.1. >> > > I haven't noticed anything like this in emacs 26.1. Can you give us a > recipe to reproduce the problem, e.g. with a thread from the notmuch > mailing list? > > d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: segfault using python bindings
Daniel Kahn Gillmor writes: > The other possibility would be to implement the old "notmuch" API on top > of the new one with explicitly logged deprecations. But iirc, the > semantics and object lifecycle/ownership issues are subtly different > enough that this would be a non-trivial project. I'd be happy to be > wrong though, perhaps someone closer to the systems (someone actively > using the current python bindings on an ongoing project?) could look > more closely? IIUC, it is precisely this compatibility layer that has stalled things for a year or so. I don't think we can afford to wait longer. d ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
