Message.get_property (prop) returns a string with the value of the property and
Message.get_properties (prop, exact=False) yields key, value pairs
---
bindings/python/docs/source/message.rst | 4 ++
bindings/python/notmuch/globals.py | 5 +++
bindings/python/notmuch/message.py | 80 +++
Message.get_property (prop) returns a string with the value of the property and
Message.get_properties (prop, exact=False) yields key, value pairs
---
bindings/python/docs/source/message.rst | 4 ++
bindings/python/notmuch/globals.py | 5 +++
bindings/python/notmuch/message.py | 80 +++
Message.get_property (prop) returns a string with the value of the property and
Message.get_properties (prop, exact=False) yields key, value pairs
---
bindings/python/docs/source/message.rst | 4 ++
bindings/python/notmuch/globals.py | 5 +++
bindings/python/notmuch/message.py | 80 +++
Message.get_property (prop) returns a string with the value of the property and
Message.get_properties (prop, exact=False) returns a list [(key, value)]
---
bindings/python/notmuch/globals.py | 5 +++
bindings/python/notmuch/message.py | 81 +-
2 files changed,
Message.get_property (prop) returns a string with the value of the property and
Message.get_properties (prop, exact=False) returns a list [(key, value)]
---
bindings/python/notmuch/globals.py | 5 +++
bindings/python/notmuch/message.py | 78 +-
2 files changed,
Message.get_property (prop) returns a string with the value of the property.
---
bindings/python/notmuch/message.py | 27 ++-
1 file changed, 26 insertions(+), 1 deletion(-)
diff --git a/bindings/python/notmuch/message.py
b/bindings/python/notmuch/message.py
index d5b98e4
two different gpg keys (key1 and key2), and I set
'encrypt-to key1' when I send emails with my identity of key2 it will also
encrypt it with my key1 and will reveal to its receivers that I own key1. Isn't
it?
--
Ruben Pollan | http://meskio.net/
-=-=-=-=-=-
two different gpg keys (key1 and key2), and I set
'encrypt-to key1' when I send emails with my identity of key2 it will also
encrypt it with my key1 and will reveal to its receivers that I own key1. Isn't
it?
--
Ruben Pollan | http://meskio.net/
-=-=-=-=-=-
es it as you say with your own public gpg key.
I think we should open an issue about in the alot github tracker:
https://github.com/pazz/alot/issues
Can you do it?
--
Ruben Pollan | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net/crypto.txt
-=
as you say with your own public gpg key.
I think we should open an issue about in the alot github tracker:
https://github.com/pazz/alot/issues
Can you do it?
--
Ruben Pollan | http://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: http://meskio.net/crypto.txt
-=
Quoting Patrick Totzke (2013-07-19 17:14:07)
> > Sadly that is not what I see. I'm trying to read an email that mutt reports
> > as PGP/MIME but the content appear blank.
>
> Is is possible that this mail's body is ctype 'text/html' and you haven't set
> up
> your mailcap for html (as in FAQ #5
Quoting Patrick Totzke (2013-07-19 16:02:34)
> Hi Rub?n,
>
> thanks for mentioning this. I must have accidentally dropped the
> corresponding paragraph
> in the docs
> (http://alot.readthedocs.org/en/testing/usage/index.html#cryptography).
> I'm almost certain I saw this documented a while back.
Hello pazz,
Quoting Patrick Totzke (2013-07-18 11:21:24)
> Most notably, this update comes with a rewrite of Thread buffers,
> allowing among other things thread-tree based focus movements.
> Alot now has full support for PGP/MIME encryption and signatures,
> courtesy of Justus (teythoon). Apart f
Quoting Patrick Totzke (2013-07-19 17:14:07)
> > Sadly that is not what I see. I'm trying to read an email that mutt reports
> > as PGP/MIME but the content appear blank.
>
> Is is possible that this mail's body is ctype 'text/html' and you haven't set
> up
> your mailcap for html (as in FAQ #5
Quoting Patrick Totzke (2013-07-19 16:02:34)
> Hi Rubén,
>
> thanks for mentioning this. I must have accidentally dropped the
> corresponding paragraph
> in the docs
> (http://alot.readthedocs.org/en/testing/usage/index.html#cryptography).
> I'm almost certain I saw this documented a while back.
Hello pazz,
Quoting Patrick Totzke (2013-07-18 11:21:24)
> Most notably, this update comes with a rewrite of Thread buffers,
> allowing among other things thread-tree based focus movements.
> Alot now has full support for PGP/MIME encryption and signatures,
> courtesy of Justus (teythoon). Apart f
Quoting Svend Sorensen (2013-03-06 19:40:19)
> Jameson Graef Rollins writes:
> > PS: if anyone has any suggestions for Bayesian classifiers better than
> > sa I'm all ears. I'm not so happy with sa at the moment.
>
> I used bogofilter when I was hosting my own email, and I was happy with
> it.
Quoting Svend Sorensen (2013-03-06 19:40:19)
> Jameson Graef Rollins writes:
> > PS: if anyone has any suggestions for Bayesian classifiers better than
> > sa I'm all ears. I'm not so happy with sa at the moment.
>
> I used bogofilter when I was hosting my own email, and I was happy with
> it.
As a way to learn javascript I'm experimenting with the idea of a notmuch based
webmail. You can see the dummy demo I did at:
https://gitorious.org/notwebmail
It's far from a proper webmail, you can only search and see your email but not
write or modify tags.
Yesterday on the irc Beamer told me
As a way to learn javascript I'm experimenting with the idea of a notmuch based
webmail. You can see the dummy demo I did at:
https://gitorious.org/notwebmail
It's far from a proper webmail, you can only search and see your email but not
write or modify tags.
Yesterday on the irc Beamer told me
On 21:27, Wed 01 Dec 10, Joel Borggr?n-Franck wrote:
> From: Joel Borggr?n-Franck
>
> Change #!/bin/bash at start of tests to "#!/usr/bin/env bash". That way
> systems running on bash < 4 can prepend bash >= 4 to path before
> running the tests.
Is there any reason to use bash? Is the test syste
On 21:27, Wed 01 Dec 10, Joel Borggrén-Franck wrote:
> From: Joel Borggrén-Franck
>
> Change #!/bin/bash at start of tests to "#!/usr/bin/env bash". That way
> systems running on bash < 4 can prepend bash >= 4 to path before
> running the tests.
Is there any reason to use bash? Is the test syste
On 00:27, Sun 21 Nov 10, Michal Sojka wrote:
> Ruben's previous patch fixed the problem that he experienced, but it
> also caused the test "Removing info from filename leaves tags unchanged"
> to fail. This is an attempt to make all tests to pass.
>
> The Ruben's change is restricted to be only ef
On 00:27, Sun 21 Nov 10, Michal Sojka wrote:
> Ruben's previous patch fixed the problem that he experienced, but it
> also caused the test "Removing info from filename leaves tags unchanged"
> to fail. This is an attempt to make all tests to pass.
>
> The Ruben's change is restricted to be only ef
On 05:04, Thu 11 Nov 10, Carl Worth wrote:
> Thanks to work by Michal, and a few followups by me, I'm now happy to
> report that the patches for synchronizing tags with maildir flags are
> now pushed out to the master branch.
Nice to see that, I was waiting for this feature since a while.
I only
On 05:04, Thu 11 Nov 10, Carl Worth wrote:
> Thanks to work by Michal, and a few followups by me, I'm now happy to
> report that the patches for synchronizing tags with maildir flags are
> now pushed out to the master branch.
Nice to see that, I was waiting for this feature since a while.
I only
On 14:35, Tue 23 Mar 10, Michal Sojka wrote:
> On Tue, 23 Mar 2010, Ruben Pollan wrote:
> > On 16:39, Thu 18 Mar 10, Michal Sojka wrote:
> > > This mailstore allows bi-directional synchronization between maildir
> > > flags and certain tags. The flag-to-tag map
On 16:39, Thu 18 Mar 10, Michal Sojka wrote:
> Signed-off-by: Michal Sojka
> ---
> test/t0006-maildir.sh | 113
> +
> test/test-lib.sh |7 ++-
> 2 files changed, 118 insertions(+), 2 deletions(-)
> create mode 100755 test/t0006-maildir.s
On 16:39, Thu 18 Mar 10, Michal Sojka wrote:
> This mailstore allows bi-directional synchronization between maildir
> flags and certain tags. The flag-to-tag mapping is defined by flag2tag
> array.
I'm trying it, the synchronization from my maildir to notmuch seems to work fine
except for the "unr
On 14:35, Tue 23 Mar 10, Michal Sojka wrote:
> On Tue, 23 Mar 2010, Ruben Pollan wrote:
> > On 16:39, Thu 18 Mar 10, Michal Sojka wrote:
> > > This mailstore allows bi-directional synchronization between maildir
> > > flags and certain tags. The flag-to-tag map
On 16:39, Thu 18 Mar 10, Michal Sojka wrote:
> Signed-off-by: Michal Sojka
> ---
> test/t0006-maildir.sh | 113
> +
> test/test-lib.sh |7 ++-
> 2 files changed, 118 insertions(+), 2 deletions(-)
> create mode 100755 test/t0006-maildir.s
On 16:39, Thu 18 Mar 10, Michal Sojka wrote:
> This mailstore allows bi-directional synchronization between maildir
> flags and certain tags. The flag-to-tag mapping is defined by flag2tag
> array.
I'm trying it, the synchronization from my maildir to notmuch seems to work fine
except for the "unr
On 21:07, Sun 21 Mar 10, Sebastian Spaeth wrote:
> On Sat, 20 Mar 2010 11:23:20 +0100, Ruben Pollan
> wrote:
> >
> > Adds support to reverse iteration on messages, threads and tags. To revew
> > and
> > think if makes sense to include them on notmuch or wait until
On 22:35, Sat 20 Mar 10, Jesse Rosenthal wrote:
> There was some talk on IRC ages ago about using notmuch as an
> address-book for tab-completion in emacs message mode. Thanks to some
> great recent work (Ingmar Vanhassel's shared lib and Sebastians's
> cnotmuch python lib) I have been able to take
On 21:07, Sun 21 Mar 10, Sebastian Spaeth wrote:
> On Sat, 20 Mar 2010 11:23:20 +0100, Ruben Pollan
> wrote:
> >
> > Adds support to reverse iteration on messages, threads and tags. To revew
> > and
> > think if makes sense to include them on notmuch or wait until
On 22:35, Sat 20 Mar 10, Jesse Rosenthal wrote:
> There was some talk on IRC ages ago about using notmuch as an
> address-book for tab-completion in emacs message mode. Thanks to some
> great recent work (Ingmar Vanhassel's shared lib and Sebastians's
> cnotmuch python lib) I have been able to take
Added the functions notmuch_threads_move_to_prevoius,
notmuch_threads_move_to_last and notmuch_threads_move_to_first to
notmuch library. With them is possible to iterate backwards on threads.
* notmuch_threads_move_to_prevoius do the opposite than
notmuch_threads_move_to_next, getting the threa
The logic of notmuch_threads_move_to_next iterator was on
notmuch_threads_valid function. Now notmuch_threads_valid just check if
the iterator is valid and is notmuch_threads_move_to_next wich actually
update the iterator.
---
lib/query.cc | 54 ++-
I send again the patches 3 and 4, beacuse I found a bug on them. The previous
implementation did a segfault when the search didn't have results.
Added the functions notmuch_threads_move_to_prevoius,
notmuch_threads_move_to_last and notmuch_threads_move_to_first to
notmuch library. With them is possible to iterate backwards on threads.
* notmuch_threads_move_to_prevoius do the opposite than
notmuch_threads_move_to_next, getting the threa
The logic of notmuch_threads_move_to_next iterator was on
notmuch_threads_valid function. Now notmuch_threads_valid just check if
the iterator is valid and is notmuch_threads_move_to_next wich actually
update the iterator.
---
lib/query.cc | 54 ++-
I send again the patches 3 and 4, beacuse I found a bug on them. The previous
implementation did a segfault when the search didn't have results.
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Added the functions notmuch_tags_move_to_prevoius,
notmuch_tags_move_to_last and notmuch_tags_move_to_first to notmuch
library. With them is possible to iterate backwards on tags.
* notmuch_tags_move_to_prevoius do the opposite than
notmuch_tags_move_to_next, getting the tags iterator one
pos
Added the functions notmuch_threads_move_to_prevoius,
notmuch_threads_move_to_last and notmuch_threads_move_to_first to
notmuch library. With them is possible to iterate backwards on threads.
* notmuch_threads_move_to_prevoius do the opposite than
notmuch_threads_move_to_next, getting the threa
The logic of notmuch_threads_move_to_next iterator was on
notmuch_threads_valid function. Now notmuch_threads_valid just check if
the iterator is valid and is notmuch_threads_move_to_next wich actually
update the iterator.
---
lib/query.cc | 47 ---
1
Added the functions notmuch_messages_move_to_prevoius,
notmuch_messages_move_to_last and notmuch_messages_move_to_first to
notmuch library. With them is possible to iterate backwards on messages.
* notmuch_messages_move_to_prevoius do the opposite than
notmuch_messages_move_to_next, getting the
The messages list now have pointers to previous nodes, so it is possible
to iterate backwards.
---
lib/messages.c| 18 +-
lib/notmuch-private.h |3 ++-
lib/thread.cc |4 ++--
3 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/lib/messages.c b/
Adds support to reverse iteration on messages, threads and tags. To revew and
think if makes sense to include them on notmuch or wait until they have a real
use.
The patch 3 "Move the logic of threads iterator out of 'valid'" is just a
reorganization of the code, I think it makes sense to includ
Added the functions notmuch_tags_move_to_prevoius,
notmuch_tags_move_to_last and notmuch_tags_move_to_first to notmuch
library. With them is possible to iterate backwards on tags.
* notmuch_tags_move_to_prevoius do the opposite than
notmuch_tags_move_to_next, getting the tags iterator one
pos
The logic of notmuch_threads_move_to_next iterator was on
notmuch_threads_valid function. Now notmuch_threads_valid just check if
the iterator is valid and is notmuch_threads_move_to_next wich actually
update the iterator.
---
lib/query.cc | 47 ---
1
Added the functions notmuch_threads_move_to_prevoius,
notmuch_threads_move_to_last and notmuch_threads_move_to_first to
notmuch library. With them is possible to iterate backwards on threads.
* notmuch_threads_move_to_prevoius do the opposite than
notmuch_threads_move_to_next, getting the threa
Added the functions notmuch_messages_move_to_prevoius,
notmuch_messages_move_to_last and notmuch_messages_move_to_first to
notmuch library. With them is possible to iterate backwards on messages.
* notmuch_messages_move_to_prevoius do the opposite than
notmuch_messages_move_to_next, getting the
The messages list now have pointers to previous nodes, so it is possible
to iterate backwards.
---
lib/messages.c| 18 +-
lib/notmuch-private.h |3 ++-
lib/thread.cc |4 ++--
3 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/lib/messages.c b/
Adds support to reverse iteration on messages, threads and tags. To revew and
think if makes sense to include them on notmuch or wait until they have a real
use.
The patch 3 "Move the logic of threads iterator out of 'valid'" is just a
reorganization of the code, I think it makes sense to includ
On 09:36, Tue 09 Mar 10, Carl Worth wrote:
> So the final proposal for iteration in either direction is:
>
> move_to_first
> valid
> move_to_next
>
> move_to_last
> valid
> move_to_previous
>
> get
Fine for me.
> I've just pushed commits chan
On 09:36, Tue 09 Mar 10, Carl Worth wrote:
> So the final proposal for iteration in either direction is:
>
> move_to_first
> valid
> move_to_next
>
> move_to_last
> valid
> move_to_previous
>
> get
Fine for me.
> I've just pushed commits chan
On 07:56, Sun 21 Feb 10, martin f krafft wrote:
> also sprach Ruben Pollan [2010.02.19.2112 +0100]:
> > > 1. will there be a usable ncurses or mutt version that supports
> > > notmuch anytime soon?
> >
> > I started to work on that I while ago. I didn't
On 07:56, Sun 21 Feb 10, martin f krafft wrote:
> also sprach Ruben Pollan [2010.02.19.2112 +0100]:
> > > 1. will there be a usable ncurses or mutt version that supports
> > > notmuch anytime soon?
> >
> > I started to work on that I while ago. I didn't
I started to code something base on your idea of a notmuch daemon. You can find
it on:
git://gitorious.org/notsomuch/notmuch.git
On the server branch.
The idea is to use unix named sockets to intercomunicate between the daemon and
the
client. And threads on the server to handle every request. The
On 17:49, Fri 19 Feb 10, Arian Kuschki wrote:
> 1. will there be a usable ncurses or mutt version that supports notmuch
> anytime soon?
I started to work on that I while ago. I didn't hack on it for a while, but I
hope I'll return to it soon. Anyway to create a proper good client is a lot of
wor
I started to code something base on your idea of a notmuch daemon. You can find
it on:
git://gitorious.org/notsomuch/notmuch.git
On the server branch.
The idea is to use unix named sockets to intercomunicate between the daemon and
the
client. And threads on the server to handle every request. The
On 17:49, Fri 19 Feb 10, Arian Kuschki wrote:
> 1. will there be a usable ncurses or mutt version that supports notmuch
> anytime soon?
I started to work on that I while ago. I didn't hack on it for a while, but I
hope I'll return to it soon. Anyway to create a proper good client is a lot of
wor
On 14:41, Fri 08 Jan 10, micah anderson wrote:
> On Fri, 8 Jan 2010 10:21:21 +0100, Ruben Pollan
> wrote:
> > On 15:56, Fri 08 Jan 10, martin f krafft wrote:
> > > How about indexing GPG-encrypted messages?
> >
> > I think that would be security hole. You s
On 14:41, Fri 08 Jan 10, micah anderson wrote:
> On Fri, 8 Jan 2010 10:21:21 +0100, Ruben Pollan wrote:
> > On 15:56, Fri 08 Jan 10, martin f krafft wrote:
> > > How about indexing GPG-encrypted messages?
> >
> > I think that would be security hole. You shou
On 15:56, Fri 08 Jan 10, martin f krafft wrote:
> How about indexing GPG-encrypted messages?
I think that would be security hole. You should not store the encrypted messages
on a decrypted database. A solution whould be to encrypt as well the xapian DB,
but I think is too complex for the use.
You
On 15:56, Fri 08 Jan 10, martin f krafft wrote:
> How about indexing GPG-encrypted messages?
I think that would be security hole. You should not store the encrypted messages
on a decrypted database. A solution whould be to encrypt as well the xapian DB,
but I think is too complex for the use.
You
On 11:39, Tue 05 Jan 10, Carl Worth wrote:
> Right. So example code using this would be:
>
> for (notmuch_messages_to_first (messages);
> notmuch_messages_has_current (messages);
> notmuch_messages_to_next (messages))
> {
> notmuch_message_t *mes
On 11:39, Tue 05 Jan 10, Carl Worth wrote:
> Right. So example code using this would be:
>
> for (notmuch_messages_to_first (messages);
> notmuch_messages_has_current (messages);
> notmuch_messages_to_next (messages))
> {
> notmuch_message_t *mes
On 19:16, Mon 21 Dec 09, Carl Worth wrote:
> On Mon, 21 Dec 2009 17:23:55 -0800, Carl Worth wrote:
> > New function Corresponds to existing function (if any)
> > -
> > move_to_first
> > has_next
On 19:16, Mon 21 Dec 09, Carl Worth wrote:
> On Mon, 21 Dec 2009 17:23:55 -0800, Carl Worth wrote:
> > New function Corresponds to existing function (if any)
> > -
> > move_to_first
> > has_next
ke it handles nicely the .foo.bar directories
so I can do searches for "folder:foo" and for "folder:bar".
Reviewed-by: Ruben Pollan
On 14:21, Mon 14 Dec 09, Andreas Kl?ckner wrote:
> I've patched notmuch to retain information on which folder emails are stored
>
ke it handles nicely the .foo.bar directories
so I can do searches for "folder:foo" and for "folder:bar".
Reviewed-by: Ruben Pollan
On 14:21, Mon 14 Dec 09, Andreas Klöckner wrote:
> I've patched notmuch to retain information on which folder emails are stored
> in. This
On 14:27, Thu 03 Dec 09, Carl Worth wrote:
> A simple solution would be a notmuch daemon that can accept commands on
> stdin, (in basically the exact same form as the current notmuch
> command-line interface). If the daemon does the job of periodically
> incorporating new mail, then the only comman
On 14:21, Wed 09 Dec 09, Mark Anderson wrote:
> advance/retreat
Jeffrey already suggested retreat. I let you (English speakers) decide, my
English
level is not enough for it.
--
Rub?n Poll?n | jabber:meskio at jabber.org
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
?sta es la historia de un
On 12:08, Wed 09 Dec 09, Carl Worth wrote:
> On Wed, 9 Dec 2009 14:24:46 +0100, Ruben Pollan
> wrote:
> > Do you like to call them regress? Should I change that?
>
> I don't love the name, (since it's so close to the word "regression"
> which has a tota
true when the limit is reached. But I think it make sense like
that.
On 14:10, Wed 09 Dec 09, Ruben Pollan wrote:
> Added the functions notmuch_tags_regress and notmuch_tags_is_first to
> notmuch library. With them is possible to iterate backwards on tags.
>
[...]
--
Rub?n Poll?n | jabb
On 14:27, Thu 03 Dec 09, Carl Worth wrote:
> A simple solution would be a notmuch daemon that can accept commands on
> stdin, (in basically the exact same form as the current notmuch
> command-line interface). If the daemon does the job of periodically
> incorporating new mail, then the only comman
On 14:21, Wed 09 Dec 09, Mark Anderson wrote:
> advance/retreat
Jeffrey already suggested retreat. I let you (English speakers) decide, my
English
level is not enough for it.
--
Rubén Pollán | jabber:mes...@jabber.org
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Ésta es la historia de una s
On 12:08, Wed 09 Dec 09, Carl Worth wrote:
> On Wed, 9 Dec 2009 14:24:46 +0100, Ruben Pollan wrote:
> > Do you like to call them regress? Should I change that?
>
> I don't love the name, (since it's so close to the word "regression"
> which has a totally
Added the functions notmuch_tags_regress and notmuch_tags_is_first to
notmuch library. With them is possible to iterate backwards on tags.
* notmuch_tags_regress do the opposite than notmuch_tags_advance,
getting the tags iterator one position backwards.
* notmuch_tags_is_first return TRUE if t
Added the functions notmuch_threads_regress and notmuch_threads_is_first to
notmuch library. With them is possible to iterate backwards on threads.
* notmuch_threads_regress do the opposite than notmuch_threads_advance,
getting the threads iterator one position backwards.
* notmuch_threads_is_f
true when the limit is reached. But I think it make sense like
that.
On 14:10, Wed 09 Dec 09, Ruben Pollan wrote:
> Added the functions notmuch_tags_regress and notmuch_tags_is_first to
> notmuch library. With them is possible to iterate backwards on tags.
>
[...]
--
Rubén Pollán | j
Added the functions notmuch_tags_regress and notmuch_tags_is_first to
notmuch library. With them is possible to iterate backwards on tags.
* notmuch_tags_regress do the opposite than notmuch_tags_advance,
getting the tags iterator one position backwards.
* notmuch_tags_is_first return TRUE if t
Added the functions notmuch_threads_regress and notmuch_threads_is_first to
notmuch library. With them is possible to iterate backwards on threads.
* notmuch_threads_regress do the opposite than notmuch_threads_advance,
getting the threads iterator one position backwards.
* notmuch_threads_is_f
Attached to this email I add a small code that use this functions, as an
example.
On 10:41, Tue 08 Dec 09, meskio at sindominio.net wrote:
> Two patches for implement the regress functions on messages. With them
> notmuch_messages_t can be use as an iterator forwards and backwards.
>
> Up to now
Attached to this email I add a small code that use this functions, as an
example.
On 10:41, Tue 08 Dec 09, mes...@sindominio.net wrote:
> Two patches for implement the regress functions on messages. With them
> notmuch_messages_t can be use as an iterator forwards and backwards.
>
> Up to now no
On 19:57, Fri 27 Nov 09, Carl Worth wrote:
> (I'd like a verb that pairs better
> with "advance" than the non-verb "back"---any suggestions)?
What about regress?
I'm not a native English speaker, so maybe someone can suggest something better.
> So those won't need any new code. The one case that
On 19:57, Fri 27 Nov 09, Carl Worth wrote:
> (I'd like a verb that pairs better
> with "advance" than the non-verb "back"---any suggestions)?
What about regress?
I'm not a native English speaker, so maybe someone can suggest something better.
> So those won't need any new code. The one case that
On 10:30, Thu 26 Nov 09, Carl Worth wrote:
> I'm glad to see work like this going on. If you do decide to keep going
> with it at all, I'd be glad to add this to contrib. I'm happy to have
> all kinds of different interfaces available.
Ok, I'll see what I'm doing about it in the future. Right now
Is it possible to implement notmuch_threads_back and notmuch_messages_back?
And I guess will make sense to have also notmuch_tags_back.
This functions will do the oposite than notmuch_threads_advance and
notmuch_messages_advance. So I can use them as iterators going back and forward.
I didn't che
On 11:17, Wed 25 Nov 09, Carl Worth wrote:
> And for the authors of the other interfaces, let us know when you've got
> similar support for streaming searches, (or if you didn't get this
> automatically as soon as "notmuch search" was fixed).
Yes, actually is faster now.
I had to rewrite some of
Is it possible to implement notmuch_threads_back and notmuch_messages_back?
And I guess will make sense to have also notmuch_tags_back.
This functions will do the oposite than notmuch_threads_advance and
notmuch_messages_advance. So I can use them as iterators going back and forward.
I didn't che
On 10:30, Thu 26 Nov 09, Carl Worth wrote:
> I'm glad to see work like this going on. If you do decide to keep going
> with it at all, I'd be glad to add this to contrib. I'm happy to have
> all kinds of different interfaces available.
Ok, I'll see what I'm doing about it in the future. Right now
On 11:17, Wed 25 Nov 09, Carl Worth wrote:
> And for the authors of the other interfaces, let us know when you've got
> similar support for streaming searches, (or if you didn't get this
> automatically as soon as "notmuch search" was fixed).
Yes, actually is faster now.
I had to rewrite some of
Hi notmuch community,
As I'm not an emacs user, I started to play with the code to see what are the
power of notmuch. I create a simple ncurses ui:
http://gitorious.org/notsomuch
Up to now it don't do much, just display searches and threads. It don't even
display the content of the emails. I gues
95 matches
Mail list logo