Le 28 juin 2012 ? 18:21 CEST, Jameson Graef Rollins a ?crit :
> On Thu, Jun 28 2012, Philip Hands wrote:
>> Actually, instead of either of these options, how about some way of
>> letting r do the single reply, and then once inside the reply, having
>> some key binding to add the rest of the
Le 28 juin 2012 à 18:21 CEST, Jameson Graef Rollins a écrit :
On Thu, Jun 28 2012, Philip Hands p...@hands.com wrote:
Actually, instead of either of these options, how about some way of
letting r do the single reply, and then once inside the reply, having
some key binding to add the rest of
Introduce a new defcustom notmuch-mua-compose-in that allows users to
specify where new mails are composed, either in the current window or
in a new window or frame.
Signed-off-by: Jameson Rollins
---
Hi David et al.,
Here it is again, with a warning in the customize message that only
appears
Introduce a new defcustom notmuch-mua-compose-in that allows users to
specify where new mails are composed, either in the current window or
in a new window or frame.
Signed-off-by: Jameson Rollins jroll...@finestructure.net
---
Hi David et al.,
Here it is again, with a warning in the customize
Le 15 avril 2012 ? 16:52 CEST, David Bremner a ?crit :
> Jameson Graef Rollins writes:
>
>> I think the issues that David was experiencing have to do with flakiness
>> in emacs's dedicated windows, not in this patch itself.
>
> Thomas,
>
> Did you have a change to investigate this as proposed in
Le 15 avril 2012 à 16:52 CEST, David Bremner a écrit :
Jameson Graef Rollins jroll...@finestructure.net writes:
I think the issues that David was experiencing have to do with flakiness
in emacs's dedicated windows, not in this patch itself.
Thomas,
Did you have a change to investigate this
gmime 2.6 had a bug [1] which made it impossible to tell why a signature
verification failed when the signer key was unavailable (empty sigstatus field
in the JSON output). Since 00b5623d the corresponding test is marked as broken
when using gmime 2.6 (2.4 is fine).
The bug has been fixed in
gmime-2.6 had a bug [1] which made it impossible to tell why a signature
verification failed when the signer key was unavailable (empty sigstatus field
in the JSON output). Since 00b5623d the corresponding test is marked as broken
when using gmime-2.6 (2.4 is fine).
This bug has been fixed in
On Thu, 16 Feb 2012 11:45:10 -0500, Philippe LeCavalier wrote:
> Hi.
>
> I get this[1] when envoking keybindings to a second language
> flyspell. Any ideas? I've already tried alternate titles to reference
> the dictionary in question ie french, francais and fran?ais to no avail.
>
> Also, how
On Thu, 16 Feb 2012 11:45:10 -0500, Philippe LeCavalier
supp...@plecavalier.com wrote:
Hi.
I get this[1] when envoking keybindings to a second language
flyspell. Any ideas? I've already tried alternate titles to reference
the dictionary in question ie french, francais and français to no
On Wed, 25 Jan 2012 11:45:03 +, David Edmondson wrote:
> `mail-header-parse-address' expects un-decoded mailbox parts, which is
> not what we have at this point. Replace it with simple string
> deconstruction.
>
> Mark the corresponding test as no longer broken.
>
> Minor whitespace
Previous version had a typo ("they may be" instead of "there may be")
and was lacking a proper description of the gmime bug.
---
Argh. Did not know how to tell it in proper English, ended with a huge
typo. Sorry about that, and thanks for noticing and fixing it :)
NEWS |4 ++--
1 files
JSON does not support hex literals (0x..) so numbers must be formatted
as %d instead of %x.
Currently, the possible values for the gmime error code are 1 (expired
signature), 2 (no public key), 4 (expired key) and 8 (revoked key).
The other possible value is 16 (unsupported algorithm) but
JSON does not support hex literals (0x..) so numbers must be formatted
as %d instead of %x.
Currently, the possible values for the gmime error code are 1 (expired
signature), 2 (no public key), 4 (expired key) and 8 (revoked key).
The other possible value is 16 (unsupported algorithm) but
Previous version had a typo (they may be instead of there may be)
and was lacking a proper description of the gmime bug.
---
Argh. Did not know how to tell it in proper English, ended with a huge
typo. Sorry about that, and thanks for noticing and fixing it :)
NEWS |4 ++--
1 files changed,
On Fri, 20 Jan 2012 07:55:03 -0400, David Bremner wrote:
> On Fri, 20 Jan 2012 10:39:23 +0100, Thomas Jost
> wrote:
> > JSON does not support hex literals (0x..) so numbers must be formatted as %d
> > instead of %x.
> > ---
> > notmuch-show.c |2 +-
> >
---
INSTALL | 12 ++--
NEWS|9 +
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/INSTALL b/INSTALL
index e51b397..bc98f1d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -20,8 +20,8 @@ configure stage.
Dependencies
-Notmuch depends on three
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:"8762i8hrb9.fsf at bookbinder.fernseed.info".
This was tested against
JSON does not support hex literals (0x..) so numbers must be formatted as %d
instead of %x.
---
notmuch-show.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index d14dac9..91f566c 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@
On Thu, 19 Jan 2012 23:10:44 -0500, Austin Clements wrote:
> Nearly there. A few more small comments.
Thanks again :) Will post new version soon, including a new patch to
update NEWS and INSTALL.
> Quoth Thomas Jost on Jan 20 at 1:06 am:
> > There are lots of API changes in gmim
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:"8762i8hrb9.fsf at bookbinder.fernseed.info".
This was tested against
JSON does not support hex literals (0x..) so numbers must be formatted as %d
instead of %x.
---
notmuch-show.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index d14dac9..91f566c 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@
7453-9405-2-git-send-email-schnouki at schnouki.net"
[3] https://bugzilla.gnome.org/show_bug.cgi?id=668085
Thomas Jost (2):
show: don't use hex literals in JSON output
Add compatibility with gmime 2.6
mime-node.c | 60 +++--
not
On Tue, 17 Jan 2012 15:38:36 -0500, Austin Clements wrote:
> Quoth Thomas Jost on Jan 17 at 11:48 am:
> > On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements
> > wrote:
> > > Quoth Thomas Jost on Jan 17 at 12:56 am:
> > > > This is mostly based on id:"8
On Wed, 18 Jan 2012 20:00:12 +0200, Tomi Ollila wrote:
> On Wed, 18 Jan 2012 12:19:45 -0500, Tom Prince
> wrote:
> >
> > How did you test against multiple versions? Using different machines? If
> > there was a way for configure (or something to pick the version, I would
> > setup the buildbot
On Wed, 18 Jan 2012 12:35:34 -0500, Austin Clements wrote:
> Quoth Tomi Ollila on Jan 18 at 10:15 am:
> > On Tue, 17 Jan 2012 17:25:46 -0500, Austin Clements
> > wrote:
> > > Quoth Thomas Jost on Jan 17 at 11:50 am:
> > > >
> > > > +#ifdef
Thanks for this review Austin. New version coming soon.
On Tue, 17 Jan 2012 17:25:46 -0500, Austin Clements wrote:
> Quoth Thomas Jost on Jan 17 at 11:50 am:
> > There are lots of API changes in gmime 2.6 crypto handling. By adding
> > preprocessor directives, it is however possib
On Thu, 19 Jan 2012 23:10:44 -0500, Austin Clements amdra...@mit.edu wrote:
Nearly there. A few more small comments.
Thanks again :) Will post new version soon, including a new patch to
update NEWS and INSTALL.
Quoth Thomas Jost on Jan 20 at 1:06 am:
There are lots of API changes in gmime
JSON does not support hex literals (0x..) so numbers must be formatted as %d
instead of %x.
---
notmuch-show.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index d14dac9..91f566c 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:8762i8hrb9@bookbinder.fernseed.info.
This was tested against both
---
INSTALL | 12 ++--
NEWS|9 +
2 files changed, 15 insertions(+), 6 deletions(-)
diff --git a/INSTALL b/INSTALL
index e51b397..bc98f1d 100644
--- a/INSTALL
+++ b/INSTALL
@@ -20,8 +20,8 @@ configure stage.
Dependencies
-Notmuch depends on three
On Fri, 20 Jan 2012 07:55:03 -0400, David Bremner da...@tethera.net wrote:
On Fri, 20 Jan 2012 10:39:23 +0100, Thomas Jost schno...@schnouki.net wrote:
JSON does not support hex literals (0x..) so numbers must be formatted as %d
instead of %x.
---
notmuch-show.c |2 +-
1 files
Thanks for this review Austin. New version coming soon.
On Tue, 17 Jan 2012 17:25:46 -0500, Austin Clements amdra...@mit.edu wrote:
Quoth Thomas Jost on Jan 17 at 11:50 am:
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible
On Wed, 18 Jan 2012 20:00:12 +0200, Tomi Ollila tomi.oll...@iki.fi wrote:
On Wed, 18 Jan 2012 12:19:45 -0500, Tom Prince tom.pri...@ualberta.net
wrote:
How did you test against multiple versions? Using different machines? If
there was a way for configure (or something to pick the
On Tue, 17 Jan 2012 15:38:36 -0500, Austin Clements amdra...@mit.edu wrote:
Quoth Thomas Jost on Jan 17 at 11:48 am:
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements amdra...@mit.edu
wrote:
Quoth Thomas Jost on Jan 17 at 12:56 am:
This is mostly based on id:8762i8hrb9
-email-schno...@schnouki.net
[3] https://bugzilla.gnome.org/show_bug.cgi?id=668085
Thomas Jost (2):
show: don't use hex literals in JSON output
Add compatibility with gmime 2.6
mime-node.c | 60 +++--
notmuch-client.h | 30 +++-
notmuch-reply.c
JSON does not support hex literals (0x..) so numbers must be formatted as %d
instead of %x.
---
notmuch-show.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index d14dac9..91f566c 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:8762i8hrb9@bookbinder.fernseed.info.
This was tested against both
On Tue, 17 Jan 2012 14:48:34 +0200, Tomi Ollila wrote:
> On Tue, 17 Jan 2012 11:50:53 +0100, Thomas Jost
> wrote:
> > There are lots of API changes in gmime 2.6 crypto handling. By adding
> > preprocessor directives, it is however possible to add gmime 2.6
> >
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:"8762i8hrb9.fsf at bookbinder.fernseed.info".
This was tested against
JSON does not support hex literals (0x..) so numbers must be formatted as %d
instead of %x.
---
notmuch-show.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index d14dac9..91f566c 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements wrote:
> Quoth Thomas Jost on Jan 17 at 12:56 am:
> > There are lots of API changes in gmime 2.6 crypto handling. By adding
> > preprocessor directives, it is however possible to add gmime 2.6
> > compatibility
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:"8762i8hrb9.fsf at bookbinder.fernseed.info".
This was tested against
On Mon, 16 Jan 2012 22:47:14 -0500, Austin Clements amdra...@mit.edu wrote:
Quoth Thomas Jost on Jan 17 at 12:56 am:
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6
compatibility
while preserving
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:8762i8hrb9@bookbinder.fernseed.info.
This was tested against both
JSON does not support hex literals (0x..) so numbers must be formatted as %d
instead of %x.
---
notmuch-show.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index d14dac9..91f566c 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@
On Tue, 17 Jan 2012 14:48:34 +0200, Tomi Ollila tomi.oll...@iki.fi wrote:
On Tue, 17 Jan 2012 11:50:53 +0100, Thomas Jost schno...@schnouki.net wrote:
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6
There are lots of API changes in gmime 2.6 crypto handling. By adding
preprocessor directives, it is however possible to add gmime 2.6 compatibility
while preserving compatibility with gmime 2.4 too.
This is mostly based on id:8762i8hrb9@bookbinder.fernseed.info.
This was tested against both
On Sun, 08 Jan 2012 13:59:30 +0100, Sebastian Spaeth
wrote:
> On Thu, 05 Jan 2012 16:04:22 +0100, Thomas Jost
> wrote:
> > There's a description of the DB "schema" in lib/database.cc in the
> > notmuch source code. But you may also consider just using libnotmuch
&
On Sun, 08 Jan 2012 13:59:30 +0100, Sebastian Spaeth sebast...@sspaeth.de
wrote:
On Thu, 05 Jan 2012 16:04:22 +0100, Thomas Jost schno...@schnouki.net wrote:
There's a description of the DB schema in lib/database.cc in the
notmuch source code. But you may also consider just using libnotmuch
On Sun, 25 Dec 2011 23:54:41 -0500, Aaron Ecay wrote:
> On Thu, 15 Dec 2011 19:50:36 -0400, David Bremner
> wrote:
> > I think the problem is related to emacsclient.
> >
> > With 'm' I have the following behaviour:
> >
> > emacs -q --daemon
> > M-x notmuch (to load variable definitions)
> >
On Thu, 5 Jan 2012 16:38:07 +0100, boyska wrote:
> > There's a description of the DB "schema" in lib/database.cc in the
> > notmuch source code. But you may also consider just using libnotmuch
> > instead, if that's enough for what you want to do.
>
> thanks, found it, much clearer now.
> But I
On Wed, 04 Jan 2012 15:49:19 +, boyska wrote:
> Hello!
> I like notmuch a lot, so I'm writing a (conceptually) similar software
> about addressbook: it will scan all your emails, storing email
> addresses
> in a xapian database (you can think of it as little brother database[1]
> on
>
On Wed, 04 Jan 2012 15:49:19 +, boyska piutto...@logorroici.org wrote:
Hello!
I like notmuch a lot, so I'm writing a (conceptually) similar software
about addressbook: it will scan all your emails, storing email
addresses
in a xapian database (you can think of it as little brother
On Thu, 5 Jan 2012 16:38:07 +0100, boyska piutto...@logorroici.org wrote:
There's a description of the DB schema in lib/database.cc in the
notmuch source code. But you may also consider just using libnotmuch
instead, if that's enough for what you want to do.
thanks, found it, much clearer
---
Hello world,
Here's my part. (Also describes Ivy Foster's patch for notmuch-hello-mode-hook.)
Regards,
Thomas
NEWS | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/NEWS b/NEWS
index 6650126..8a3ff5a 100644
--- a/NEWS
+++ b/NEWS
@@ -34,6 +34,25 @@
---
Hello world,
Here's my part. (Also describes Ivy Foster's patch for notmuch-hello-mode-hook.)
Regards,
Thomas
NEWS | 19 +++
1 files changed, 19 insertions(+), 0 deletions(-)
diff --git a/NEWS b/NEWS
index 6650126..8a3ff5a 100644
--- a/NEWS
+++ b/NEWS
@@ -34,6 +34,25 @@
On Thu, 22 Dec 2011 01:54:21 +0400, Dmitry Kurochkin wrote:
> On Wed, 21 Dec 2011 22:49:13 +0100, Thomas Jost
> wrote:
> > On Wed, 21 Dec 2011 22:18:26 +0400, Dmitry Kurochkin > gmail.com> wrote:
> > > Test that `notmuch-hello-refresh-hook' is called once when
>
On Tue, 20 Dec 2011 15:20:04 +, David Edmondson wrote:
> Cast away the result of various *write functions. Provide a default
> value for some variables to avoid "use before set" warnings.
> ---
>
> The buildbot complains about these, though my own system (Debian
> testing on amd64) does not.
On Wed, 21 Dec 2011 22:18:26 +0400, Dmitry Kurochkin wrote:
> Test that `notmuch-hello-refresh-hook' is called once when
> `notmuch-hello' is called and twice when calling
> `notmuch-hello-update' after that.
>
> The tests are very similar to tests for `notmuch-hello-mode-hook'.
Quite nice,
This had been discussed and decided on IRC.
Rationale:
Therefore the space is recommended in the SI/ISO 31-0 standard, and the
International Bureau of Weights and Measures states that "for numbers with
many digits the digits may be divided into groups of three by a thin space, in
order to
In 123,456.78, "." is the decimal separator, but "," is the thousands separator.
---
emacs/notmuch-hello.el |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index f892ff7..ef585ea 100644
--- a/emacs/notmuch-hello.el
+++
Test that it's called once when `notmuch-hello' is called, and twice when
calling `notmuch-hello-update' after that.
---
Here it is. No broken subtest first since the first patch was already pushed
though.
Regards,
Thomas
test/emacs | 23 +++
1 files changed, 23
This hook is called every time a notmuch-hello buffer is updated.
---
Oops, the previous patch had a typo which prevented it to work (":group notmuch"
instead of ":group 'notmuch"). Sorry about that.
emacs/notmuch-hello.el |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff
ll be overwritten by the remote one, period. It
should also work with more than 2 hosts (but not tested yet). No sync
data is kept in the notmuch DB.
Right now all of this fits in about 250 lines of Python (could be made
shorter) and works quite well for me. I'll put it online after doing
some cleanup.
On Wed, 14 Dec 2011 14:54:10 -0700, Mark Anderson
wrote:
> On Tue, 13 Dec 2011 11:11:42 -0600, Thomas Jost
> wrote:
> > This is a time_t value, similar to the message date (TIMESTAMP). It is
> > first set
> > when the message is added to the database, and is then updat
On Fri, 16 Dec 2011 16:34:03 +0400, Dmitry Kurochkin wrote:
> On Fri, 16 Dec 2011 08:29:00 -0400, David Bremner
> wrote:
> > On Fri, 16 Dec 2011 04:59:22 +0400, Dmitry Kurochkin > gmail.com> wrote:
> > >
> > > What do perople think about making the thousands separator a space by
> > >
This hook is called every time a notmuch-hello buffer is updated.
---
Hi Dmitry,
I like the idea of having a -mode-hook and a -refresh-hook :) Thanks for your
suggestions!
Regards,
Thomas
emacs/notmuch-hello.el |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git
Test that it's called once when `notmuch-hello' is called, and twice when
calling `notmuch-hello-update' after that.
---
Here it is. No broken subtest first since the first patch was already pushed
though.
Regards,
Thomas
test/emacs | 23 +++
1 files changed, 23
In 123,456.78, . is the decimal separator, but , is the thousands separator.
---
emacs/notmuch-hello.el |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index f892ff7..ef585ea 100644
--- a/emacs/notmuch-hello.el
+++
This had been discussed and decided on IRC.
Rationale:
Therefore the space is recommended in the SI/ISO 31-0 standard, and the
International Bureau of Weights and Measures states that for numbers with
many digits the digits may be divided into groups of three by a thin space, in
order to
On Wed, 21 Dec 2011 22:18:26 +0400, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
Test that `notmuch-hello-refresh-hook' is called once when
`notmuch-hello' is called and twice when calling
`notmuch-hello-update' after that.
The tests are very similar to tests for
On Tue, 20 Dec 2011 15:20:04 +, David Edmondson d...@dme.org wrote:
Cast away the result of various *write functions. Provide a default
value for some variables to avoid use before set warnings.
---
The buildbot complains about these, though my own system (Debian
testing on amd64) does
On Thu, 22 Dec 2011 01:54:21 +0400, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
On Wed, 21 Dec 2011 22:49:13 +0100, Thomas Jost schno...@schnouki.net wrote:
On Wed, 21 Dec 2011 22:18:26 +0400, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
Test that `notmuch-hello-refresh-hook
This hook is called every time a notmuch-hello buffer is updated.
---
Hi Dmitry,
I like the idea of having a -mode-hook and a -refresh-hook :) Thanks for your
suggestions!
Regards,
Thomas
emacs/notmuch-hello.el |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git
On Fri, 16 Dec 2011 16:34:03 +0400, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
On Fri, 16 Dec 2011 08:29:00 -0400, David Bremner da...@tethera.net wrote:
On Fri, 16 Dec 2011 04:59:22 +0400, Dmitry Kurochkin
dmitry.kuroch...@gmail.com wrote:
What do perople think about making
On Wed, 14 Dec 2011 14:54:10 -0700, Mark Anderson markr.ander...@amd.com
wrote:
On Tue, 13 Dec 2011 11:11:42 -0600, Thomas Jost schno...@schnouki.net wrote:
This is a time_t value, similar to the message date (TIMESTAMP). It is
first set
when the message is added to the database
.
Right now all of this fits in about 250 lines of Python (could be made
shorter) and works quite well for me. I'll put it online after doing
some cleanup.
Quoth Thomas Jost on Dec 13 at 6:11 pm:
This is a time_t value, similar to the message date (TIMESTAMP). It is
first set
when the message
This hook is called every time a notmuch-hello buffer is updated.
---
Oops, the previous patch had a typo which prevented it to work (:group notmuch
instead of :group 'notmuch). Sorry about that.
emacs/notmuch-hello.el |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff
binutils-2.22 changes the behaviour of ld by defaulting to
--no-copy-dt-needed-entries, which means that required objects/libs are not
indirectly linked through intermediate objects/libs anymore. As a consequence,
when using binutils-2.22, building symbol-test fails with the following error:
This hook is called every time the notmuch-hello buffer is updated.
---
emacs/notmuch-hello.el |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/emacs/notmuch-hello.el b/emacs/notmuch-hello.el
index 0fe9c1d..112b40b 100644
--- a/emacs/notmuch-hello.el
+++
In 123,456.78, "." is the decimal separator, but "," is the thousands separator.
This commit also mentions the space being used as thousands separator in several
European countries.
---
emacs/notmuch-hello.el |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git
Commit cb841878 introduced new parts handlers for crypto parts, but also
hardcoded values for their headers face. This replaces these hardcoded values
with a customizable face.
---
emacs/notmuch-crypto.el |5 +
emacs/notmuch-show.el |4 ++--
2 files changed, 7 insertions(+), 2
Reusing the current window to compose a new mail may be troublesome for the
user. This patch introduces a new customizable variable, notmuch-mua-compose-in,
which lets the user choose where to create the mail buffer: in the current
window (current and default behaviour), in a new window, or in a
Thomas Jost (4):
emacs: Let the user choose where to compose new mails
emacs: Add a face for crypto parts headers
emacs: rename notmuch-decimal-separator to
notmuch-thousands-separator
emacs: add notmuch-hello-hook
emacs/notmuch-crypto.el |5 +
emacs/notmuch-hello.el | 17
Commit 567bcbc2 introduced two new values for each message (content of the
From and Subject headers), but the comments about the database schema had
not been updated accordingly.
---
lib/database.cc |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/lib/database.cc
with a range syntax.
- the fourth commit adds the MTIME to the JSON output of notmuch show.
- the fifth and last commit adds Message.get_mtime() to the Python
bindings.
Please tell me what you think of this.
Best regards,
Thomas
Thomas Jost (5):
Fix comments about what is stored in the database
This is a time_t value, similar to the message date (TIMESTAMP). It is first set
when the message is added to the database, and is then updated every time a tag
is added or removed. It can thus be used for doing incremental dumps of the
database or for synchronizing it between several computers.
Tag modification times are now searchable as ranges (just like regular message
dates) with the mtime: prefix.
---
lib/database-private.h |1 +
lib/database.cc|3 +++
notmuch.1 | 14 --
notmuch.c | 13 ++---
4 files changed, 26
This could be used by a UI implementation somehow.
---
notmuch-show.c |7 ---
1 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/notmuch-show.c b/notmuch-show.c
index 873a7c4..7279601 100644
--- a/notmuch-show.c
+++ b/notmuch-show.c
@@ -202,17 +202,18 @@ format_message_json
---
bindings/python/notmuch/message.py | 20
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/bindings/python/notmuch/message.py
b/bindings/python/notmuch/message.py
index ce8e718..56f56c2 100644
--- a/bindings/python/notmuch/message.py
+++
Thomas Jost (4):
emacs: Let the user choose where to compose new mails
emacs: Add a face for crypto parts headers
emacs: rename notmuch-decimal-separator to
notmuch-thousands-separator
emacs: add notmuch-hello-hook
emacs/notmuch-crypto.el |5 +
emacs/notmuch-hello.el | 17
Reusing the current window to compose a new mail may be troublesome for the
user. This patch introduces a new customizable variable, notmuch-mua-compose-in,
which lets the user choose where to create the mail buffer: in the current
window (current and default behaviour), in a new window, or in a
In 123,456.78, . is the decimal separator, but , is the thousands separator.
This commit also mentions the space being used as thousands separator in several
European countries.
---
emacs/notmuch-hello.el |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git
Commit cb841878 introduced new parts handlers for crypto parts, but also
hardcoded values for their headers face. This replaces these hardcoded values
with a customizable face.
---
emacs/notmuch-crypto.el |5 +
emacs/notmuch-show.el |4 ++--
2 files changed, 7 insertions(+), 2
Some distros (Arch Linux) ship Python as python2 and Python 3 as python.
Checking for python2 is necessary for the Python tests to work on these
platforms.
---
test/test-lib.sh |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/test/test-lib.sh b/test/test-lib.sh
The new test_python() function makes writing Python tests a little easier:
- it sets the environment variables as needed
- it redirects stdout to the OUTPUT file (like test_emacs()).
This commit also declares python as an external prereq.
The stdout redirection is required to avoid trouble when
Some distros (Arch Linux) ship Python as python2 and Python 3 as python.
Checking for python2 is necessary for the Python tests to work on these
platforms.
---
test/test-lib.sh |9 -
1 files changed, 8 insertions(+), 1 deletions(-)
diff --git a/test/test-lib.sh b/test/test-lib.sh
The new test_python() function makes writing Python tests a little easier:
- it sets the environment variables as needed
- it redirects stdout to the OUTPUT file (like test_emacs()).
This commit also declares python as an external prereq.
The stdout redirection is required to avoid trouble when
Now that types are checked correctly, we also need to make sure that all the
arguments actually are instances of these types. Otherwise the function calls
will fail and raise an exception similar to this one:
ctypes.ArgumentError: argument 3: : expected
LP_LP_NotmuchMessageS instance instead
1 - 100 of 224 matches
Mail list logo
