Hello, On Mon 06 May 2019 at 05:35PM -04, Daniel Kahn Gillmor wrote:
> notmuch-{import-patch,extract-patch,slurpdebbug} could all be "notmuch" > subcommands, similar to the way that notmuch-emacs-mua is. their > configuration could also be stored in notmuch's own configuration, > rather than in ~/.config/mailscripts. that would make them nicer for > folks already using notmuch. (and for folks not using notmuch, those > tools aren't very useful ;) ) > > Making this a tighter integration would mean maybe fixing up "notmuch > help" (so that it learns about any installed subcommand extensions and > at least tries their manual pages), and maybe fixing the notmuch bash > tab completion as well. Could you explain how this would be beneficial? I don't really see what's gained. > also, it's not clear whether the configuration should be stored in the > config file for notmuch, or in the database. I still believe we should > be getting rid of the config file if possible and storing most config in > the database, so i'd prefer to not store anything in the config file. As an aside, I hope this does not happen. I consider my notmuch database just a cache; I do not store any nonreproducible data in it. I hope this usecase will continue to be supported. -- Sean Whitton
signature.asc
Description: PGP signature