Log of tagging actions
> I use a C wrapper to do the same (with date prefixes like 2014-05-09 > (Fri) 12:47:19) -- I originally did it to do argument conversions > around .. to have date-based searches before those came to notmuch > (and I am still using it, as I don't have to type date: prefix) Having a wrapper script possible, however, it is quite a hack and doesn't potentially collect everything. There's already a .notmuch-config file, so adding a logging directive should be straightforward. It's more about whether something like this becomes part of notmuch directly. >> Would be nice to be able to log all operations done via libnotmuch >> too though. > > IIRC someone suggested/asked whether we'd get logs where all > Message-ID:s affected were logged. That could be useful (and produce > lot of log when one does notmuch tag +foobar '*') I'm not worried about the size of the logfiles. Drives are large and many utilities exist to create a rolling removal and compression of log files. Sebastian
Re: Log of tagging actions
> I use a C wrapper to do the same (with date prefixes like 2014-05-09 > (Fri) 12:47:19) -- I originally did it to do argument conversions > around .. to have date-based searches before those came to notmuch > (and I am still using it, as I don't have to type date: prefix) Having a wrapper script possible, however, it is quite a hack and doesn't potentially collect everything. There's already a .notmuch-config file, so adding a logging directive should be straightforward. It's more about whether something like this becomes part of notmuch directly. >> Would be nice to be able to log all operations done via libnotmuch >> too though. > > IIRC someone suggested/asked whether we'd get logs where all > Message-ID:s affected were logged. That could be useful (and produce > lot of log when one does notmuch tag +foobar '*') I'm not worried about the size of the logfiles. Drives are large and many utilities exist to create a rolling removal and compression of log files. Sebastian ___ notmuch mailing list [email protected] http://notmuchmail.org/mailman/listinfo/notmuch
Log of tagging actions
On Fri, May 09 2014, Istvan Marko wrote: > Sebastian Fischmeister writes: > >> Is there a possibility to log all tagging actions done in notmuch? > > I use a shell wrapper around notmuch to get this: > > #! /bin/sh > echo "notmuch $@" >>$HOME/logs/notmuch.log > /usr/local/bin/notmuch "$@" You could make the last line 'exec /usr/local/bin/notmuch "$@"' :D (and if you use debian, #!/bin/dash...) I use a C wrapper to do the same (with date prefixes like 2014-05-09 (Fri) 12:47:19) -- I originally did it to do argument conversions around .. to have date-based searches before those came to notmuch (and I am still using it, as I don't have to type date: prefix) > Would be nice to be able to log all operations done via libnotmuch too > though. IIRC someone suggested/asked whether we'd get logs where all Message-ID:s affected were logged. That could be useful (and produce lot of log when one does notmuch tag +foobar '*') That means to do logging with this granularity may prove problematic... > -- > Istvan Tomi
Re: Log of tagging actions
On Fri, May 09 2014, Istvan Marko wrote: > Sebastian Fischmeister writes: > >> Is there a possibility to log all tagging actions done in notmuch? > > I use a shell wrapper around notmuch to get this: > > #! /bin/sh > echo "notmuch $@" >>$HOME/logs/notmuch.log > /usr/local/bin/notmuch "$@" You could make the last line 'exec /usr/local/bin/notmuch "$@"' :D (and if you use debian, #!/bin/dash...) I use a C wrapper to do the same (with date prefixes like 2014-05-09 (Fri) 12:47:19) -- I originally did it to do argument conversions around .. to have date-based searches before those came to notmuch (and I am still using it, as I don't have to type date: prefix) > Would be nice to be able to log all operations done via libnotmuch too > though. IIRC someone suggested/asked whether we'd get logs where all Message-ID:s affected were logged. That could be useful (and produce lot of log when one does notmuch tag +foobar '*') That means to do logging with this granularity may prove problematic... > -- > Istvan Tomi ___ notmuch mailing list [email protected] http://notmuchmail.org/mailman/listinfo/notmuch
Re: Log of tagging actions
Sebastian Fischmeister writes: > Is there a possibility to log all tagging actions done in notmuch? I use a shell wrapper around notmuch to get this: #! /bin/sh echo "notmuch $@" >>$HOME/logs/notmuch.log /usr/local/bin/notmuch "$@" Would be nice to be able to log all operations done via libnotmuch too though. -- Istvan ___ notmuch mailing list [email protected] http://notmuchmail.org/mailman/listinfo/notmuch
Log of tagging actions
Sebastian Fischmeister writes: > Is there a possibility to log all tagging actions done in notmuch? I use a shell wrapper around notmuch to get this: #! /bin/sh echo "notmuch $@" >>$HOME/logs/notmuch.log /usr/local/bin/notmuch "$@" Would be nice to be able to log all operations done via libnotmuch too though. -- Istvan
Log of tagging actions
Hi, The amazing thing about the notmuch emacs interface is that with just a couple of keystrokes you can quickly manipulate a lot of emails and thus be very efficient. The big disadvantage is that with just a couple of keystrokes you can manipulate a lot of emails and thus quickly completely mess up your emails. Just think about the scenario of a cat wandering across your keyboard. Is there a possibility to log all tagging actions done in notmuch? Something like: , , It would be helpful for restoring things in case something went wrong, and it could be the start of an undo function. Sebastian
Log of tagging actions
Hi, The amazing thing about the notmuch emacs interface is that with just a couple of keystrokes you can quickly manipulate a lot of emails and thus be very efficient. The big disadvantage is that with just a couple of keystrokes you can manipulate a lot of emails and thus quickly completely mess up your emails. Just think about the scenario of a cat wandering across your keyboard. Is there a possibility to log all tagging actions done in notmuch? Something like: , , It would be helpful for restoring things in case something went wrong, and it could be the start of an undo function. Sebastian ___ notmuch mailing list [email protected] http://notmuchmail.org/mailman/listinfo/notmuch
