Bye !

2012-10-22 Thread Xavier Maillard
Hi,

After several months of notmuch usage, I feel like it is not really
adapted to me or I do not want to adapt. I am going back to my first
and beloved simplistic rmail.

I just wanted to congratulate all of you for your really appreciated
awesome work. Thank you very much and keep up the good work. I'll try
to follow your baby enhancing even if I am not using it anymore.

Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org


Bye !

2012-10-21 Thread Xavier Maillard
Hi,

After several months of notmuch usage, I feel like it is not really
adapted to me or I do not want to adapt. I am going back to my first
and beloved simplistic rmail.

I just wanted to congratulate all of you for your really appreciated
awesome work. Thank you very much and keep up the good work. I'll try
to follow your baby enhancing even if I am not using it anymore.

Xavier
-- 
http://www.gnu.org
http://www.april.org
http://www.lolica.org
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


A big thank you for the major tagging speedup

2012-02-08 Thread Xavier Maillard

On Tue, 07 Feb 2012 17:36:24 +0100, Florian Friesdorf  
wrote:
> 
> I just wanted to express my gratitude, that for a while now notmuch is
> tagging by a factor 200 faster than it used to be!

+1 It is really comfortable to notmuch tag now !

/Xavier


Re: A big thank you for the major tagging speedup

2012-02-08 Thread Xavier Maillard

On Tue, 07 Feb 2012 17:36:24 +0100, Florian Friesdorf f...@chaoflow.net wrote:
 
 I just wanted to express my gratitude, that for a while now notmuch is
 tagging by a factor 200 faster than it used to be!

+1 It is really comfortable to notmuch tag now !

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


Re: [PATCH 08/10] test: set variables using `let' instead of `setq' in Emacs tests

2012-01-24 Thread Xavier Maillard
On Tue, 28 Jun 2011 08:45:09 +0400, Dmitry Kurochkin 
dmitry.kuroch...@gmail.com wrote:
 Using `setq' for setting variables in Emacs tests affect other
 tests that may run in the same Emacs environment.  Currently it
 works because each test is run in a separate Emacs instance.  But
 in the future multiple tests will run in a single Emacs instance.
 The patch changes all variables to use `let', so the scope of the
 change is limited to a single test.

+1 (definetely)

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


Re: [PATCH 10/10] test: use emacsclient(1) for Emacs tests

2012-01-24 Thread Xavier Maillard
On Tue, 28 Jun 2011 08:45:11 +0400, Dmitry Kurochkin 
dmitry.kuroch...@gmail.com wrote:
 Before the change, every Emacs test ran in a separate Emacs
 instance.  Starting Emacs many times wastes considerable time and
 it gets worse as the test suite grows.  The patch solves this by
 using a single Emacs server and emacsclient(1) to run multiple
 tests.  Emacs server is started on the first test_emacs call and
 stopped when test_done is called.  We take care not to leave
 orphan Emacs processes behind when test is terminated by whatever
 reason: Emacs server runs a watchdog that periodically checks
 that the test is still running.
 
 Some tests need to provide user input.  Before the change, this
 was done using echo(1) to Emacs stdin.  This no longer works and
 instead `standard-input' variable is set accordingly to make
 `read' return the appropriate string.

I really like this too. 

+1

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


Re: [PATCH 6/6] emacs: modify the default show-mode key bindings for archiving

2012-01-24 Thread Xavier Maillard
This is also +1 for me.

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


[PATCH 6/6] emacs: modify the default show-mode key bindings for archiving

2012-01-23 Thread Xavier Maillard
This is also +1 for me.

/Xavier


[PATCH 10/10] test: use emacsclient(1) for Emacs tests

2012-01-23 Thread Xavier Maillard
On Tue, 28 Jun 2011 08:45:11 +0400, Dmitry Kurochkin  wrote:
> Before the change, every Emacs test ran in a separate Emacs
> instance.  Starting Emacs many times wastes considerable time and
> it gets worse as the test suite grows.  The patch solves this by
> using a single Emacs server and emacsclient(1) to run multiple
> tests.  Emacs server is started on the first test_emacs call and
> stopped when test_done is called.  We take care not to leave
> orphan Emacs processes behind when test is terminated by whatever
> reason: Emacs server runs a watchdog that periodically checks
> that the test is still running.
> 
> Some tests need to provide user input.  Before the change, this
> was done using echo(1) to Emacs stdin.  This no longer works and
> instead `standard-input' variable is set accordingly to make
> `read' return the appropriate string.

I really like this too. 

+1

/Xavier


[PATCH 08/10] test: set variables using `let' instead of `setq' in Emacs tests

2012-01-23 Thread Xavier Maillard
On Tue, 28 Jun 2011 08:45:09 +0400, Dmitry Kurochkin  wrote:
> Using `setq' for setting variables in Emacs tests affect other
> tests that may run in the same Emacs environment.  Currently it
> works because each test is run in a separate Emacs instance.  But
> in the future multiple tests will run in a single Emacs instance.
> The patch changes all variables to use `let', so the scope of the
> change is limited to a single test.

+1 (definetely)

/Xavier


[PATCH 3/4] config: only set search.exclude_tags to "deleted; spam; " during setup

2012-01-22 Thread Xavier Maillard

On Thu, 19 Jan 2012 20:19:03 +0100, Pieter Praet  wrote:
> If the 'search.exclude_tags' option is missing from the config file,
> its value is automatically set to "deleted;spam;".  Taking PoLS/DWIM
> into account, this should probably only happen during setup.
> 
> This patch is actually Austin Clements' work:
>   id:"20120117203211.GQ16740 at mit.edu"

I do not think this is a sane default. As I told it in another post. I
do not expect notmuch to skew my search queries not that I specifically
asked.

/Xavier


[PATCH v3 2/2] search: Support automatic tag exclusions

2012-01-22 Thread Xavier Maillard
Hey Pieter,

On Thu, 19 Jan 2012 20:19:00 +0100, Pieter Praet  wrote:
> Nice feature!  I won't be using it myself, but I can imagine it being
> *very* useful for those who still feel the need to "delete" email :).

Adding a 'deleted' tag does not mean there will be a delete/purge
process ;) (currently I got 5k messages with the tag deleted ;). 

> Nitpicking:
> 

[ ... ]

>   So I'd like to suggest replacing all occurences of "auto_exclude_tags"
>   with "search_exclude_tags" (and simply "exclude_tags" in the args to
>   `_config_get_list' and `_config_set_list', of course).

+1

>   Unfortunately, this would also partially invalidate your recent NEWS
>   submission [2].
> 
> - If the 'search.exclude_tags' option is missing from the config file,
>   its value is automatically set to "deleted;spam;", which probably isn't
>   a sane default.  Luckily, you've already provided the solution [3].

I am against doing something /unsafe/ in the user's back. If there is no
option set intentionnaly by the user, there is nothing notmuch should
do -i.e no exclusion -

> - To make new users aware of the config option's existence, we should
>   prompt them to configure it during setup.

+1

/Xavier


[PATCH] .dir-locals.el: changed one-char comment prefix '; ' to two; '; ; '

2012-01-22 Thread Xavier Maillard
On Sun, 22 Jan 2012 10:35:47 +0200, Tomi Ollila  wrote:
> Like in emacs/*.el two comment chars (;;) is required so that
> (indent-region) doesn't break indentation.
> ---
>  .dir-locals.el |6 +++---

+1

/Xavier


Re: [PATCH] .dir-locals.el: changed one-char comment prefix '; ' to two; '; ; '

2012-01-22 Thread Xavier Maillard
On Sun, 22 Jan 2012 10:35:47 +0200, Tomi Ollila tomi.oll...@iki.fi wrote:
 Like in emacs/*.el two comment chars (;;) is required so that
 (indent-region) doesn't break indentation.
 ---
  .dir-locals.el |6 +++---

+1

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


Re: [PATCH v3 2/2] search: Support automatic tag exclusions

2012-01-22 Thread Xavier Maillard
Hey Pieter,

On Thu, 19 Jan 2012 20:19:00 +0100, Pieter Praet pie...@praet.org wrote:
 Nice feature!  I won't be using it myself, but I can imagine it being
 *very* useful for those who still feel the need to delete email :).

Adding a 'deleted' tag does not mean there will be a delete/purge
process ;) (currently I got 5k messages with the tag deleted ;). 

 Nitpicking:
 

[ ... ]

   So I'd like to suggest replacing all occurences of auto_exclude_tags
   with search_exclude_tags (and simply exclude_tags in the args to
   `_config_get_list' and `_config_set_list', of course).

+1
 
   Unfortunately, this would also partially invalidate your recent NEWS
   submission [2].
 
 - If the 'search.exclude_tags' option is missing from the config file,
   its value is automatically set to deleted;spam;, which probably isn't
   a sane default.  Luckily, you've already provided the solution [3].

I am against doing something /unsafe/ in the user's back. If there is no
option set intentionnaly by the user, there is nothing notmuch should
do -i.e no exclusion -

 - To make new users aware of the config option's existence, we should
   prompt them to configure it during setup.

+1

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


Re: [PATCH 3/4] config: only set search.exclude_tags to deleted; spam; during setup

2012-01-22 Thread Xavier Maillard

On Thu, 19 Jan 2012 20:19:03 +0100, Pieter Praet pie...@praet.org wrote:
 If the 'search.exclude_tags' option is missing from the config file,
 its value is automatically set to deleted;spam;.  Taking PoLS/DWIM
 into account, this should probably only happen during setup.
 
 This patch is actually Austin Clements' work:
   id:20120117203211.gq16...@mit.edu

I do not think this is a sane default. As I told it in another post. I
do not expect notmuch to skew my search queries not that I specifically
asked.

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


[PATCH] emacs/*.el: changed one-char comment prefix '; ' to two; '; ; '

2012-01-21 Thread Xavier Maillard

On Sat, 21 Jan 2012 16:44:28 +0200, Tomi Ollila  wrote:
> In order for emacs (indent-region) to (re)indent emacs lisp
> properly there needs to be at least 2 comment characters (;;).
> ---
> 
> resubmitted as the old patch does not apply cleanly anymore.
> 
>  emacs/notmuch-hello.el |4 +-
>  emacs/notmuch-lib.el   |   16 +++---
>  emacs/notmuch-show.el  |   16 +++---
>  emacs/notmuch.el   |  118 
> 
>  4 files changed, 77 insertions(+), 77 deletions(-)

You should add dir-locals.el to this list.

Otherwise, +1

/Xavier


Re: [PATCH] emacs/*.el: changed one-char comment prefix '; ' to two; '; ; '

2012-01-21 Thread Xavier Maillard

On Sat, 21 Jan 2012 16:44:28 +0200, Tomi Ollila tomi.oll...@iki.fi wrote:
 In order for emacs (indent-region) to (re)indent emacs lisp
 properly there needs to be at least 2 comment characters (;;).
 ---
 
 resubmitted as the old patch does not apply cleanly anymore.
 
  emacs/notmuch-hello.el |4 +-
  emacs/notmuch-lib.el   |   16 +++---
  emacs/notmuch-show.el  |   16 +++---
  emacs/notmuch.el   |  118 
 
  4 files changed, 77 insertions(+), 77 deletions(-)

You should add dir-locals.el to this list.

Otherwise, +1

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


tach.el: an attachment interface for message mode.

2012-01-20 Thread Xavier Maillard
On Fri, 20 Jan 2012 12:04:49 -0500, Jesse Rosenthal  
wrote:

[ ... ]

> Thus: tach.el. Tach is a minor mode that adds mutt-like attachment
> handling to message mode. It's not notmuch specific, but I wrote it to
> use with notmuch, and I thought it might be of use to some on the
> list.

I like it.

> Now when you type "C-c C-a" in message-mode, you should get a new window
> with an attachment list. In that window, you can add and delete
> attachments using `+' and `-', and scroll through them using the arrow
> keys or the emacs direction commands.

Simple but at first it is not easy to understand what to do with that
window. Also, there is no way to toggle the window visibility. But for a
first shot, it is a good shot :D

I tried it by adding tach.el to myself. When sending the message, I have
been asked whether I'd like to update copyright date and change licence
to GPL3, huh ? Is this something specific to how tach.el works ?

/Xavier



Re: tach.el: an attachment interface for message mode.

2012-01-20 Thread Xavier Maillard
On Fri, 20 Jan 2012 12:04:49 -0500, Jesse Rosenthal jrosent...@jhu.edu wrote:

[ ... ]

 Thus: tach.el. Tach is a minor mode that adds mutt-like attachment
 handling to message mode. It's not notmuch specific, but I wrote it to
 use with notmuch, and I thought it might be of use to some on the
 list.

I like it.

 Now when you type C-c C-a in message-mode, you should get a new window
 with an attachment list. In that window, you can add and delete
 attachments using `+' and `-', and scroll through them using the arrow
 keys or the emacs direction commands.

Simple but at first it is not easy to understand what to do with that
window. Also, there is no way to toggle the window visibility. But for a
first shot, it is a good shot :D
 
I tried it by adding tach.el to myself. When sending the message, I have
been asked whether I'd like to update copyright date and change licence
to GPL3, huh ? Is this something specific to how tach.el works ?

/Xavier

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


Sort by newest first from notmuch-hello ?

2012-01-19 Thread Xavier Maillard
Hi,

I am running latest release (0.11).
I have set notmuch-search-oldest-first to t. When doing M-x
notmuch-search, messages order does not respect this setting -i.e newest
com firts -. On the other hand, from notmuch-hello I get expected
behaviour.

How can this be more "consistent" ?

By the way, am I alone having hundreds thousand messages ? If not, what
would you thing setting this variable to `nil' by default ? Having first
messages at the top would be more usefull that scrolling down really far
;-)

Regards

/Xavier


Sort by newest first from notmuch-hello ?

2012-01-18 Thread Xavier Maillard
Hi,

I am running latest release (0.11).
I have set notmuch-search-oldest-first to t. When doing M-x
notmuch-search, messages order does not respect this setting -i.e newest
com firts -. On the other hand, from notmuch-hello I get expected
behaviour.

How can this be more consistent ?

By the way, am I alone having hundreds thousand messages ? If not, what
would you thing setting this variable to `nil' by default ? Having first
messages at the top would be more usefull that scrolling down really far
;-)

Regards

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


on deleting messages

2012-01-17 Thread Xavier Maillard
Hi,

On Tue, 17 Jan 2012 11:01:45 -0800, Jameson Graef Rollins  wrote:

[ ... ]

> Based on the show-mode improvements I recently sent [1], the following
> patch set implements thread and message delete keys.
> 
> This is the last I'm going to comment on this issue.  If we don't want
> to support this, we should put together something on the wiki that
> states we don't want to support it and that users should just bind it
> themselves (with a nice explanation how), so that we can try to reduce
> the number of future patches on the issue.

I think this is something every (new) users are expecting to have: a
simple and sensible way "to list the trashed messages". So I'd go for
it.

/Xavier


Re: on deleting messages

2012-01-17 Thread Xavier Maillard
Hi,

On Tue, 17 Jan 2012 11:01:45 -0800, Jameson Graef Rollins 
jroll...@finestructure.net wrote:

[ ... ]

 Based on the show-mode improvements I recently sent [1], the following
 patch set implements thread and message delete keys.
 
 This is the last I'm going to comment on this issue.  If we don't want
 to support this, we should put together something on the wiki that
 states we don't want to support it and that users should just bind it
 themselves (with a nice explanation how), so that we can try to reduce
 the number of future patches on the issue.

I think this is something every (new) users are expecting to have: a
simple and sensible way to list the trashed messages. So I'd go for
it.

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


[PATCH 2/2] notmuch-dev: Update the master branch when requested.

2012-01-16 Thread Xavier Maillard
On Mon, 16 Jan 2012 09:07:52 +, David Edmondson  wrote:
> On Fri, 13 Jan 2012 22:03:17 +0100, Xavier Maillard  
> wrote:
> > Have you planned to cook something about this in notmuch wiki ?
> > That sounds like something I could use to test patches more easily than
> > I do currently.
> 
> I'll do so.

If I can help, just tell :D

/Xavier


[PATCH v2] Document external dependencies in the test suite

2012-01-16 Thread Xavier Maillard
Hi,

On Mon, 16 Jan 2012 13:52:47 -0500, Ethan Glasser-Camp  
wrote:

[...]

> +Prerequisites
> +-
> +Some tests require external dependencies to run. Without them, they
> +will be skipped, or (rarely) marked failed. Please install these, so
> +that you know if you break anything.
> +
> +  - dtach(1)
> +  - emacs(1)
> +  - emacsclient(1)
> +  - gdb(1)
> +  - gpg(1)
> +  - python(1)

Looks good but just a nit: what is the meaning of the '1' ?

/Xavier


Re: [PATCH v2] Document external dependencies in the test suite

2012-01-16 Thread Xavier Maillard
Hi,

On Mon, 16 Jan 2012 13:52:47 -0500, Ethan Glasser-Camp gla...@cs.rpi.edu 
wrote:

[...]

 +Prerequisites
 +-
 +Some tests require external dependencies to run. Without them, they
 +will be skipped, or (rarely) marked failed. Please install these, so
 +that you know if you break anything.
 +
 +  - dtach(1)
 +  - emacs(1)
 +  - emacsclient(1)
 +  - gdb(1)
 +  - gpg(1)
 +  - python(1)

Looks good but just a nit: what is the meaning of the '1' ?

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


Re: [PATCH 2/2] notmuch-dev: Update the master branch when requested.

2012-01-16 Thread Xavier Maillard
On Mon, 16 Jan 2012 09:07:52 +, David Edmondson d...@dme.org wrote:
 On Fri, 13 Jan 2012 22:03:17 +0100, Xavier Maillard xav...@maillard.im 
 wrote:
  Have you planned to cook something about this in notmuch wiki ?
  That sounds like something I could use to test patches more easily than
  I do currently.
 
 I'll do so.

If I can help, just tell :D

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


[PATCH] Set fill column to 70 in .dir-locals.el and refactor other settings.

2012-01-14 Thread Xavier Maillard
On Fri, 13 Jan 2012 17:54:51 -0500, Austin Clements  wrote:
> Quoth Xavier Maillard on Jan 13 at 11:42 pm:
> > 
> > This controls where comments and other text wraps.  70 is the default
> > value, so this simply returns it to the default for people who have
> > overridden it.  Most notmuch code already adheres to this.
> > ---
> > SO here is the patch (still sorry if I did it wrongly and very badly).
> 
> You ammended it right, but actually the configuration is intentionally
> repeated for the various modes.

That's ok.

Maybe I will find an easier way to build and to send patches

/Xavier


notmuch release 0.11 now available

2012-01-14 Thread Xavier Maillard
Hi,

congratulations to all of the notmuch contributors.

Keep up the effort

/Xavier


[PATCH] Set fill column to 70 in .dir-locals.el and refactor other settings.

2012-01-13 Thread Xavier Maillard

This controls where comments and other text wraps.  70 is the default
value, so this simply returns it to the default for people who have
overridden it.  Most notmuch code already adheres to this.
---
SO here is the patch (still sorry if I did it wrongly and very badly).

 .dir-locals.el |   19 ++-
 1 files changed, 6 insertions(+), 13 deletions(-)

diff --git a/.dir-locals.el b/.dir-locals.el
index aea630b..27f01c0 100644
--- a/.dir-locals.el
+++ b/.dir-locals.el
@@ -1,23 +1,16 @@
-; emacs local configuration settings for notmuch source
-; surmised by dkg on 2010-11-23 13:43:18-0500
-; amended by amdragon on 2011-06-06
+;; emacs local configuration settings for notmuch source
+;; surmised by dkg on 2010-11-23 13:43:18-0500
+;; amended by amdragon on 2011-06-06

-((c-mode
+((nil
   (indent-tabs-mode . t)
   (tab-width . 8)
   (c-basic-offset . 4)
+  (fill-column . 70))
+ (c-mode
   (c-file-style . "linux"))
  (c++-mode
-  (indent-tabs-mode . t)
-  (tab-width . 8)
-  (c-basic-offset . 4)
   (c-file-style . "linux"))
- (emacs-lisp-mode
-  (indent-tabs-mode . t)
-  (tab-width . 8))
  (shell-mode
-  (indent-tabs-mode . t)
-  (tab-width . 8)
-  (sh-basic-offset . 4)
   (sh-indentation . 4))
  )
-- 
1.7.1



[PATCH] Set fill column to 70 in .dir-locals.el.

2012-01-13 Thread Xavier Maillard
Sorry if it is not correct to act like this (did I ever tell how n00b I
am when it comes to git ?).

So I wanted to /amend/ your patch to add some refactoring to it.

I hope this will not hurt :/


/Xavier



[PATCH] emacs: whitespace-cleanup for emacs/*.el files

2012-01-13 Thread Xavier Maillard
On Fri, 13 Jan 2012 11:50:52 +0200, Tomi Ollila  wrote:
> On Fri, 13 Jan 2012 08:22:49 +, David Edmondson  wrote:
> > On Thu, 12 Jan 2012 23:07:03 +0100, Xavier Maillard  
> > wrote:
> > > On Wed, 11 Jan 2012 17:13:35 +0200, Tomi Ollila  
> > > wrote:
> > > > Executed
> > > > for f in emacs/*.el
> > > > do emacs -q --batch --eval \
> > > > "(progn (find-file \"$f\") (whitespace-cleanup) (save-buffer))"
> > > > done
> > > > 
> > > > which
> > > > removed trailing whitespace and empty lines at the end of file
> > > > removed spaces before tab (if any)
> > > > converted 8 spaces to tabs in the beginning of line
> > > 
> > > +1
> > > 
> > > Maybe we should note something about this as a /coding style/ rule ?
> > 
> > How about "Running `indent-region' over the file should produce no
> > changes" as well?
> 
> So, In addition to 'uncrustify.cfg' we need emacs reformatter along lines:

What about doing all of this directly in .dir-locals.el (could be
considered unsafe though to add an EVAL block).

/Xavier


[PATCH 2/2] notmuch-dev: Update the master branch when requested.

2012-01-13 Thread Xavier Maillard
Hi David,

Have you planned to cook something about this in notmuch wiki ?
That sounds like something I could use to test patches more easily than
I do currently.

Note: I am totally a dummy when I have to use git :/

Regards

/Xavier


[PATCH] emacs: globally replace non-branching "(if (not ..." with "(unless ..."

2012-01-13 Thread Xavier Maillard

On Fri, 13 Jan 2012 08:23:55 +, David Edmondson  wrote:
> On Thu, 12 Jan 2012 18:33:06 +0100, Pieter Praet  wrote:
> > Less code, same results, without sacrificing readability.
> 
> +1, but why not replace non-branching `if' with `when' as well?

I tend to use WHEN for case I need to execute multiple
statements. For the rest, IF is ok.

/Xavier


[PATCH] Set fill column to 70 in .dir-locals.el.

2012-01-13 Thread Xavier Maillard

On Thu, 12 Jan 2012 18:17:23 -0500, Austin Clements  wrote:
> This controls where comments and other text wraps.  70 is the default
> value, so this simply returns it to the default for people who have
> overridden it.  Most notmuch code already adheres to this.

+1

/Xavier


Re: [PATCH] Set fill column to 70 in .dir-locals.el.

2012-01-13 Thread Xavier Maillard

On Thu, 12 Jan 2012 18:17:23 -0500, Austin Clements amdra...@mit.edu wrote:
 This controls where comments and other text wraps.  70 is the default
 value, so this simply returns it to the default for people who have
 overridden it.  Most notmuch code already adheres to this.

+1

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


Re: [PATCH] emacs: globally replace non-branching (if (not ... with (unless ...

2012-01-13 Thread Xavier Maillard

On Fri, 13 Jan 2012 08:23:55 +, David Edmondson d...@dme.org wrote:
 On Thu, 12 Jan 2012 18:33:06 +0100, Pieter Praet pie...@praet.org wrote:
  Less code, same results, without sacrificing readability.
 
 +1, but why not replace non-branching `if' with `when' as well?

I tend to use WHEN for case I need to execute multiple
statements. For the rest, IF is ok.

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


Re: [PATCH] emacs: whitespace-cleanup for emacs/*.el files

2012-01-13 Thread Xavier Maillard
On Fri, 13 Jan 2012 11:50:52 +0200, Tomi Ollila tomi.oll...@iki.fi wrote:
 On Fri, 13 Jan 2012 08:22:49 +, David Edmondson d...@dme.org wrote:
  On Thu, 12 Jan 2012 23:07:03 +0100, Xavier Maillard xav...@maillard.im 
  wrote:
   On Wed, 11 Jan 2012 17:13:35 +0200, Tomi Ollila tomi.oll...@iki.fi 
   wrote:
Executed
for f in emacs/*.el
do emacs -q --batch --eval \
(progn (find-file \$f\) (whitespace-cleanup) (save-buffer))
done

which
removed trailing whitespace and empty lines at the end of file
removed spaces before tab (if any)
converted 8 spaces to tabs in the beginning of line
   
   +1
   
   Maybe we should note something about this as a /coding style/ rule ?
  
  How about Running `indent-region' over the file should produce no
  changes as well?
 
 So, In addition to 'uncrustify.cfg' we need emacs reformatter along lines:

What about doing all of this directly in .dir-locals.el (could be
considered unsafe though to add an EVAL block).

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


Re: [PATCH] Set fill column to 70 in .dir-locals.el.

2012-01-13 Thread Xavier Maillard
Sorry if it is not correct to act like this (did I ever tell how n00b I
am when it comes to git ?).

So I wanted to /amend/ your patch to add some refactoring to it.

I hope this will not hurt :/


/Xavier

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


[PATCH] Set fill column to 70 in .dir-locals.el and refactor other settings.

2012-01-13 Thread Xavier Maillard

This controls where comments and other text wraps.  70 is the default
value, so this simply returns it to the default for people who have
overridden it.  Most notmuch code already adheres to this.
---
SO here is the patch (still sorry if I did it wrongly and very badly).

 .dir-locals.el |   19 ++-
 1 files changed, 6 insertions(+), 13 deletions(-)

diff --git a/.dir-locals.el b/.dir-locals.el
index aea630b..27f01c0 100644
--- a/.dir-locals.el
+++ b/.dir-locals.el
@@ -1,23 +1,16 @@
-; emacs local configuration settings for notmuch source
-; surmised by dkg on 2010-11-23 13:43:18-0500
-; amended by amdragon on 2011-06-06
+;; emacs local configuration settings for notmuch source
+;; surmised by dkg on 2010-11-23 13:43:18-0500
+;; amended by amdragon on 2011-06-06
 
-((c-mode
+((nil
   (indent-tabs-mode . t)
   (tab-width . 8)
   (c-basic-offset . 4)
+  (fill-column . 70))
+ (c-mode
   (c-file-style . linux))
  (c++-mode
-  (indent-tabs-mode . t)
-  (tab-width . 8)
-  (c-basic-offset . 4)
   (c-file-style . linux))
- (emacs-lisp-mode
-  (indent-tabs-mode . t)
-  (tab-width . 8))
  (shell-mode
-  (indent-tabs-mode . t)
-  (tab-width . 8)
-  (sh-basic-offset . 4)
   (sh-indentation . 4))
  )
-- 
1.7.1

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


0.11 is frozen, please update NEWS

2012-01-12 Thread Xavier Maillard
Hi,

Maybe it is inappropriate, but do you have any idea when you plan to
release the so-expected 0.11 release ? 

Anyway, keep up the good job guys !

/Xavier


[PATCH] emacs: globally replace non-branching "(if (not ..." with "(unless ..."

2012-01-12 Thread Xavier Maillard

On Thu, 12 Jan 2012 18:33:06 +0100, Pieter Praet  wrote:
> Less code, same results, without sacrificing readability.

+1

/Xavier


[PATCH] emacs: whitespace-cleanup for emacs/*.el files

2012-01-12 Thread Xavier Maillard
On Wed, 11 Jan 2012 17:13:35 +0200, Tomi Ollila  wrote:
> Executed
> for f in emacs/*.el
> do emacs -q --batch --eval \
> "(progn (find-file \"$f\") (whitespace-cleanup) (save-buffer))"
> done
> 
> which
> removed trailing whitespace and empty lines at the end of file
> removed spaces before tab (if any)
> converted 8 spaces to tabs in the beginning of line

+1

Maybe we should note something about this as a /coding style/ rule ?

/Xavier


[PATCH] emacs: Improve `notmuch-hello' display on ttys.

2012-01-11 Thread Xavier Maillard
On Tue, 10 Jan 2012 10:15:28 +, David Edmondson  wrote:
> Inserting spaces to pad out columns is good, except when the padding
> makes the line wider than the window. This looks particularly bad on a
> tty where there is no fringe.
> 
> Hence, avoid padding the last column on each row.

Works for me

/Xavier


Re: [PATCH] emacs: Improve `notmuch-hello' display on ttys.

2012-01-11 Thread Xavier Maillard
On Tue, 10 Jan 2012 10:15:28 +, David Edmondson d...@dme.org wrote:
 Inserting spaces to pad out columns is good, except when the padding
 makes the line wider than the window. This looks particularly bad on a
 tty where there is no fringe.
 
 Hence, avoid padding the last column on each row.

Works for me

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


Re: [PATCH] man: add missing SEE ALSO header to notmuch reply man page

2012-01-10 Thread Xavier Maillard

On Sun,  8 Jan 2012 22:57:22 +0200, Jani Nikula j...@nikula.org wrote:
 Signed-off-by: Jani Nikula j...@nikula.org
 ---
  man/man1/notmuch-reply.1 |3 +++
  1 files changed, 3 insertions(+), 0 deletions(-)

+1

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


[PATCH] man: add missing SEE ALSO header to notmuch reply man page

2012-01-09 Thread Xavier Maillard

On Sun,  8 Jan 2012 22:57:22 +0200, Jani Nikula  wrote:
> Signed-off-by: Jani Nikula 
> ---
>  man/man1/notmuch-reply.1 |3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)

+1

/Xavier


[PATCH] emacs: Mark the quoted region during reply.

2012-01-06 Thread Xavier Maillard

On Fri,  6 Jan 2012 10:03:40 +, David Edmondson  wrote:
> Mark the quoted region of text during a reply, making it easy for the
> user to delete it quickly.

LGTM ! (That's also a desirable feature).

/Xavier


[PATCH 2/2] update NEWS

2012-01-03 Thread Xavier Maillard
Hi,

sorry to bother with such a simple correction

On Mon,  2 Jan 2012 14:16:51 -0800, Jameson Graef Rollins  wrote:

> +Don't sort messages when creating a dump file
> +
> +  This speads up tag dumps considerably, without any loss of
  ^^
  speeds

/Xavier


Python bindings for adoption

2012-01-03 Thread Xavier Maillard
On Mon, 02 Jan 2012 17:14:58 +0100, Sebastian Spaeth  
wrote:

> As I have repeatedly stated that I want to hand over the maintainership
> of the notmuch python bindings, and I would like to do it asap. I feel
> that people like Patrick Totzke, or Justus Winter who generally have
> been working on this far more intensely than I recently did are both
> very well positioned to take on that role :-). Most importantly, they
> actually work with the bindings while I don't use them myself anymore.

Thank you very much for your work and effort much appreciated.

/Xavier


[ANNOUNCE] mutt with notmuch support

2012-01-03 Thread Xavier Maillard

On Tue, 3 Jan 2012 13:39:38 +0100, Karel Zak  wrote:
> 
> This is not another curses front-end for notmuch, this is mutt :-)
> 
> I have forked mutt to seriously integrate notmuch to this excellent e-mail
> client. I don't want to use symlinks or any other hacks to emulate virtual
> folders. My wish is mutt linked with libnotmuch.

Not sure I will ever use it but this is really an awesome news ! Good
job.

/Xavier


Re: [PATCH 1/4] emacs: unify search mechanisms

2012-01-03 Thread Xavier Maillard
On Mon, 02 Jan 2012 15:23:17 +0200, Tomi Ollila tomi.oll...@nixu.com wrote:
 On Sat, 31 Dec 2011 14:42:47 +0200, Jani Nikula j...@nikula.org wrote:
  On Fri, 30 Dec 2011 10:43:37 -0400, David Bremner da...@tethera.net wrote:
  
   Personally I would like to be able to customize the hello screen to
   remove the search box. I find it confusing that that 's' jumps to the
   search box there, and everywhere else brings up the mini-buffer. That
   might be just me, and the fact that I bind C-c s globally to
   notmuch-search.  I could easily believe that for new users having a
   search box is nicer.
  
  Would it be a suitable compromise to bind 's' to notmuch-search (the
  mini-buffer search) also in notmuch-hello, while leaving the search box
  there with a common history?
 
 I like this approach!

+1 but, like David, I'd like to be able to display/to hide the search
box via a keybinding and/or a configuration option.

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


Re: [ANNOUNCE] mutt with notmuch support

2012-01-03 Thread Xavier Maillard

On Tue, 3 Jan 2012 13:39:38 +0100, Karel Zak k...@redhat.com wrote:
 
 This is not another curses front-end for notmuch, this is mutt :-)
 
 I have forked mutt to seriously integrate notmuch to this excellent e-mail
 client. I don't want to use symlinks or any other hacks to emulate virtual
 folders. My wish is mutt linked with libnotmuch.

Not sure I will ever use it but this is really an awesome news ! Good
job.

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


Re: Python bindings for adoption

2012-01-03 Thread Xavier Maillard
On Mon, 02 Jan 2012 17:14:58 +0100, Sebastian Spaeth sebast...@sspaeth.de 
wrote:

 As I have repeatedly stated that I want to hand over the maintainership
 of the notmuch python bindings, and I would like to do it asap. I feel
 that people like Patrick Totzke, or Justus Winter who generally have
 been working on this far more intensely than I recently did are both
 very well positioned to take on that role :-). Most importantly, they
 actually work with the bindings while I don't use them myself anymore.

Thank you very much for your work and effort much appreciated.

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


Re: [PATCH 2/2] update NEWS

2012-01-03 Thread Xavier Maillard
Hi,

sorry to bother with such a simple correction

On Mon,  2 Jan 2012 14:16:51 -0800, Jameson Graef Rollins 
jroll...@finestructure.net wrote:

 +Don't sort messages when creating a dump file
 +
 +  This speads up tag dumps considerably, without any loss of
  ^^
  speeds

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


[PATCH 1/4] emacs: unify search mechanisms

2012-01-02 Thread Xavier Maillard
On Mon, 02 Jan 2012 15:23:17 +0200, Tomi Ollila  wrote:
> On Sat, 31 Dec 2011 14:42:47 +0200, Jani Nikula  wrote:
> > On Fri, 30 Dec 2011 10:43:37 -0400, David Bremner  
> > wrote:
> > 
> > > Personally I would like to be able to customize the hello screen to
> > > remove the search box. I find it confusing that that 's' jumps to the
> > > search box there, and everywhere else brings up the mini-buffer. That
> > > might be just me, and the fact that I bind "C-c s" globally to
> > > notmuch-search.  I could easily believe that for new users having a
> > > search box is nicer.
> > 
> > Would it be a suitable compromise to bind 's' to notmuch-search (the
> > mini-buffer search) also in notmuch-hello, while leaving the search box
> > there with a common history?
> 
> I like this approach!

+1 but, like David, I'd like to be able to display/to hide the search
box via a keybinding and/or a configuration option.

/Xavier


Tagging strategy and latest notmuch

2011-12-28 Thread Xavier Maillard
Hi,

my mail workflow is pretty /basic/ and /raw/. Here it is:

1a. notmuch new (for consistency sake)
1b. notmuchsync syncs from notmuch tags to my maildir flags (actually, it is to
prune is:delete tagged messages)
2. offlineimap syncs with my imap server
3. notmuch new incorporate new messages into the database
4. notmuchsync syncs from my maildirs flags to notmuch
5. (at last) a shell-script is testing/tagging all my messages corpus

This is a solution I am using for months but I am pretty sure it is not
adapted with latest notmuch. Sadly I could not follow the recent feature
additions (and reading through NEWS file or the wiki is not really
helping).

So what I am looking for is a "modern" solution to replace my current
strategy not really /scalable/ -i.e incorporating new mails is really
getting slower each day- and most importantly I really need to reduce
time taken to tag new material. Currently, my tagging script processes
all my notmuch database even if only new mails are really tagged, it has
to test each message to sort out what messages need tags; tagging only
new mail would be really awesome.

By the way, I am using 0.10.x.

Thank you

/Xavier


[PATCH] emacs: Don't attempt to colour tags in `notmuch-show-mode'.

2011-12-28 Thread Xavier Maillard
On Wed, 28 Dec 2011 12:09:40 -0800, Jameson Graef Rollins  wrote:
> On Wed, 28 Dec 2011 13:42:28 +0100, Xavier Maillard  
> wrote:
> > On Tue, 27 Dec 2011 22:29:57 -0500, Austin Clements  
> > wrote:
> > > LGTM.
> > 
> > uh, what ?
> 
> http://www.google.com/search?q=LGTM

LGTM too no :D

/Xavier


[PATCH] emacs: Don't attempt to colour tags in `notmuch-show-mode'.

2011-12-28 Thread Xavier Maillard
Hi David,

On Tue, 27 Dec 2011 16:47:14 +, David Edmondson  wrote:
> The tags were coloured using text properties. Unfortunately that text
> (the header line) also has an overlay, which overrides the text
> properties. There's not point in applying text properties that will
> never be seen.

Yet another good patch by You. I'd vote +1 for this feature.

/Xavier


[PATCH] emacs: Don't attempt to colour tags in `notmuch-show-mode'.

2011-12-28 Thread Xavier Maillard

On Tue, 27 Dec 2011 22:29:57 -0500, Austin Clements  wrote:
> LGTM.

uh, what ?

/Xavier 


[PATCH] Ignore encrypted parts when indexing.

2011-12-28 Thread Xavier Maillard
Hi Jameson,

On Tue, 27 Dec 2011 09:11:41 -0800, Jameson Graef Rollins  wrote:
> It appears to be an oversight that encrypted parts were indexed
> previously.  The terms generated from encrypted parts are meaningless
> and do nothing but add bloat to the database.  It is not worth
> indexing the encrypted content, just as it's not worth indexing the
> signatures in signed parts.

+1 for this.

But,

> + if (GMIME_IS_MULTIPART_ENCRYPTED (multipart)) {
> + /* Don't index encrypted parts. */
> + continue

This needs a semicolon, doesn't it ?

/Xavier


Re: [PATCH] emacs: Add `notmuch-show-line-faces' and apply it.

2011-12-28 Thread Xavier Maillard
Hi David,

On Tue, 27 Dec 2011 17:13:23 +, David Edmondson d...@dme.org wrote:
 Similar to `notmuch-search-line-faces', `notmuch-show-line-faces'
 allows the header line in `notmuch-show-mode' buffers to be coloured
 according to the tags of the message.

I have not tested this feature (yet). What would be useful when such
/theming feature/ is proposed is to show a before/after patch aka a
screenshot. Do you have some for this one for example ?

Have a nice day.

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


Re: [PATCH] Ignore encrypted parts when indexing.

2011-12-28 Thread Xavier Maillard
Hi Jameson,

On Tue, 27 Dec 2011 09:11:41 -0800, Jameson Graef Rollins 
jroll...@finestructure.net wrote:
 It appears to be an oversight that encrypted parts were indexed
 previously.  The terms generated from encrypted parts are meaningless
 and do nothing but add bloat to the database.  It is not worth
 indexing the encrypted content, just as it's not worth indexing the
 signatures in signed parts.

+1 for this.

But,

 + if (GMIME_IS_MULTIPART_ENCRYPTED (multipart)) {
 + /* Don't index encrypted parts. */
 + continue

This needs a semicolon, doesn't it ?

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


Re: [PATCH] emacs: Don't attempt to colour tags in `notmuch-show-mode'.

2011-12-28 Thread Xavier Maillard
On Wed, 28 Dec 2011 12:09:40 -0800, Jameson Graef Rollins 
jroll...@finestructure.net wrote:
 On Wed, 28 Dec 2011 13:42:28 +0100, Xavier Maillard xav...@maillard.im 
 wrote:
  On Tue, 27 Dec 2011 22:29:57 -0500, Austin Clements amdra...@mit.edu 
  wrote:
   LGTM.
  
  uh, what ?
 
 http://www.google.com/search?q=LGTM

LGTM too no :D

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


Tagging strategy and latest notmuch

2011-12-28 Thread Xavier Maillard
Hi,

my mail workflow is pretty /basic/ and /raw/. Here it is:

1a. notmuch new (for consistency sake)
1b. notmuchsync syncs from notmuch tags to my maildir flags (actually, it is to
prune is:delete tagged messages)
2. offlineimap syncs with my imap server
3. notmuch new incorporate new messages into the database
4. notmuchsync syncs from my maildirs flags to notmuch
5. (at last) a shell-script is testing/tagging all my messages corpus

This is a solution I am using for months but I am pretty sure it is not
adapted with latest notmuch. Sadly I could not follow the recent feature
additions (and reading through NEWS file or the wiki is not really
helping).

So what I am looking for is a modern solution to replace my current
strategy not really /scalable/ -i.e incorporating new mails is really
getting slower each day- and most importantly I really need to reduce
time taken to tag new material. Currently, my tagging script processes
all my notmuch database even if only new mails are really tagged, it has
to test each message to sort out what messages need tags; tagging only
new mail would be really awesome.

By the way, I am using 0.10.x.

Thank you

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


list of notmuch frontend

2011-12-27 Thread Xavier Maillard
On Tue, 27 Dec 2011 21:29:33 +0100, Antoine Amarilli  wrote:

> > Out of curiosity, how can people contribute to the "wiki" ? I do not see
> > any 'Edit this page' button.
> 
> It's a git repository which you can clone, edit and push back. See
>  (linked at the very bottom of
> ).

Good catch !

Thank you

/Xavier


list of notmuch frontend

2011-12-27 Thread Xavier Maillard
On Mon, 26 Dec 2011 22:12:52 +0100, Antoine Amarilli  wrote:
> On Sun, Dec 18, 2011 at 06:10:13PM +0200, Tomi Ollila wrote:
> > On Sun, 18 Dec 2011 15:34:23 +0100, Olivier Schwander  > chadok.info> wrote:
> > > Is there a somewhere a list of the various notmuch frontend ? It would
> > > be very valuable for people who are not completly happy with the main
> > > emacs frontend.
> > 
> > If not, Someone(TM) should create such a page in notmuch-wiki
> > (http://notmuchmail.org/)
> 
> I tried to be that someone. See . I did no
> effort to find more information or frontends, though.

Thank you Antoine.

Out of curiosity, how can people contribute to the "wiki" ? I do not see
any 'Edit this page' button.

Thanks

/Xavier


Re: list of notmuch frontend

2011-12-27 Thread Xavier Maillard
On Mon, 26 Dec 2011 22:12:52 +0100, Antoine Amarilli a...@a3nm.net wrote:
 On Sun, Dec 18, 2011 at 06:10:13PM +0200, Tomi Ollila wrote:
  On Sun, 18 Dec 2011 15:34:23 +0100, Olivier Schwander 
  olivier.schwan...@chadok.info wrote:
   Is there a somewhere a list of the various notmuch frontend ? It would
   be very valuable for people who are not completly happy with the main
   emacs frontend.
  
  If not, Someone(TM) should create such a page in notmuch-wiki
  (http://notmuchmail.org/)
 
 I tried to be that someone. See http://notmuchmail.org/frontends/. I did no
 effort to find more information or frontends, though.

Thank you Antoine.

Out of curiosity, how can people contribute to the wiki ? I do not see
any 'Edit this page' button.

Thanks

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


[PATCH v2] emacs: call notmuch-show instead of notmuch-search in buttonised id: links

2011-12-23 Thread Xavier Maillard
Hi David,

On Fri, 23 Dec 2011 07:48:49 +, David Edmondson  wrote:
> On Thu, 22 Dec 2011 20:59:12 -0800, Jameson Graef Rollins  finestructure.net> wrote:
> > Since message-ids necessarily match just a single message, there's no
> > reason to do a search for the id before viewing the actual message;
> > the search just becomes an extra screen to click through.  Clicking on
> > an id: links now just jumps straight to the message itself.
> 
> It's often useful to see a message in context, particularly as it's
> common for people to reference id:'s when referring to a thread (thread:
> is instance local, as I recall).
> 
> Is there a simple way from `notmuch-show' to jump out to the result of
> `notmuch-search' for the current id:? Maybe we could bind ^ to something
> like `notmuch-show-in-context'.

Why not use a prefix argument to do different thing:

C-u RET -> show in context
RET -> show single message

WDYT ?

/Xavier


[PATCH] emacs: call notmuch-show instead notmuch-search in buttonised id: links

2011-12-23 Thread Xavier Maillard
Hi Jameson,

On Thu, 22 Dec 2011 20:55:48 -0800, Jameson Graef Rollins  wrote:
> Since message-ids necessarily match just a single message, there's no
> reason to do a search for the id before viewing the actual message;
> the search just becomes an extra screen to click through.  Clicking on
> an id: links now just jumps straight to the message itself.

Definetely +1 for this patch !

/Xavier


Re: [PATCH] emacs: call notmuch-show instead notmuch-search in buttonised id: links

2011-12-23 Thread Xavier Maillard
Hi Jameson,

On Thu, 22 Dec 2011 20:55:48 -0800, Jameson Graef Rollins 
jroll...@finestructure.net wrote:
 Since message-ids necessarily match just a single message, there's no
 reason to do a search for the id before viewing the actual message;
 the search just becomes an extra screen to click through.  Clicking on
 an id: links now just jumps straight to the message itself.

Definetely +1 for this patch !

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


Re: [PATCH v2] emacs: call notmuch-show instead of notmuch-search in buttonised id: links

2011-12-23 Thread Xavier Maillard
Hi David,

On Fri, 23 Dec 2011 07:48:49 +, David Edmondson d...@dme.org wrote:
 On Thu, 22 Dec 2011 20:59:12 -0800, Jameson Graef Rollins 
 jroll...@finestructure.net wrote:
  Since message-ids necessarily match just a single message, there's no
  reason to do a search for the id before viewing the actual message;
  the search just becomes an extra screen to click through.  Clicking on
  an id: links now just jumps straight to the message itself.
 
 It's often useful to see a message in context, particularly as it's
 common for people to reference id:'s when referring to a thread (thread:
 is instance local, as I recall).
 
 Is there a simple way from `notmuch-show' to jump out to the result of
 `notmuch-search' for the current id:? Maybe we could bind ^ to something
 like `notmuch-show-in-context'.

Why not use a prefix argument to do different thing:

C-u RET - show in context
RET - show single message

WDYT ?

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


[RFC][PATCH v2] emacs: Re-implement advance/rewind functions of notmuch-show-mode.

2011-12-22 Thread Xavier Maillard
On Thu, 22 Dec 2011 09:29:55 -0500, Aaron Ecay  wrote:

> Would the problem you had with previous-s-c-prop-change be fixed by the
> patch to the original function I sent in the thread starting at
> id:"m2y5u5cykp.fsf at kcals.intra.maillard.im" ?

AFAIK it does.

/Xavier


[PATCH] emacs: fix off-by-one bug in notmuch-show-archive

2011-12-22 Thread Xavier Maillard
Hey Aaron,

On Thu, 22 Dec 2011 09:24:20 -0500, Aaron Ecay  wrote:
> Text properties change between characters; prev-s-c-property-change
> returns the position after the change.  Thus, it is still inside the
> invisible region.

This patch works for me (at least on all the messages I tested it
on). Thank you very much !

/Xavier


Filter one-post thread only ?

2011-12-22 Thread Xavier Maillard
Hi,

In order to clean up and to trash out as many posts as possible in
several mailing lists I did not check lately, I am trying to find a way
to limit the current display to messages matching this requirements:

1. post older than 1 month
2. one-message thread only (a post and no followup/answer).

Do you think this can be done ? In case you do, then how ? :D

Thank you very much.

/Xavier


[BUG?] Pressing SPACEbar is not doing what's expected.

2011-12-22 Thread Xavier Maillard
Hi Jamie,

On Wed, 21 Dec 2011 15:19:24 -0800, Jameson Graef Rollins  wrote:
> On Thu, 22 Dec 2011 00:08:38 +0100, Xavier Maillard  wrote:
> > What happens here is just what is described in paragraph 2. Although I
> > am in situation described in first paragraph, pressing SPC just advance
> > to next message and never scroll to see the next part of the current
> > message.
> 
> Hi, Xavier.  I have noticed this as well, and it's definitely a bug and
> not a feature (there's no way to change this behavior).  I think it has
> to do with there being hidden text at the end of the current message,
> and notmuch somehow assuming that it is at the end of the message when
> it's really not.

Well, the good news is that I am not alone :D At the beginning, I
thought it was me.

> This issue has actually been addressed once, with a patch in fact [0].
> However, somehow my patch to split the "and-archive" bit out of the
> notmuch-show-advance-and-archive function [1] seems to have exposed a
> problem.

I hope you (notmuch hackers) will find a solution to this bug.

Take care guys and thank you for such an awesome tool !

/Xavier


[BUG?] Pressing SPACEbar is not doing what's expected.

2011-12-22 Thread Xavier Maillard
Hi,

I recently upgraded my notmuch installation here (passing from 0.6 or
such to latest 0.10.x series).

Problem is now, pressing SPACE in a notmuch-show buffer no longer scroll
in the message as it used to do.

SPC is bound to run command notmuch-show-advance-and-archive and its
docstring says:

This command is intended to be one of the simplest ways to
process a thread of email. It does the following:

If the current message in the thread is not yet fully visible,
scroll by a near screenful to read more of the message.

Otherwise, (the end of the current message is already within the
current window), advance to the next open message.

Finally, if there is no further message to advance to, and this
last message is already read, then archive the entire current
thread, (remove the "inbox" tag from each message). Also kill
this buffer, and display the next thread from the search from
which this thread was originally shown.

What happens here is just what is described in paragraph 2. Although I
am in situation described in first paragraph, pressing SPC just advance
to next message and never scroll to see the next part of the current
message.

How can I change this behaviour ? Does I need to do something in my
.emacs file ?

Thank you very much.

/Xavier


Filter one-post thread only ?

2011-12-22 Thread Xavier Maillard
Hi,

In order to clean up and to trash out as many posts as possible in
several mailing lists I did not check lately, I am trying to find a way
to limit the current display to messages matching this requirements:

1. post older than 1 month
2. one-message thread only (a post and no followup/answer).

Do you think this can be done ? In case you do, then how ? :D

Thank you very much.

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


Re: [PATCH] emacs: fix off-by-one bug in notmuch-show-archive

2011-12-22 Thread Xavier Maillard
Hey Aaron,

On Thu, 22 Dec 2011 09:24:20 -0500, Aaron Ecay aarone...@gmail.com wrote:
 Text properties change between characters; prev-s-c-property-change
 returns the position after the change.  Thus, it is still inside the
 invisible region.

This patch works for me (at least on all the messages I tested it
on). Thank you very much !

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


Re: [RFC][PATCH v2] emacs: Re-implement advance/rewind functions of notmuch-show-mode.

2011-12-22 Thread Xavier Maillard
On Thu, 22 Dec 2011 09:29:55 -0500, Aaron Ecay aarone...@gmail.com wrote:

 Would the problem you had with previous-s-c-prop-change be fixed by the
 patch to the original function I sent in the thread starting at
 id:m2y5u5cykp@kcals.intra.maillard.im ?

AFAIK it does.

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


[BUG?] Pressing SPACEbar is not doing what's expected.

2011-12-21 Thread Xavier Maillard
Hi,

I recently upgraded my notmuch installation here (passing from 0.6 or
such to latest 0.10.x series).

Problem is now, pressing SPACE in a notmuch-show buffer no longer scroll
in the message as it used to do.

SPC is bound to run command notmuch-show-advance-and-archive and its
docstring says:

This command is intended to be one of the simplest ways to
process a thread of email. It does the following:

If the current message in the thread is not yet fully visible,
scroll by a near screenful to read more of the message.

Otherwise, (the end of the current message is already within the
current window), advance to the next open message.

Finally, if there is no further message to advance to, and this
last message is already read, then archive the entire current
thread, (remove the inbox tag from each message). Also kill
this buffer, and display the next thread from the search from
which this thread was originally shown.

What happens here is just what is described in paragraph 2. Although I
am in situation described in first paragraph, pressing SPC just advance
to next message and never scroll to see the next part of the current
message.

How can I change this behaviour ? Does I need to do something in my
.emacs file ?

Thank you very much.

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


Re: [BUG?] Pressing SPACEbar is not doing what's expected.

2011-12-21 Thread Xavier Maillard
Hi Jamie,

On Wed, 21 Dec 2011 15:19:24 -0800, Jameson Graef Rollins 
jroll...@finestructure.net wrote:
 On Thu, 22 Dec 2011 00:08:38 +0100, Xavier Maillard x...@gnu.org wrote:
  What happens here is just what is described in paragraph 2. Although I
  am in situation described in first paragraph, pressing SPC just advance
  to next message and never scroll to see the next part of the current
  message.
 
 Hi, Xavier.  I have noticed this as well, and it's definitely a bug and
 not a feature (there's no way to change this behavior).  I think it has
 to do with there being hidden text at the end of the current message,
 and notmuch somehow assuming that it is at the end of the message when
 it's really not.

Well, the good news is that I am not alone :D At the beginning, I
thought it was me.

 This issue has actually been addressed once, with a patch in fact [0].
 However, somehow my patch to split the and-archive bit out of the
 notmuch-show-advance-and-archive function [1] seems to have exposed a
 problem.

I hope you (notmuch hackers) will find a solution to this bug.

Take care guys and thank you for such an awesome tool !

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


RFC/PATCH emacs attachment handling

2011-09-07 Thread Xavier Maillard
Hello Tomi,

On Wed, 07 Sep 2011 10:06:36 +0300, Tomi Ollila  wrote:
> On Wed 07 Sep 2011 04:20, Mark Walters  writes:
> 
> > Hello
> >
> > I have modified the emacs interface for handling attachments by adding
> > a keymap to the attachment button. For example pressing v when on an
> > attachment button views the attachment (using the mailcap method) and
> > pressing s saves the attachment. I find this makes it a lot easier
> > when dealing with message with lots of attachments.
> 
> In my gnus (haven't got rid the latest one, yet ;) :
> 
> Pressing ENTER (RET) on top of text/html content: w3m-safe-view-this-url
> Pressing ENTER (RET) on top of text content: widget-button-press
> Pressing ENTER (RET) on top of an attachment: gnus-article-press-button
> 
> Pressing 'o' on top of text executes: gnus-summary-save-article
> Pressing 'o' on top of an attachment: gnus-mime-save-part
> 
> To user that is:
> 
> Pressing Enter on top of an attachment will either show the attachment on
> buffer (in case there is 'converter' defined) or offer to save the
> attachment. Pressing 'o' on top of an attachment will always offer to save
> the attachment.

I really do not like it this behaviour. I'd rather want easy to memorize
keybindings: 'v'iew,'s'ave, etc.

-- X=M=A


SlackBuild package for notmuch 0.7

2011-09-07 Thread Xavier Maillard
Hi,

On Sun, 04 Sep 2011 19:15:56 +0200, Jostein Berntsen  
wrote:
> 
> I have made a SlackBuild package for notmuch version 0.7 that makes it 
> easy to install it the correct way in Slackware 13.37:

Thank you very much Jostein !

-- X=M=A


Re: SlackBuild package for notmuch 0.7

2011-09-07 Thread Xavier Maillard
Hi,

On Sun, 04 Sep 2011 19:15:56 +0200, Jostein Berntsen jber...@broadpark.no 
wrote:
 
 I have made a SlackBuild package for notmuch version 0.7 that makes it 
 easy to install it the correct way in Slackware 13.37:

Thank you very much Jostein !

-- X=M=A
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: RFC/PATCH emacs attachment handling

2011-09-07 Thread Xavier Maillard
Hello Tomi,

On Wed, 07 Sep 2011 10:06:36 +0300, Tomi Ollila tomi.oll...@iki.fi wrote:
 On Wed 07 Sep 2011 04:20, Mark Walters markwalters1...@gmail.com writes:
 
  Hello
 
  I have modified the emacs interface for handling attachments by adding
  a keymap to the attachment button. For example pressing v when on an
  attachment button views the attachment (using the mailcap method) and
  pressing s saves the attachment. I find this makes it a lot easier
  when dealing with message with lots of attachments.
 
 In my gnus (haven't got rid the latest one, yet ;) :
 
 Pressing ENTER (RET) on top of text/html content: w3m-safe-view-this-url
 Pressing ENTER (RET) on top of text content: widget-button-press
 Pressing ENTER (RET) on top of an attachment: gnus-article-press-button
 
 Pressing 'o' on top of text executes: gnus-summary-save-article
 Pressing 'o' on top of an attachment: gnus-mime-save-part
 
 To user that is:
 
 Pressing Enter on top of an attachment will either show the attachment on
 buffer (in case there is 'converter' defined) or offer to save the
 attachment. Pressing 'o' on top of an attachment will always offer to save
 the attachment.

I really do not like it this behaviour. I'd rather want easy to memorize
keybindings: 'v'iew,'s'ave, etc.

-- X=M=A
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


[PATCH 2/2] add edit function to resume postponed emails

2011-07-22 Thread Xavier Maillard
On Thu, 21 Jul 2011 14:58:22 -0700, Jameson Graef Rollins  wrote:
> On Thu, 21 Jul 2011 23:32:58 +0200, Xavier Maillard  
> wrote:
> > Maybe I misunderstood original goal but what I had in mind reading this
> > is certainly not editing a priviously received message in order to
> > (re)send it again but sending a postponed/draft message which, I guess,
> > means no full header(s) (no received header and such and probably
> > partially filled header, if any).
> 
> Hey, Xavier.  I was just responding to Antoine's comment that he had
> "trouble making message-mode digest an existing buffer".

Oh well, sorry then ;)

/Xavier


[PATCH 2/2] add edit function to resume postponed emails

2011-07-22 Thread Xavier Maillard
Hi Jameson,

On Wed, 20 Jul 2011 14:40:44 -0700, Jameson Graef Rollins  wrote:
> On Wed, 20 Jul 2011 17:36:43 -0400, Antoine Beaupr?  
> wrote:
> > I think this is a great idea. Unfortunately, I had a lot of trouble
> > making message-mode digest an existing buffer. For example, if you take
> > any existing buffer and call (message-mode) on it, you will notice it
> > will clear the buffer completely.
> 
> Hey, Antoine.  Is this really true?  It seems to work for me.  For
> instance, if I view a received message raw ('V') I can then "C-x
> message-mode" on that buffer and it creates a partially filled, although
> not properly formatted, message.

Maybe I misunderstood original goal but what I had in mind reading this
is certainly not editing a priviously received message in order to
(re)send it again but sending a postponed/draft message which, I guess,
means no full header(s) (no received header and such and probably
partially filled header, if any).

On the other hand, doing just something like:

C-x mail RET M-x text-mode RET M-x message-mode RET

does no harm to the buffer content as far as I can tell thus, I guess
amdragon suggestion is by far, the best compromise.

/Xavier


Re: [PATCH 2/2] add edit function to resume postponed emails

2011-07-22 Thread Xavier Maillard
On Thu, 21 Jul 2011 14:58:22 -0700, Jameson Graef Rollins 
jroll...@finestructure.net wrote:
 On Thu, 21 Jul 2011 23:32:58 +0200, Xavier Maillard xav...@maillard.im 
 wrote:
  Maybe I misunderstood original goal but what I had in mind reading this
  is certainly not editing a priviously received message in order to
  (re)send it again but sending a postponed/draft message which, I guess,
  means no full header(s) (no received header and such and probably
  partially filled header, if any).
 
 Hey, Xavier.  I was just responding to Antoine's comment that he had
 trouble making message-mode digest an existing buffer.

Oh well, sorry then ;)
 
/Xavier
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


Re: [PATCH 2/2] add edit function to resume postponed emails

2011-07-21 Thread Xavier Maillard
Hi Jameson,

On Wed, 20 Jul 2011 14:40:44 -0700, Jameson Graef Rollins 
jroll...@finestructure.net wrote:
 On Wed, 20 Jul 2011 17:36:43 -0400, Antoine Beaupré anar...@koumbit.org 
 wrote:
  I think this is a great idea. Unfortunately, I had a lot of trouble
  making message-mode digest an existing buffer. For example, if you take
  any existing buffer and call (message-mode) on it, you will notice it
  will clear the buffer completely.
 
 Hey, Antoine.  Is this really true?  It seems to work for me.  For
 instance, if I view a received message raw ('V') I can then C-x
 message-mode on that buffer and it creates a partially filled, although
 not properly formatted, message.

Maybe I misunderstood original goal but what I had in mind reading this
is certainly not editing a priviously received message in order to
(re)send it again but sending a postponed/draft message which, I guess,
means no full header(s) (no received header and such and probably
partially filled header, if any).

On the other hand, doing just something like:

C-x mail RET M-x text-mode RET M-x message-mode RET

does no harm to the buffer content as far as I can tell thus, I guess
amdragon suggestion is by far, the best compromise.

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


[PATCH] fix sum moar typos

2011-06-05 Thread Xavier Maillard
Hi Pieter,

On Sat,  4 Jun 2011 17:54:12 +0200, Pieter Praet  wrote:
> Because they cause global warming.
> 
> Signed-off-by: Pieter Praet 
> ---
> 
> TL;DR: Various typo fixes. Applies to jrollins/release-candidate/0.6 
> (2baf08f5)
> 
> Due to the impending 0.6 release, I've gone off on an ephemeral typo hunt,
> and have brought back some trophies.
> 
> As it's such an utterly amusing passtime, I've been pretty fat-fingered about 
> it,
> and wouldn't be surprised if I've missed some, or even made some new ones.
> 
> Nonetheless: Lets maek 0.6 purrfec!

Yaeh !

/Xavier

P.S: good job !


[PATCH] Added C-up and C-down to cycle through previous searches

2011-06-05 Thread Xavier Maillard
Hi,

On Sun, 29 May 2011 20:04:00 +0400, Dmitry Kurochkin  wrote:
> Hi Dima.
> 
> On Sun, 29 May 2011 01:56:28 -0700, notmuch at dima.secretsauce.net wrote:
> > From: Dima Kogan 
> > 
> > ---
> > 
> >  Hi.
> > 
> >  I made a few improvements to the emacs UI. This patch allows the user to 
> > scroll
> >  through the most recent searches with C-up and C-down while in the search 
> > box.
> > 
> 
> This sounds like a very nice improvement to me!  I just have one
> concern: Why C-up and C-down?  I believe M-p and M-n would be more
> natural for Emacs users (at least for me :)).

+1. M-p/M-n is way simpler to remember for me too. IMO, that should be
setq'able at the user level to suit best users preferences.

/Xavier


Re: [PATCH] Added C-up and C-down to cycle through previous searches

2011-06-05 Thread Xavier Maillard
Hi,

On Sun, 29 May 2011 20:04:00 +0400, Dmitry Kurochkin 
dmitry.kuroch...@gmail.com wrote:
 Hi Dima.
 
 On Sun, 29 May 2011 01:56:28 -0700, notm...@dima.secretsauce.net wrote:
  From: Dima Kogan d...@secretsauce.net
  
  ---
  
   Hi.
  
   I made a few improvements to the emacs UI. This patch allows the user to 
  scroll
   through the most recent searches with C-up and C-down while in the search 
  box.
  
 
 This sounds like a very nice improvement to me!  I just have one
 concern: Why C-up and C-down?  I believe M-p and M-n would be more
 natural for Emacs users (at least for me :)).

+1. M-p/M-n is way simpler to remember for me too. IMO, that should be
setq'able at the user level to suit best users preferences.

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


Re: [PATCH] fix sum moar typos

2011-06-05 Thread Xavier Maillard
Hi Pieter,

On Sat,  4 Jun 2011 17:54:12 +0200, Pieter Praet pie...@praet.org wrote:
 Because they cause global warming.
 
 Signed-off-by: Pieter Praet pie...@praet.org
 ---
 
 TL;DR: Various typo fixes. Applies to jrollins/release-candidate/0.6 
 (2baf08f5)
 
 Due to the impending 0.6 release, I've gone off on an ephemeral typo hunt,
 and have brought back some trophies.
 
 As it's such an utterly amusing passtime, I've been pretty fat-fingered about 
 it,
 and wouldn't be surprised if I've missed some, or even made some new ones.
 
 Nonetheless: Lets maek 0.6 purrfec!

Yaeh !

/Xavier

P.S: good job !
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


When will we have our next release?

2011-06-04 Thread Xavier Maillard
Hi,

On Sat, 04 Jun 2011 10:21:00 -0300, David Bremner  wrote:

> Overall I think Carl's time based release proposal is a reasonable
> plan. I think one problem we've been having is that we seem to have lost
> track of 
> 
> # Releases of notmuch have a two-digit version (0.1, 0.2, etc.). We
> # increment the second digit for each release and increment the first
> # digit when we reach particularly major milestones of usability.
> 
> In short, I think we are make too big of a deal out of releases. Looking
> at the log between 0.5 and now, there are features enough to justify
> several minor releases.

Or even major ! Frankly, this project has grew up quite quickly and
features are implemented at a really good rythm. The sole problem is
that it is really hard to see how far we are from a release and what
exactly has been cooked up since latest release (from my point of view).

> On Fri, 03 Jun 2011 15:56:42 -0700, Carl Worth  wrote:
> > 
> > Frankly, I wouldn't mind doing strict time-based releases with something
> > like the following:
> > 
> > * We schedule a release period (once per month?)
> 
> I think every two months might be a bit more comfortable, but then
> again, 1 month would keep us from "making a big deal out of releases."

Best before choosing the frequency is probably to try doing this a few
times and be comfortable with the process. If after a few releases
-i.e. say 3- the more we can do is release every trimester so do it.

The process should be simple (and will be I guess) and the most
difficult part is probably to document every aspect of every changes in
the NEWS file (with eventually a good shaped manual ;)).

> > * We schedule a "safety period" before the release (one week?)
> > * At the beginning of the safety period, package up the head
> >   of the notmuch tree and upload to Debian experimental and
> >   anywhere else similar.
> 
> Sure. I don't mind doing that part, at least for Debian.  I'm going to
> try to do at roughly weekly uploads to Debian experimental. Hopefully
> this will get some critical mass of users testing those versions.

I know it is a bit off topic here but just a question: how will you deal
with dependencies ? I mean, when we need GMime vX.Y.Z and Debian has
already vX.V.W ?

/Xavier


When will we have our next release?

2011-06-04 Thread Xavier Maillard
Hi Carl,

On Fri, 03 Jun 2011 15:56:42 -0700, Carl Worth  wrote:
> On Fri, 03 Jun 2011 14:39:13 -0700, Jameson Graef Rollins  finestructure.net> wrote:
> > Can we set a target date for 0.6 release?  So we'll all start feeling
> > really bad if we miss it?
> 
> Frankly, I wouldn't mind doing strict time-based releases with something
> like the following:
> 
>   * We schedule a release period (once per month?)

That sounds reasonable to me. You could even do it less frequently
-i.e. every 2 month.

>   * At the beginning of the safety period, package up the head
>   of the notmuch tree and upload to Debian experimental and
>   anywhere else similar.

I like this idea. I already have slackware packages for notmuch and
that's the way I prefer testing notmuch since I am not really
comfortable with the git machinery (I wish I could do something for
notmuch though).

> So switching to a more strictly time-based cycle can definitely help,
> (so many other projects use time-based releases very successfully).

+1. THat's pretty frustating to contemplate all those patches/source
code sent to this list and not being able to "test" them :)

Whatever we choose, keep up the good work guys !

/Xavier


Re: When will we have our next release?

2011-06-04 Thread Xavier Maillard
Hi Carl,

On Fri, 03 Jun 2011 15:56:42 -0700, Carl Worth cwo...@cworth.org wrote:
 On Fri, 03 Jun 2011 14:39:13 -0700, Jameson Graef Rollins 
 jroll...@finestructure.net wrote:
  Can we set a target date for 0.6 release?  So we'll all start feeling
  really bad if we miss it?
 
 Frankly, I wouldn't mind doing strict time-based releases with something
 like the following:
 
   * We schedule a release period (once per month?)

That sounds reasonable to me. You could even do it less frequently
-i.e. every 2 month.
 
   * At the beginning of the safety period, package up the head
   of the notmuch tree and upload to Debian experimental and
   anywhere else similar.

I like this idea. I already have slackware packages for notmuch and
that's the way I prefer testing notmuch since I am not really
comfortable with the git machinery (I wish I could do something for
notmuch though).
  
 So switching to a more strictly time-based cycle can definitely help,
 (so many other projects use time-based releases very successfully).

+1. THat's pretty frustating to contemplate all those patches/source
code sent to this list and not being able to test them :)
 
Whatever we choose, keep up the good work guys !

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


Re: When will we have our next release?

2011-06-04 Thread Xavier Maillard
Hi,

On Sat, 04 Jun 2011 10:21:00 -0300, David Bremner brem...@unb.ca wrote:

 Overall I think Carl's time based release proposal is a reasonable
 plan. I think one problem we've been having is that we seem to have lost
 track of 
 
 # Releases of notmuch have a two-digit version (0.1, 0.2, etc.). We
 # increment the second digit for each release and increment the first
 # digit when we reach particularly major milestones of usability.
 
 In short, I think we are make too big of a deal out of releases. Looking
 at the log between 0.5 and now, there are features enough to justify
 several minor releases.

Or even major ! Frankly, this project has grew up quite quickly and
features are implemented at a really good rythm. The sole problem is
that it is really hard to see how far we are from a release and what
exactly has been cooked up since latest release (from my point of view).
 
 On Fri, 03 Jun 2011 15:56:42 -0700, Carl Worth cwo...@cworth.org wrote:
  
  Frankly, I wouldn't mind doing strict time-based releases with something
  like the following:
  
  * We schedule a release period (once per month?)
 
 I think every two months might be a bit more comfortable, but then
 again, 1 month would keep us from making a big deal out of releases.

Best before choosing the frequency is probably to try doing this a few
times and be comfortable with the process. If after a few releases
-i.e. say 3- the more we can do is release every trimester so do it.

The process should be simple (and will be I guess) and the most
difficult part is probably to document every aspect of every changes in
the NEWS file (with eventually a good shaped manual ;)).

  * We schedule a safety period before the release (one week?)
  * At the beginning of the safety period, package up the head
of the notmuch tree and upload to Debian experimental and
anywhere else similar.
 
 Sure. I don't mind doing that part, at least for Debian.  I'm going to
 try to do at roughly weekly uploads to Debian experimental. Hopefully
 this will get some critical mass of users testing those versions.

I know it is a bit off topic here but just a question: how will you deal
with dependencies ? I mean, when we need GMime vX.Y.Z and Debian has
already vX.V.W ?

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


[RFC] Several minor enhancements to the Emacs interface

2011-05-31 Thread Xavier Maillard
Hi Thomas,

On Tue, 31 May 2011 16:47:27 +0200, Thomas Jost  
wrote:
> Hi list,
> 
> The thread regarding multiple sender identities seems to have been of
> interest for several people, so I'd like to share a few other snippets
> From my Emacs configuration file.
> 
> Please tell me what you think of them. If you like them, I'd be glad to
> write some patches so they can be merged in notmuch.

Just send patch cause I think that all that stuff could be quite useful.

Anyway thank you.

/Xavier


  1   2   3   >