Re: GitHub + notmuch scripts/hacks

2018-06-24 Thread William Casarin
William Casarin  writes:

> I've started collecting[1] a bunch of notmuch+GitHub hacks from some of
> the discussions @ id:87d16jtsdj@kyleam.com
> [..]
>
> [1] https://github.com/jb55/notmuch-github
> [2] 
> https://github.com/jb55/notmuch-github/commit/fb2d80cf9ee9a5967c78ae6ccda866ee98cdd547
> [3] https://jb55.com/s/notmuch-github.mp4

Hey notmuch peoples,

I've started looking into possible ways to tag github pull requests and
issues. So far I've been able to put together these semi-reliable
tagging methods for pull requests:

notmuch tag +github from:github.com and tag:inbox

notmuch tag +pr '"You can view, comment on, or merge this pull request 
online at"' \
  and tag:github and not tag:pr and tag:inbox and not tag:issue

# tag all messages in the thread that have a pr tag
notmuch tag +pr $(notmuch search --output=threads tag:pr and tag:inbox)

# this seems to be a semi reliable way to find github merge emails
notmuch tag +merged Merged and event from:notificati...@github.com \
  and not tag:merged and tag:inbox and tag:pr

# tag the entire pr thread as merged
notmuch tag +merged $(notmuch search --output=threads tag:merged and 
tag:inbox)

I still haven't found a reliable way to tag issues and their closed
status. If anyone has something more reliable feel free to share here or
at https://github.com/jb55/notmuch-github#tagging

Cheers,
Will


--
https://jb55.com
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


GitHub + notmuch scripts/hacks

2017-10-13 Thread William Casarin

Hey there,

I've started collecting[1] a bunch of notmuch+GitHub hacks from some of
the discussions @ id:87d16jtsdj@kyleam.com

I've added the ability to comment on/approve/reject pull requests from a
GitHub pull-request email[2].

It can also open a magit-log view of the PR from an email, as shown in
this[3] demo video.

This is still very much a work in progress and is not very user friendly
yet. If you would like to help out and convert my hacky bash script to
elisp that would be great.

Much of this work is due to Kyle Meyer and I have been building off of it.
Thanks Kyle!

Cheers,
William


[1] https://github.com/jb55/notmuch-github
[2] 
https://github.com/jb55/notmuch-github/commit/fb2d80cf9ee9a5967c78ae6ccda866ee98cdd547
[3] https://jb55.com/s/notmuch-github.mp4


-- 
https://jb55.com
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts (again), now with more usenet

2012-12-09 Thread Jani Nikula
On Sat, 14 Jul 2012, ccx at webprojekty.cz wrote:
> Hello, for quite some time my set of scripts just lied in my repo and
> waited for polish before release. So tonight I finally managed to update
> the docs, remove old stuff, rewrite some unfortunate things etc.
>
> One notable addition is slrn2maildir script which can convert NNTP
> spool, eg. gmane mailing lists or blogs, as fetched by slrnpull to
> maildir format. This way you can follow plethora of mailing lists
> without subscribing, any blog that publishes full atom/rss feed or
> usenet newsgroup.
>
> For details see the readme:
>   http://webprojekty.cz/ccx/loggerhead/zmuch/view/head:/README
> or check out the code:
>   bzr branch http://webprojekty.cz/ccx/bzr/zmuch
>
> I hope it's now in the form acceptable for inclusion to contrib.

Hi, lacking a more appropriate tag, I have tagged this message
notmuch::stale in nmbug, the notmuch bug and patch tracking system. See
[1] and [2] for details.

If you're still interested in getting your scripts included in contrib,
please provide them in patch form. See [3] for patch submission
guidelines.

BR,
Jani.


[1] http://nmbug.tethera.net/status/
[2] http://notmuchmail.org/nmbug/
[3] http://notmuchmail.org/patchformatting/


Notmuch scripts (again), now with more usenet

2012-11-25 Thread David Bremner
Ethan Glasser-Camp  writes:
>
> If Bremner is willing to put this package in contrib, I think he should
> do so.

I guess that's fine, but I'd be more likely to get around to it if
presented with a patch against git master 

d


Re: Notmuch scripts (again), now with more usenet

2012-11-25 Thread David Bremner
Ethan Glasser-Camp ethan.glasser.c...@gmail.com writes:

 If Bremner is willing to put this package in contrib, I think he should
 do so.

I guess that's fine, but I'd be more likely to get around to it if
presented with a patch against git master 

d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts (again), now with more usenet

2012-11-18 Thread Ethan Glasser-Camp
Jan Pobrislo  writes:

> Hi! I was having some hardware issues and had to migrate the site. It should
> be all up again and ready for inclusion.
>
> Added stuff from last time:
> * source function & actions for zaw (https://github.com/zsh-users/zaw)
> * LICENSE (CC0)

Hi! Sorry for the delay, real life got in the way.

In previous emails, David Bremner said he'd like someone with Python
expertise to look at notmuch-new.py. He notes that pylint goes
ballistic, but most of these errors don't bother me much (complaints
about variable naming and missing docstrings).

As for the rest, I'm not a zsh expert, but I looked at zmuch and
notmuch-colorize and they looked fine.

If Bremner is willing to put this package in contrib, I think he should
do so.

Ethan


Re: Notmuch scripts (again), now with more usenet

2012-11-18 Thread Ethan Glasser-Camp
Jan Pobrislo c...@webprojekty.cz writes:

 Hi! I was having some hardware issues and had to migrate the site. It should
 be all up again and ready for inclusion.

 Added stuff from last time:
 * source function  actions for zaw (https://github.com/zsh-users/zaw)
 * LICENSE (CC0)

Hi! Sorry for the delay, real life got in the way.

In previous emails, David Bremner said he'd like someone with Python
expertise to look at notmuch-new.py. He notes that pylint goes
ballistic, but most of these errors don't bother me much (complaints
about variable naming and missing docstrings).

As for the rest, I'm not a zsh expert, but I looked at zmuch and
notmuch-colorize and they looked fine.

If Bremner is willing to put this package in contrib, I think he should
do so.

Ethan
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: Notmuch scripts (again), now with more usenet

2012-11-01 Thread Jan Pobrislo
On Thu, 18 Oct 2012 23:33:22 -0400, Ethan Glasser-Camp 
ethan.glasser.c...@gmail.com wrote:
 c...@webprojekty.cz writes:

  Hello, for quite some time my set of scripts just lied in my repo and
  waited for polish before release. So tonight I finally managed to update
  the docs, remove old stuff, rewrite some unfortunate things etc.
 
  One notable addition is slrn2maildir script which can convert NNTP
  spool, eg. gmane mailing lists or blogs, as fetched by slrnpull to
  maildir format. This way you can follow plethora of mailing lists
  without subscribing, any blog that publishes full atom/rss feed or
  usenet newsgroup.
 
  For details see the readme:
http://webprojekty.cz/ccx/loggerhead/zmuch/view/head:/README
  or check out the code:
bzr branch http://webprojekty.cz/ccx/bzr/zmuch
 
  I hope it's now in the form acceptable for inclusion to contrib.

 Hi! Sorry about the delay, but I'm going through the patch queue now and
 it seems like this branch is just completely gone. I get 502 Bad Gateway
 errors when I follow the first link. Did it move or is there a problem
 with your site?

 Ethan

Hi! I was having some hardware issues and had to migrate the site. It should
be all up again and ready for inclusion.

Added stuff from last time:
* source function  actions for zaw (https://github.com/zsh-users/zaw)
* LICENSE (CC0)


pgp1RSpuhdDIg.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts (again), now with more usenet

2012-10-19 Thread Ethan Glasser-Camp
ccx at webprojekty.cz writes:

> Hello, for quite some time my set of scripts just lied in my repo and
> waited for polish before release. So tonight I finally managed to update
> the docs, remove old stuff, rewrite some unfortunate things etc.
>
> One notable addition is slrn2maildir script which can convert NNTP
> spool, eg. gmane mailing lists or blogs, as fetched by slrnpull to
> maildir format. This way you can follow plethora of mailing lists
> without subscribing, any blog that publishes full atom/rss feed or
> usenet newsgroup.
>
> For details see the readme:
>   http://webprojekty.cz/ccx/loggerhead/zmuch/view/head:/README
> or check out the code:
>   bzr branch http://webprojekty.cz/ccx/bzr/zmuch
>
> I hope it's now in the form acceptable for inclusion to contrib.

Hi! Sorry about the delay, but I'm going through the patch queue now and
it seems like this branch is just completely gone. I get 502 Bad Gateway
errors when I follow the first link. Did it move or is there a problem
with your site?

Ethan


Re: Notmuch scripts (again), now with more usenet

2012-10-18 Thread Ethan Glasser-Camp
c...@webprojekty.cz writes:

 Hello, for quite some time my set of scripts just lied in my repo and
 waited for polish before release. So tonight I finally managed to update
 the docs, remove old stuff, rewrite some unfortunate things etc.

 One notable addition is slrn2maildir script which can convert NNTP
 spool, eg. gmane mailing lists or blogs, as fetched by slrnpull to
 maildir format. This way you can follow plethora of mailing lists
 without subscribing, any blog that publishes full atom/rss feed or
 usenet newsgroup.

 For details see the readme:
   http://webprojekty.cz/ccx/loggerhead/zmuch/view/head:/README
 or check out the code:
   bzr branch http://webprojekty.cz/ccx/bzr/zmuch

 I hope it's now in the form acceptable for inclusion to contrib.

Hi! Sorry about the delay, but I'm going through the patch queue now and
it seems like this branch is just completely gone. I get 502 Bad Gateway
errors when I follow the first link. Did it move or is there a problem
with your site?

Ethan
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts (again), now with more usenet

2012-07-19 Thread David Bremner
ccx at webprojekty.cz writes:

>
> I might not always have time to read the entirety of the ML, so it would
> be great if people CC me when posting there.
>

OK, please add some kind of README file explaining the best way to
report bugs.

>
> You can consider it public domain. I guess I should add wtfpl text to my
> repo. :-)

Please do. or CC0 if you prefer less swearing ;).

d


Re: Notmuch scripts (again), now with more usenet

2012-07-19 Thread David Bremner
c...@webprojekty.cz writes:


 I might not always have time to read the entirety of the ML, so it would
 be great if people CC me when posting there.


OK, please add some kind of README file explaining the best way to
report bugs.


 You can consider it public domain. I guess I should add wtfpl text to my
 repo. :-)

Please do. or CC0 if you prefer less swearing ;).

d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts (again), now with more usenet

2012-07-17 Thread c...@webprojekty.cz
On Sun, Jul 15, 2012 at 10:36:54AM -0600, David Bremner wrote:
> ccx at webprojekty.cz writes:
> 
> > I hope it's now in the form acceptable for inclusion to contrib.
> 
> Dear Jan;
> 
> Without looking too much at the details I think this is reasonable to
> include in contrib, as a set of examples if nothing else. Still, I'm
> curious about a few things. Are there actual users (other than the
> author)?  What would we do about bug reports? Will you follow the list,
> or would we explicitely tell people to contact you directly?

I might not always have time to read the entirety of the ML, so it would
be great if people CC me when posting there.

> I guess some of the python experts might want to discuss the coding
> style of notmuch-new.py. pylint goes ballistic, for whatever that is
> worth.

That's mainly because of tabs used for indentation, which used to be
considered a viable alternative, but is now considered obsolete. I
reformatted the code to conform to pep8 guidelines.

> For the shell stuff, I noticed lots of unquoted parameter expansion;
> also at some point you make a temporary directory using $$
> directly rather than using e.g. mktemp.

Zsh does not word-split parameter expansion by default, this is
intentional. The temporary directories are created in xdg cache dir,
which should not be susceptible to symlink attacks etc. and the pid
actually helps to correlate the directories to processes, eg. when you
want to autoclean after searches that got killed for some reason.

> What did you have in mind for a license? since there is no linking here,
> it does not have to be GPL3+, but some standard Free license is needed I
> think; since I'm also maintaining the Debian package, I don't want to
> have to remove your stuff before uploading to Debian.

You can consider it public domain. I guess I should add wtfpl text to my
repo. :-)

> d

Thanks very much for your rewiev.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: 



Re: Notmuch scripts (again), now with more usenet

2012-07-17 Thread ccx
On Sun, Jul 15, 2012 at 10:36:54AM -0600, David Bremner wrote:
 c...@webprojekty.cz writes:
 
  I hope it's now in the form acceptable for inclusion to contrib.
 
 Dear Jan;
 
 Without looking too much at the details I think this is reasonable to
 include in contrib, as a set of examples if nothing else. Still, I'm
 curious about a few things. Are there actual users (other than the
 author)?  What would we do about bug reports? Will you follow the list,
 or would we explicitely tell people to contact you directly?

I might not always have time to read the entirety of the ML, so it would
be great if people CC me when posting there.

 I guess some of the python experts might want to discuss the coding
 style of notmuch-new.py. pylint goes ballistic, for whatever that is
 worth.

That's mainly because of tabs used for indentation, which used to be
considered a viable alternative, but is now considered obsolete. I
reformatted the code to conform to pep8 guidelines.

 For the shell stuff, I noticed lots of unquoted parameter expansion;
 also at some point you make a temporary directory using $$
 directly rather than using e.g. mktemp.

Zsh does not word-split parameter expansion by default, this is
intentional. The temporary directories are created in xdg cache dir,
which should not be susceptible to symlink attacks etc. and the pid
actually helps to correlate the directories to processes, eg. when you
want to autoclean after searches that got killed for some reason.

 What did you have in mind for a license? since there is no linking here,
 it does not have to be GPL3+, but some standard Free license is needed I
 think; since I'm also maintaining the Debian package, I don't want to
 have to remove your stuff before uploading to Debian.

You can consider it public domain. I guess I should add wtfpl text to my
repo. :-)

 d

Thanks very much for your rewiev.


signature.asc
Description: Digital signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts (again), now with more usenet

2012-07-16 Thread Daniel Schoepe
On Sun, 15.07.2012 18:36, David Bremner wrote:
> Are there actual users (other than the author)?

I started using the slrn2maildir script yesterday, but none of the other
scripts. It's working fine so far.

Cheers,
Daniel
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: 



Notmuch scripts (again), now with more usenet

2012-07-15 Thread David Bremner
ccx at webprojekty.cz writes:

> I hope it's now in the form acceptable for inclusion to contrib.

Dear Jan;

Without looking too much at the details I think this is reasonable to
include in contrib, as a set of examples if nothing else. Still, I'm
curious about a few things. Are there actual users (other than the
author)?  What would we do about bug reports? Will you follow the list,
or would we explicitely tell people to contact you directly?

I guess some of the python experts might want to discuss the coding
style of notmuch-new.py. pylint goes ballistic, for whatever that is
worth.

For the shell stuff, I noticed lots of unquoted parameter expansion;
also at some point you make a temporary directory using $$
directly rather than using e.g. mktemp.

What did you have in mind for a license? since there is no linking here,
it does not have to be GPL3+, but some standard Free license is needed I
think; since I'm also maintaining the Debian package, I don't want to
have to remove your stuff before uploading to Debian.

d





Re: Notmuch scripts (again), now with more usenet

2012-07-15 Thread David Bremner
c...@webprojekty.cz writes:

 I hope it's now in the form acceptable for inclusion to contrib.

Dear Jan;

Without looking too much at the details I think this is reasonable to
include in contrib, as a set of examples if nothing else. Still, I'm
curious about a few things. Are there actual users (other than the
author)?  What would we do about bug reports? Will you follow the list,
or would we explicitely tell people to contact you directly?

I guess some of the python experts might want to discuss the coding
style of notmuch-new.py. pylint goes ballistic, for whatever that is
worth.

For the shell stuff, I noticed lots of unquoted parameter expansion;
also at some point you make a temporary directory using $$
directly rather than using e.g. mktemp.

What did you have in mind for a license? since there is no linking here,
it does not have to be GPL3+, but some standard Free license is needed I
think; since I'm also maintaining the Debian package, I don't want to
have to remove your stuff before uploading to Debian.

d



___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: Notmuch scripts (again), now with more usenet

2012-07-15 Thread Daniel Schoepe
On Sun, 15.07.2012 18:36, David Bremner wrote:
 Are there actual users (other than the author)?

I started using the slrn2maildir script yesterday, but none of the other
scripts. It's working fine so far.

Cheers,
Daniel


pgpnnUpoMefpM.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts (again), now with more usenet

2012-07-14 Thread c...@webprojekty.cz
Hello, for quite some time my set of scripts just lied in my repo and
waited for polish before release. So tonight I finally managed to update
the docs, remove old stuff, rewrite some unfortunate things etc.

One notable addition is slrn2maildir script which can convert NNTP
spool, eg. gmane mailing lists or blogs, as fetched by slrnpull to
maildir format. This way you can follow plethora of mailing lists
without subscribing, any blog that publishes full atom/rss feed or
usenet newsgroup.

For details see the readme:
  http://webprojekty.cz/ccx/loggerhead/zmuch/view/head:/README
or check out the code:
  bzr branch http://webprojekty.cz/ccx/bzr/zmuch

I hope it's now in the form acceptable for inclusion to contrib.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: 



Notmuch scripts (again), now with more usenet

2012-07-13 Thread ccx
Hello, for quite some time my set of scripts just lied in my repo and
waited for polish before release. So tonight I finally managed to update
the docs, remove old stuff, rewrite some unfortunate things etc.

One notable addition is slrn2maildir script which can convert NNTP
spool, eg. gmane mailing lists or blogs, as fetched by slrnpull to
maildir format. This way you can follow plethora of mailing lists
without subscribing, any blog that publishes full atom/rss feed or
usenet newsgroup.

For details see the readme:
  http://webprojekty.cz/ccx/loggerhead/zmuch/view/head:/README
or check out the code:
  bzr branch http://webprojekty.cz/ccx/bzr/zmuch

I hope it's now in the form acceptable for inclusion to contrib.


signature.asc
Description: Digital signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts

2011-07-10 Thread David Bremner
On Fri, 24 Jun 2011 13:28:21 +0200, ccx at te2000.cz wrote:
> As some of you know I have written several scripts that aid using
> notmuch, including an alternative to the notmuch-mutt perl script.
> 
> Since Carl Worth consented to include them into official distribution
> I am now cleaning them up, writing docs and extending it so it covers
> all features notmuch-mutt currently has.

Sorry if I missed this somewhere, but how does the functionality of your
scripts compare to those of Stefano Zacchiroli

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628018

At least I think the mutt-notmuch referred to here is a third
alternative compared to your scripts and those of wart_ (Peter John Hartman?)

David
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: 



Re: Notmuch scripts

2011-07-10 Thread David Bremner
On Fri, 24 Jun 2011 13:28:21 +0200, c...@te2000.cz wrote:
 As some of you know I have written several scripts that aid using
 notmuch, including an alternative to the notmuch-mutt perl script.
 
 Since Carl Worth consented to include them into official distribution
 I am now cleaning them up, writing docs and extending it so it covers
 all features notmuch-mutt currently has.

Sorry if I missed this somewhere, but how does the functionality of your
scripts compare to those of Stefano Zacchiroli

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628018

At least I think the mutt-notmuch referred to here is a third
alternative compared to your scripts and those of wart_ (Peter John Hartman?)

David


pgpMdOsJURI0r.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts

2011-06-28 Thread Pieter Praet
On Mon, 27 Jun 2011 21:31:26 -0400, Ben Gamari  
wrote:
> [SNIP] It
> would be nice, however, if the emacs interface supported hiding tags
> matching certain patterns (say /\..+/).

This should be possible as of last month (eb4e0ea2),
by courtesy of Daniel Schoepe [1].

> 
> - Ben
> 
> ___
> notmuch mailing list
> notmuch at notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch


Peace

-- 
Pieter


[1] id:"87fwoath2s.fsf at gilead.home.box"


Notmuch scripts

2011-06-28 Thread Ben Gamari
On Tue, 28 Jun 2011 10:36:59 +0200, Pieter Praet  wrote:
> On Mon, 27 Jun 2011 21:31:26 -0400, Ben Gamari  
> wrote:
> > [SNIP] It
> > would be nice, however, if the emacs interface supported hiding tags
> > matching certain patterns (say /\..+/).
> 
> This should be possible as of last month (eb4e0ea2),
> by courtesy of Daniel Schoepe [1].
> 
Thanks for your note, althought it appears this only appears to apply to
the notmuch-hello all-tags list. I was hoping one could hide tag
patterns from all lists (or at least search results). This is definitely
a good first step, however.

Cheers,

- Ben


Re: Notmuch scripts

2011-06-28 Thread Pieter Praet
On Mon, 27 Jun 2011 21:31:26 -0400, Ben Gamari bgamari.f...@gmail.com wrote:
 [SNIP] It
 would be nice, however, if the emacs interface supported hiding tags
 matching certain patterns (say /\..+/).

This should be possible as of last month (eb4e0ea2),
by courtesy of Daniel Schoepe [1].

 
 - Ben
 
 ___
 notmuch mailing list
 notmuch@notmuchmail.org
 http://notmuchmail.org/mailman/listinfo/notmuch


Peace

-- 
Pieter


[1] id:87fwoath2s@gilead.home.box
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: Notmuch scripts

2011-06-28 Thread Ben Gamari
On Tue, 28 Jun 2011 10:36:59 +0200, Pieter Praet pie...@praet.org wrote:
 On Mon, 27 Jun 2011 21:31:26 -0400, Ben Gamari bgamari.f...@gmail.com wrote:
  [SNIP] It
  would be nice, however, if the emacs interface supported hiding tags
  matching certain patterns (say /\..+/).
 
 This should be possible as of last month (eb4e0ea2),
 by courtesy of Daniel Schoepe [1].
 
Thanks for your note, althought it appears this only appears to apply to
the notmuch-hello all-tags list. I was hoping one could hide tag
patterns from all lists (or at least search results). This is definitely
a good first step, however.

Cheers,

- Ben
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: Notmuch scripts

2011-06-27 Thread Ben Gamari
On Fri, 24 Jun 2011 11:29:21 -0700, Carl Worth cwo...@cworth.org wrote:
* Spam filter. Do you guys use any? What does it's interface look like?
  I currently use bsfilter which I've found does it's job pretty
  well.
 
 I've currently got amavis and spamassassin adding extra headers, (and
 below a certain threshold I've got maildrop delivering detected spam to
 a separate maildir).
 
 Currently, notmuch never sees the detected spam. Ever since we got
 folder: support I've been meaning to let notmuch see it so that I can
 use notmuch to dig into my spam when I suspect something got
 mis-detected.
 
 I don't currently have any system for getting user-provided feedback
 into my spam filtering. Do you get that with bsfilter?
 
I use bogofilter along with a python cron job to bring my tags and the
spam filter into sync. I use a tag (junk) to mark mail as spam and
two other tags (.bf_ham and .bf_spam) to indicate that the message has been 
added to
bogofilter. The script's task is then to,

 * Unregister as spam, register as ham messages with tag:.bf_spam and not 
tag:junk with bogofilter
 * Register as spam, unregister as ham messages with tag:junk and not 
tag:.bf_spam

This is pretty straightforward to implement and is quite effective. It
would be nice, however, if the emacs interface supported hiding tags
matching certain patterns (say /\..+/).

- Ben

___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Notmuch scripts

2011-06-25 Thread c...@te2000.cz
On Fri, Jun 24, 2011 at 11:29:21AM -0700, Carl Worth wrote:
> So much of the new functionality here consists of things I'd love to
> have implemented in the core command-line interface of notmuch

That's what I thought. I think it's actually beneficial to go the
prototyping route here and start with implementations that can be
written and altered quickly.

> The features I see that I'd really like to see in the core notmuch
> command-line tool are:
> 
>   * Configurable "saved searches", (a syntax for expanding aliases
>   for often-repeated search specifications).
> 
> That's an idea we've had for a while. What's new with the
> zmuch implementation is the proposal of ":alias" for the
> syntax. I think I might like that quite a bit. It looks a bit
> easier to read (and type) than the previously-proposed
> "{alias}".

Glad you like it. :-)

>   * Delivery of search results to a maildir of symlinks
> 
> The zmuch implementation has this functionality intertwined
> with something that also invokes mutt. Obviously, people using
> other MUAs might like to access this feature independently.

That's one of reasons I'm rewriting it. What I'm planning to have is:

  * notmuch-maildir-create -- make the symlinks, also save metadata in
  the maildir

  * notmuch-maildir-merge -- reflect the changes on the original files

  * notmuch-maildir-refresh -- merge and recreate with same query

  * notmuch-maildir-mua -- create temp directory, invoke MUA (mutt) on
   it, merge back

  * notmuch-maildir-search -- merge if old maildir is there, prompt for
  query, create new maildir

The last one should be sufficient replacement for what notmuch-mutt
currently does, provided one has set up to run merge after mutt instance
exits. I'm not very satisfied with naming on the last two, so
suggestions are welcome :-)

>   * Operations on files matching search terms (move, remove,
>   xargs)
> 
> This isn't an operation I'd previously considered including in
> notmuch, but it does seem generally quite useful.

These are just handy shorthands, the actual command could still fit on
one line.

> Should we consider doing something like git does and allow
> something like "notmuch xargs" simply find and invoke a shell
> script named notmuch-xargs?

I thought of that also, but I wouldn't do that yet. Not until the
scripts are bit more polished and tested.

> Doing that could let us get a bunch of this functionality in
> place in the "core" sooner than if we waited for it to be
> re-implemented in C.
> 
> Though if we did this, I think I'd be highly inclined to port
> the scripts from zsh to bash or even POSIX sh. How hard would
> that be?

Not much of a problem for simpler scripts, but for the big ones like
saved searches or maildir merging it would mean a lot of added
boilerplate. That would reduce the readability and defeat the purpose of
prototyping.

I could rewrite the more complex ones in python, but on the other hand,
the zsh package is just 6MiB here including debugging symbols. I don't
think there will be many who will find it problematic to install.

>   * Better date syntax for search specifications
> 
> That's something that's obviously been missing from notmuch
> core from the beginning. And there have been several proposals
> with patches to do this in various ways.

I think it would be neat to steal this from the 'at' command.
By the way, this is another use-case for notmuch proxy.

>   * Implicit concatenation of search terms with OR
> 
> This seems like something easy to do with a command-line
> arguemnt. Perhaps "notmuch search --or ..." ?

What would I personally like would be to use [] to mean the same as (),
just with implicit ORs inside. For example: "[ foo bar ( spam eggs ) ]"
would expand to "foo or bar or ( spam and eggs )". This way we can have
long sequences of both ORs and ANDs in one query.


> If we got all that into the core, then what would be left here would be:
> 
>   notmuch-mailvars.sh
>   notmuch-mutt.sh
> 
>   These would provide integration of notmuch with mutt.

Actually I wish to make it generic enough that it can be used with
anything that can read a maildir.

>   notmuch-spam.sh
>   notmuch-unspam.sh
> 
>   These would provide integration of notmuch with
>   bsfilter, (and perhaps should be named to make that more
>   clear---or generalized to justify the current name).

I'd love to make it generic, that's why I asked what people use.

>   notmuch-pager.sh
> 
>   I haven't looked at this to see what the colorization
>   actually looks like, (I'm not always a huge fan of lots
>   of color in my 

Notmuch scripts

2011-06-24 Thread c...@te2000.cz
Hello list!

As some of you know I have written several scripts that aid using
notmuch, including an alternative to the notmuch-mutt perl script.

Since Carl Worth consented to include them into official distribution
I am now cleaning them up, writing docs and extending it so it covers
all features notmuch-mutt currently has.

They can currently be obtained by:
bzr branch http://webprojekty.cz/ccx/bzr/zmuch
Or you can browse the code at:
http://webprojekty.cz/ccx/loggerhead/zmuch/files

During the process of polishing the scripts I thought about few things
that may be interesting to other people integrating notmuch, so let me
hear your opinions. :-)

$NOTMUCH and proxies:
There are applications (whether full-blown interfaces or simple scripts)
that use notmuch. There are scrips that work as proxies to actual
notmuch, eg. by invoking ssh to a machine where the mails are, or
processing the argument list and expanding saved searches. Therefore it
would be very practical if the path to actual executable would be
configurable. Thus I propose:

  * Every application that does not act as a proxy should use
environment variable NOTMUCH to find the actual notmuch executable.
If not defined or empty, just execute 'notmuch' as usual.

  * Every application that acts as a proxy should ignore the NOTMUCH
variable, instead it should be configurable in other way
(configuration file or something easily changeable). This way
chaining of proxies will be possible.

Configuration and temporary files:
I like XDG specification. I think it's bit unnecessary to have to have
config files that belong only to few scripts littered all around my
homedir. Also I think it's reasonable that user would be able to specify
where to put the temporary files. That said atm I have ~/.zmuch as the
only config file, as it felt bit weird to create new directory for just
one file. But as I'm preparing the scripts I see more and more things
that are specific to my setup and I would like them to be configurable.
These are:

  * Spam filter. Do you guys use any? What does it's interface look like?
I currently use bsfilter which I've found does it's job pretty well.

  * Colors. I use bright fg on dark bg, but I understand somebody won't
be happy with this choice.

  * New message processing. Currently I check for spam and I mute
selected threads. I can see this can be made quite configurable.
Maybe create procmail equivalent for notmuch? :-)

Thanks for notmuch! I look forward to your responses.
Jan Pobrislo (ccxCZ at freenode)
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: 



Notmuch scripts

2011-06-24 Thread Carl Worth
On Fri, 24 Jun 2011 13:28:21 +0200, ccx at te2000.cz wrote:
> As some of you know I have written several scripts that aid using
> notmuch, including an alternative to the notmuch-mutt perl script.

Thanks for sharing these, Jan!

> Since Carl Worth consented to include them into official distribution
> I am now cleaning them up, writing docs and extending it so it covers
> all features notmuch-mutt currently has.
...
> Or you can browse the code at:
>   http://webprojekty.cz/ccx/loggerhead/zmuch/files

It's been interesting for me to read through the README here.

So much of the new functionality here consists of things I'd love to
have implemented in the core command-line interface of notmuch, (I
always have wanted it to be useful for direct command-line interaction
by a human). Some of these features I think have even be implemented
previously by Austin through his custom query parser.

The features I see that I'd really like to see in the core notmuch
command-line tool are:

* Configurable "saved searches", (a syntax for expanding aliases
  for often-repeated search specifications).

  That's an idea we've had for a while. What's new with the
  zmuch implementation is the proposal of ":alias" for the
  syntax. I think I might like that quite a bit. It looks a bit
  easier to read (and type) than the previously-proposed
  "{alias}".

* Delivery of search results to a maildir of symlinks

  The zmuch implementation has this functionality intertwined
  with something that also invokes mutt. Obviously, people using
  other MUAs might like to access this feature independently.

  I think I'd like to see this as:

notmuch search --format=maildir:/path/to/directory

* Operations on files matching search terms (move, remove,
  xargs)

  This isn't an operation I'd previously considered including in
  notmuch, but it does seem generally quite useful.

  Should we consider doing something like git does and allow
  something like "notmuch xargs" simply find and invoke a shell
  script named notmuch-xargs?

  Doing that could let us get a bunch of this functionality in
  place in the "core" sooner than if we waited for it to be
  re-implemented in C.

  Though if we did this, I think I'd be highly inclined to port
  the scripts from zsh to bash or even POSIX sh. How hard would
  that be?

* Better date syntax for search specifications

  That's something that's obviously been missing from notmuch
  core from the beginning. And there have been several proposals
  with patches to do this in various ways.

* Implicit concatenation of search terms with OR

  This seems like something easy to do with a command-line
  arguemnt. Perhaps "notmuch search --or ..." ?

If we got all that into the core, then what would be left here would be:

notmuch-mailvars.sh
notmuch-mutt.sh

These would provide integration of notmuch with mutt.

notmuch-spam.sh
notmuch-unspam.sh

These would provide integration of notmuch with
bsfilter, (and perhaps should be named to make that more
clear---or generalized to justify the current name).

notmuch-pager.sh

I haven't looked at this to see what the colorization
actually looks like, (I'm not always a huge fan of lots
of color in my terminals). It seems that this would be
more cleanly implemented as notmuch-colorize.sh or so
and leave the pagination separate.

If we had that, I'd feel really comfortable having each of those in
contrib. I think contrib should be restricted to things which provide
integration of notmuch with some external tool, (and should make that
obvious by having a name like notmuch- or notmuch-.sh or
whatever).

All in all, there's definitely some very interesting functionality here,
and I definitely appreciate you sharing it. Let's figure out the best
way to get it all integrated into notmuch.

Maybe in the meantime we throw everything into contrib even if some of
it is seen as just proposals for better interfaces in the core tool? I
don't know.

>   * Every application that does not act as a proxy should use
> environment variable NOTMUCH to find the actual notmuch executable.
> 
>   * Every application that acts as a proxy should ignore the NOTMUCH
>   variable

That sounds reasonable enough to me. Perhaps these rules could go into a
new contrib/README that would set out some guidelines for writing
contrib tools, (such as notmuch- which I mentioned above).

> Configuration and temporary files:
> I like XDG specification.

I'm missing some context to know what you're suggesting here.

> I think it's bit unnecessary 

Notmuch scripts

2011-06-24 Thread ccx
Hello list!

As some of you know I have written several scripts that aid using
notmuch, including an alternative to the notmuch-mutt perl script.

Since Carl Worth consented to include them into official distribution
I am now cleaning them up, writing docs and extending it so it covers
all features notmuch-mutt currently has.

They can currently be obtained by:
bzr branch http://webprojekty.cz/ccx/bzr/zmuch
Or you can browse the code at:
http://webprojekty.cz/ccx/loggerhead/zmuch/files

During the process of polishing the scripts I thought about few things
that may be interesting to other people integrating notmuch, so let me
hear your opinions. :-)

$NOTMUCH and proxies:
There are applications (whether full-blown interfaces or simple scripts)
that use notmuch. There are scrips that work as proxies to actual
notmuch, eg. by invoking ssh to a machine where the mails are, or
processing the argument list and expanding saved searches. Therefore it
would be very practical if the path to actual executable would be
configurable. Thus I propose:

  * Every application that does not act as a proxy should use
environment variable NOTMUCH to find the actual notmuch executable.
If not defined or empty, just execute 'notmuch' as usual.

  * Every application that acts as a proxy should ignore the NOTMUCH
variable, instead it should be configurable in other way
(configuration file or something easily changeable). This way
chaining of proxies will be possible.

Configuration and temporary files:
I like XDG specification. I think it's bit unnecessary to have to have
config files that belong only to few scripts littered all around my
homedir. Also I think it's reasonable that user would be able to specify
where to put the temporary files. That said atm I have ~/.zmuch as the
only config file, as it felt bit weird to create new directory for just
one file. But as I'm preparing the scripts I see more and more things
that are specific to my setup and I would like them to be configurable.
These are:

  * Spam filter. Do you guys use any? What does it's interface look like?
I currently use bsfilter which I've found does it's job pretty well.

  * Colors. I use bright fg on dark bg, but I understand somebody won't
be happy with this choice.

  * New message processing. Currently I check for spam and I mute
selected threads. I can see this can be made quite configurable.
Maybe create procmail equivalent for notmuch? :-)

Thanks for notmuch! I look forward to your responses.
Jan Pobrislo (ccxCZ@freenode)


pgpNDYPQ3qwls.pgp
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: Notmuch scripts

2011-06-24 Thread Carl Worth
On Fri, 24 Jun 2011 13:28:21 +0200, c...@te2000.cz wrote:
 As some of you know I have written several scripts that aid using
 notmuch, including an alternative to the notmuch-mutt perl script.

Thanks for sharing these, Jan!

 Since Carl Worth consented to include them into official distribution
 I am now cleaning them up, writing docs and extending it so it covers
 all features notmuch-mutt currently has.
...
 Or you can browse the code at:
   http://webprojekty.cz/ccx/loggerhead/zmuch/files

It's been interesting for me to read through the README here.

So much of the new functionality here consists of things I'd love to
have implemented in the core command-line interface of notmuch, (I
always have wanted it to be useful for direct command-line interaction
by a human). Some of these features I think have even be implemented
previously by Austin through his custom query parser.

The features I see that I'd really like to see in the core notmuch
command-line tool are:

* Configurable saved searches, (a syntax for expanding aliases
  for often-repeated search specifications).

  That's an idea we've had for a while. What's new with the
  zmuch implementation is the proposal of :alias for the
  syntax. I think I might like that quite a bit. It looks a bit
  easier to read (and type) than the previously-proposed
  {alias}.

* Delivery of search results to a maildir of symlinks

  The zmuch implementation has this functionality intertwined
  with something that also invokes mutt. Obviously, people using
  other MUAs might like to access this feature independently.

  I think I'd like to see this as:

notmuch search --format=maildir:/path/to/directory

* Operations on files matching search terms (move, remove,
  xargs)

  This isn't an operation I'd previously considered including in
  notmuch, but it does seem generally quite useful.

  Should we consider doing something like git does and allow
  something like notmuch xargs simply find and invoke a shell
  script named notmuch-xargs?

  Doing that could let us get a bunch of this functionality in
  place in the core sooner than if we waited for it to be
  re-implemented in C.

  Though if we did this, I think I'd be highly inclined to port
  the scripts from zsh to bash or even POSIX sh. How hard would
  that be?

* Better date syntax for search specifications

  That's something that's obviously been missing from notmuch
  core from the beginning. And there have been several proposals
  with patches to do this in various ways.

* Implicit concatenation of search terms with OR

  This seems like something easy to do with a command-line
  arguemnt. Perhaps notmuch search --or ... ?

If we got all that into the core, then what would be left here would be:

notmuch-mailvars.sh
notmuch-mutt.sh

These would provide integration of notmuch with mutt.

notmuch-spam.sh
notmuch-unspam.sh

These would provide integration of notmuch with
bsfilter, (and perhaps should be named to make that more
clear---or generalized to justify the current name).

notmuch-pager.sh

I haven't looked at this to see what the colorization
actually looks like, (I'm not always a huge fan of lots
of color in my terminals). It seems that this would be
more cleanly implemented as notmuch-colorize.sh or so
and leave the pagination separate.

If we had that, I'd feel really comfortable having each of those in
contrib. I think contrib should be restricted to things which provide
integration of notmuch with some external tool, (and should make that
obvious by having a name like notmuch-tool or notmuch-tool.sh or
whatever).

All in all, there's definitely some very interesting functionality here,
and I definitely appreciate you sharing it. Let's figure out the best
way to get it all integrated into notmuch.

Maybe in the meantime we throw everything into contrib even if some of
it is seen as just proposals for better interfaces in the core tool? I
don't know.

   * Every application that does not act as a proxy should use
 environment variable NOTMUCH to find the actual notmuch executable.
 
   * Every application that acts as a proxy should ignore the NOTMUCH
   variable

That sounds reasonable enough to me. Perhaps these rules could go into a
new contrib/README that would set out some guidelines for writing
contrib tools, (such as notmuch-tool which I mentioned above).

 Configuration and temporary files:
 I like XDG specification.

I'm missing some context to know what you're suggesting here.

 I think it's bit unnecessary to have to have