On Mon, 16 Jan 2012 15:18:18 -0700, Jeremy Nickurak wrote:
> 1) If no exclude options are in the config file, none should be used.
> 2) On notmuch setup, "deleted" and "spam" should be added to .notmuch-config
That's correct.
jamie.
-- next part --
A non-text attachment
On Mon, 16 Jan 2012 21:38:30 +, Mark Walters
wrote:
> Define a keymap for attachment buttons to allow multiple actions.
Thanks, Mark. This new patch works great. I'm still not quite sure why
it wasn't working for me before, but this patch works great.
+1
We'll need to add a ":group
On Sat, 14 Jan 2012 19:17:32 -0500, Austin Clements wrote:
> This fixes the symbol visibility warning Jamie pointed out.
LGTM. I'm using this now and it works like a charm.
jamie.
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type:
On Mon, 16 Jan 2012 09:12:38 +, David Edmondson wrote:
> I don't think that anything should be excluded from the search results
> by default, at least not as a default behaviour of the 'notmuch'
> binary.
>
> Having "deleted" and "spam" as default settings in the configuration
> file might
On Mon, 16 Jan 2012 22:06:15 +0400, Dmitry Kurochkin wrote:
> Since this patches got in, I have yet to send a single email to the
> address(es) I intend to :( I am really used to the bindings and this
> change is a pain. From IRC discussion, it seems like I am not alone
> here.
Yeah, this has
On Sun, 15 Jan 2012 12:16:36 +, Mark Walters
wrote:
> Define a keymap for attachment buttons to allow multiple actions.
> Define 3 possible actions:
> save attachment: exactly as currently,
> view attachment: uses mailcap entry,
> view attachment with user chosen program
Great
On Mon, 16 Jan 2012 08:39:30 +, David Edmondson wrote:
> Is there a mechanistic way to determine the correct behaviour in this
> respect? I suspect that it's exactly the kind of thing that Carl wanted
> to be included in 'notmuch' itself, so that other UIs can benefit.
Agreed. I think it's
On Mon, 16 Jan 2012 08:39:30 +, David Edmondson d...@dme.org wrote:
Is there a mechanistic way to determine the correct behaviour in this
respect? I suspect that it's exactly the kind of thing that Carl wanted
to be included in 'notmuch' itself, so that other UIs can benefit.
Agreed. I
On Mon, 16 Jan 2012 21:38:30 +, Mark Walters markwalters1...@gmail.com
wrote:
Define a keymap for attachment buttons to allow multiple actions.
Thanks, Mark. This new patch works great. I'm still not quite sure why
it wasn't working for me before, but this patch works great.
+1
We'll
On Mon, 16 Jan 2012 15:18:18 -0700, Jeremy Nickurak not-m...@trk.nickurak.ca
wrote:
1) If no exclude options are in the config file, none should be used.
2) On notmuch setup, deleted and spam should be added to .notmuch-config
That's correct.
jamie.
pgpte3TFLdDYd.pgp
Description: PGP
On Mon, 16 Jan 2012 23:32:00 -0500, Austin Clements amdra...@mit.edu wrote:
Cleanup is the type of pain that should only be suffered once, so I'd
be much happier with this if there was an accompanying git hook that
prevented more mis-formatted code from slipping in.
Agreed. However, if we're
On Tue, 17 Jan 2012 07:48:27 -, Mark Foxwell fastfre...@archlinux.org.uk
wrote:
Not sure if you're aware of this?
Yes, we are aware. There are actually two fresh patches to the list to
address this, though:
id:1326758199-18058-1-git-send-email-schno...@schnouki.net
This patch looks fine. Philosophical UI discussion to follow:
On Fri, 13 Jan 2012 18:07:04 -0500, Austin Clements wrote:
> +if (notmuch_config_get_auto_exclude_tags (config, ) == NULL) {
> + const char *tags[] = { "deleted", "spam" };
> + notmuch_config_set_auto_exclude_tags
It looks like something in this patch is causing the following build
warning:
CXX -O2 lib/query.o
lib/query.cc:26:8: warning: ?_notmuch_query? declared with greater visibility
than the type of its field
?_notmuch_query::exclude_terms? [-Wattributes]
However, I can't quite figure out what's
On Fri, 13 Jan 2012 18:07:01 -0500, Austin Clements wrote:
> This addresses Jani's comments and improves some of the text and code
> comments.
This is a really nice feature addition, Austin. And it works like a
charm. ++1.
A couple of small comments to follow.
jamie.
-- next part
I like all of Austin's description suggestions.
jamie.
I like all of Austin's description suggestions.
jamie.
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
It looks like something in this patch is causing the following build
warning:
CXX -O2 lib/query.o
lib/query.cc:26:8: warning: ‘_notmuch_query’ declared with greater visibility
than the type of its field
‘_notmuch_query::exclude_terms’ [-Wattributes]
However, I can't quite figure out what's
This patch looks fine. Philosophical UI discussion to follow:
On Fri, 13 Jan 2012 18:07:04 -0500, Austin Clements amdra...@mit.edu wrote:
+if (notmuch_config_get_auto_exclude_tags (config, tmp) == NULL) {
+ const char *tags[] = { deleted, spam };
+
On Thu, 12 Jan 2012 18:12:16 +0100, Pieter Praet wrote:
> To allow for expansion whilst keeping everything tidy and organized,
> move all defcustom/defface variables to the following subgroups,
> defined in notmuch-lib.el:
Baring the issue that the Davids brought up about the sub group
On Fri, 13 Jan 2012 05:05:35 -0400, David Bremner wrote:
> I thought about this a bit more, and I agree that at least the release
> candidates (basically anything tagged on branch release) ought to be
> merged back to master. Since any series of bugfix patches seems to be
> cause for a new
On Fri, 13 Jan 2012 05:05:35 -0400, David Bremner da...@tethera.net wrote:
I thought about this a bit more, and I agree that at least the release
candidates (basically anything tagged on branch release) ought to be
merged back to master. Since any series of bugfix patches seems to be
cause for
On Thu, 12 Jan 2012 18:12:16 +0100, Pieter Praet pie...@praet.org wrote:
To allow for expansion whilst keeping everything tidy and organized,
move all defcustom/defface variables to the following subgroups,
defined in notmuch-lib.el:
Baring the issue that the Davids brought up about the sub
On Thu, 12 Jan 2012 20:05:14 +0100, Gregor Zattler wrote:
> But how about not only replying encrypted but encrypting every
> email if possible? "Possible" could mean different things,
> though:
This is already easy to do in emacs, and doesn't require any special
notmuch support:
(add-hook
On Tue, 03 Jan 2012 13:45:14 -0800, Jameson Graef Rollins wrote:
> Unfortunately, auto encrypting of replies to encrypted emails is not yet
> implemented. It is desperately needed, though, obviously. So this is a
> good excuse to start a discussion about how we could achieve this.
>
On Tue, 03 Jan 2012 13:45:14 -0800, Jameson Graef Rollins
jroll...@finestructure.net wrote:
Unfortunately, auto encrypting of replies to encrypted emails is not yet
implemented. It is desperately needed, though, obviously. So this is a
good excuse to start a discussion about how we could
On Thu, 12 Jan 2012 20:05:14 +0100, Gregor Zattler telegr...@gmx.net wrote:
But how about not only replying encrypted but encrypting every
email if possible? Possible could mean different things,
though:
This is already easy to do in emacs, and doesn't require any special
notmuch support:
On Mon, 2 Jan 2012 17:04:17 +0100, piuttosto at logorroici.org wrote:
> 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 Mon, 2 Jan 2012 17:04:17 +0100, piutto...@logorroici.org wrote:
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, 11 Jan 2012 00:53:35 -0500, Aaron Ecay wrote:
> On Tue, 10 Jan 2012 18:56:29 -0800, Jameson Graef Rollins finestructure.net> wrote:
> > Actually, the show-next argument was already part of the function. I
> > did not introduce it. And it wasn't optional origina
On Wed, 11 Jan 2012 00:02:50 -0500, Austin Clements wrote:
> This implements essentially the same idea as Jamie's patch, but does
> it in the library/CLI and operates on the parsed query rather than
> using an ad hoc regexp. Which tags are automatically excluded is set
> in the config file and
On Tue, 10 Jan 2012 16:01:32 -0400, David Bremner wrote:
> Just thinking out loud here, but it does seem a bit unfortunate to me
> that it represents a pretty fundamental divergence between the CLI and
> the emacs interface. Mind you, I guess one could make the same argument
> about the libs
On Mon, 09 Jan 2012 00:02:20 -0500, Aaron Ecay wrote:
> On Sun, 08 Jan 2012 18:49:56 -0800, Jameson Graef Rollins finestructure.net> wrote:
> > On Sun, 08 Jan 2012 20:08:59 -0500, Aaron Ecay
> > wrote:
> > >
> > > - It would be good to make show-next T
On Tue, 10 Jan 2012 07:47:23 +, David Edmondson wrote:
> I honestly don't understand the reason for this. If someone wants to not
> see messages that they have tagged as 'deleted', they add 'and not
> tag:deleted' to the end of the search expression.
Adding "and not tag:deleted" in all of
On Sun, 08 Jan 2012 16:16:06 -, Justus Winter
4win...@informatik.uni-hamburg.de wrote:
I've decided to step up as a new maintainer for the libnotmuch python
bindings. I assume that I'll have to mail an ssh public key to someone
for repository access, right?
That's great to hear, Justus.
On Tue, 10 Jan 2012 07:47:23 +, David Edmondson d...@dme.org wrote:
I honestly don't understand the reason for this. If someone wants to not
see messages that they have tagged as 'deleted', they add 'and not
tag:deleted' to the end of the search expression.
Adding and not tag:deleted in
On Mon, 09 Jan 2012 00:02:20 -0500, Aaron Ecay aarone...@gmail.com wrote:
On Sun, 08 Jan 2012 18:49:56 -0800, Jameson Graef Rollins
jroll...@finestructure.net wrote:
On Sun, 08 Jan 2012 20:08:59 -0500, Aaron Ecay aarone...@gmail.com wrote:
- It would be good to make show-next optional
On Tue, 10 Jan 2012 16:01:32 -0400, David Bremner da...@tethera.net wrote:
Just thinking out loud here, but it does seem a bit unfortunate to me
that it represents a pretty fundamental divergence between the CLI and
the emacs interface. Mind you, I guess one could make the same argument
about
On Wed, 11 Jan 2012 00:02:50 -0500, Austin Clements amdra...@mit.edu wrote:
This implements essentially the same idea as Jamie's patch, but does
it in the library/CLI and operates on the parsed query rather than
using an ad hoc regexp. Which tags are automatically excluded is set
in the
On Wed, 11 Jan 2012 00:53:35 -0500, Aaron Ecay aarone...@gmail.com wrote:
On Tue, 10 Jan 2012 18:56:29 -0800, Jameson Graef Rollins
jroll...@finestructure.net wrote:
Actually, the show-next argument was already part of the function. I
did not introduce it. And it wasn't optional
On Sun, 08 Jan 2012 16:16:06 -, Justus Winter <4winter at
informatik.uni-hamburg.de> wrote:
> I've decided to step up as a new maintainer for the libnotmuch python
> bindings. I assume that I'll have to mail an ssh public key to someone
> for repository access, right?
That's great to hear,
Thanks so much for the review, Aaron.
On Sun, 08 Jan 2012 20:08:59 -0500, Aaron Ecay wrote:
> A couple of comments on the arguments:
> - It would be good to make show-next This will enable code
> to call the fn with only two arguments, and not showing next will be
> the default behavior.
On Sun, 8 Jan 2012 20:49:38 -0500, Austin Clements wrote:
> > > @@ -927,6 +932,9 @@ The optional parameters are used as follows:
> > > (set 'notmuch-search-target-thread target-thread)
> > > (set 'notmuch-search-target-line target-line)
> > > (set 'notmuch-search-continuation
On Sun, 8 Jan 2012 15:01:30 -0700, Jeremy Nickurak wrote:
> FWIW, I generally prefer reply-all as the default. In my experience,
> when a message is sent to a bunch of people, it's usually treated as a
> "forum" discussion where everybody wants to be in on everything. Also,
> once you've started
This provides a smoother message processing flow by reducing the
number of key presses needed for these common operations.
---
Sorry sorry. I originally missed the problem in patch 1/4, so I had
to modify this patch again to apply against the new version of the
previous. So sorry for the noise,
This adds two new function, notmuch-show-{archive,delete}-message,
that archive/delete the current message, and then move to the next
open one.
---
Sorry, there were some errant extra parens at the end of these
function definitions.
emacs/notmuch-show.el | 24
1 files
This provides a smoother message processing flow by reducing the
number of key presses needed for these common operations.
---
Sorry, there were some errant extra parens at the end of these
function definitions.
emacs/notmuch-show.el |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
This provides a smoother message processing flow by reducing the
number of key presses needed for these common operations.
---
Sorry, there were some errant extra parens at the end of these
function definitions.
emacs/notmuch-show.el |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
This adds two new function, notmuch-show-{archive,delete}-message,
that archive/delete the current message, and then move to the next
open one.
---
Sorry, there were some errant extra parens at the end of these
function definitions.
emacs/notmuch-show.el | 24
1 files
This provides a smoother message processing flow by reducing the
number of key presses needed for these common operations.
---
Sorry sorry. I originally missed the problem in patch 1/4, so I had
to modify this patch again to apply against the new version of the
previous. So sorry for the noise,
On Sun, 8 Jan 2012 15:01:30 -0700, Jeremy Nickurak not-m...@trk.nickurak.ca
wrote:
FWIW, I generally prefer reply-all as the default. In my experience,
when a message is sent to a bunch of people, it's usually treated as a
forum discussion where everybody wants to be in on everything. Also,
On Sun, 8 Jan 2012 20:49:38 -0500, Austin Clements amdra...@mit.edu wrote:
@@ -927,6 +932,9 @@ The optional parameters are used as follows:
(set 'notmuch-search-target-thread target-thread)
(set 'notmuch-search-target-line target-line)
(set 'notmuch-search-continuation
Thanks so much for the review, Aaron.
On Sun, 08 Jan 2012 20:08:59 -0500, Aaron Ecay aarone...@gmail.com wrote:
A couple of comments on the arguments:
- It would be good to make show-next optional. This will enable code
to call the fn with only two arguments, and not showing next will be
This provides a smoother message processing flow by reducing the
number of key presses needed for these common operations.
---
emacs/notmuch-show.el |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 4c2b507..7103c23
This changes the default key bindings for the 'a' and 'd' keys in
notmuch-show mode. Instead of archiving/deleting the entire thread,
they now just archive/delete the current message, and then advance to
the next open message.
'A' and 'D' are rebound to the previous archive/delete-thread
This will allow for keybindings that achieve a smoother message
processing flow by reducing the number of key presses needed for most
common operations.
---
emacs/notmuch-show.el | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/emacs/notmuch-show.el
This adds two new function, notmuch-show-{archive,delete}-message,
that archive/delete the current message, and then move to the next
open one.
---
emacs/notmuch-show.el | 24
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/emacs/notmuch-show.el
While working on the delete message handling patches, I was reminded
how much I really dislike the default show-mode key bindings. Why
can't I just archive/delete the current message, without archiving the
entire thread? It doesn't make any sense.
Here we add two new functions to archive and
No functional change here. The help message previously referred to
the "delete" tag, but "deleted" is now preferred, so hopefully this
will reduce any potential confusion.
---
emacs/notmuch.el |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/emacs/notmuch.el
This completely mimics the behavior of archiving, but instead of
remove the inbox tag it add the "deleted" tag. The functionality is
bound to the 'd' key in both search and show mode.
Note: this does *not* actually delete any messages. That is still
left entirely up to the user to figure out
Instead of having a function that is only used for archiving a thread,
we instead make it useful for any tagging operation. The new
function, notmuch-show-tag-thread-internal, now takes two more
arguments, for the "sign" of the tagging operation ("-" or "+"), and
the tag to be added or removed.
The new customization variable, notmuch-search-exclude-deleted, when
set to t, will exclude any messages with the "deleted" tag from
searches.
Additionally, specifying "tag:deleted" in the search directly will
override the exclusion and will included deleted messages in the
search results.
---
So, after many stabs at adding the ability to "delete" messages in
emacs [0], and the corresponding heated discussions, I'm throwing
another attempt into the fray.
I try to address the concerns that have come up in previous attempts.
In particular, I include a patch that creates a new
On Sat, 07 Jan 2012 09:37:20 -0400, David Bremner wrote:
> 2) can you share (by private email is a fine) a few of those really
>problematic messages so I can use them to test the new dump/restore code?
I think the better option would be to create a test that runs through
all the horrible
On Sat, 07 Jan 2012 09:37:20 -0400, David Bremner da...@tethera.net wrote:
2) can you share (by private email is a fine) a few of those really
problematic messages so I can use them to test the new dump/restore code?
I think the better option would be to create a test that runs through
all
So, after many stabs at adding the ability to delete messages in
emacs [0], and the corresponding heated discussions, I'm throwing
another attempt into the fray.
I try to address the concerns that have come up in previous attempts.
In particular, I include a patch that creates a new customization
No functional change here. The help message previously referred to
the delete tag, but deleted is now preferred, so hopefully this
will reduce any potential confusion.
---
emacs/notmuch.el |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/emacs/notmuch.el
Instead of having a function that is only used for archiving a thread,
we instead make it useful for any tagging operation. The new
function, notmuch-show-tag-thread-internal, now takes two more
arguments, for the sign of the tagging operation (- or +), and
the tag to be added or removed. This
This completely mimics the behavior of archiving, but instead of
remove the inbox tag it add the deleted tag. The functionality is
bound to the 'd' key in both search and show mode.
Note: this does *not* actually delete any messages. That is still
left entirely up to the user to figure out how
The new customization variable, notmuch-search-exclude-deleted, when
set to t, will exclude any messages with the deleted tag from
searches.
Additionally, specifying tag:deleted in the search directly will
override the exclusion and will included deleted messages in the
search results.
---
This will allow for keybindings that achieve a smoother message
processing flow by reducing the number of key presses needed for most
common operations.
---
emacs/notmuch-show.el | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/emacs/notmuch-show.el
This changes the default key bindings for the 'a' and 'd' keys in
notmuch-show mode. Instead of archiving/deleting the entire thread,
they now just archive/delete the current message, and then advance to
the next open message.
'A' and 'D' are rebound to the previous archive/delete-thread
This provides a smoother message processing flow by reducing the
number of key presses needed for these common operations.
---
emacs/notmuch-show.el |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 4c2b507..7103c23
While working on the delete message handling patches, I was reminded
how much I really dislike the default show-mode key bindings. Why
can't I just archive/delete the current message, without archiving the
entire thread? It doesn't make any sense.
Here we add two new functions to archive and
This adds two new function, notmuch-show-{archive,delete}-message,
that archive/delete the current message, and then move to the next
open one.
---
emacs/notmuch-show.el | 24
1 files changed, 24 insertions(+), 0 deletions(-)
diff --git a/emacs/notmuch-show.el
On Fri, 06 Jan 2012 15:10:57 -0500, Antoine Beaupr?
wrote:
> Most patches I have submitted here haven't been accepted and I have to
> painfully reroll my own packages every time there's a new release, which
> has been a very frustrating experience. To see such a trivial patch
> obsoleted tops
On Thu, 29 Dec 2011 16:05:39 +, David Edmondson wrote:
> What's the general feeling about this approach to producing tests for
> the emacs UI? (That is, code the test in a .el file and call the
> relevant function(s) from the test harness.)
I think it's a nice idea. It seems much cleaner
On Wed, 28 Dec 2011 14:31:31 +, David Edmondson wrote:
> Probably just for aficionados at the moment...
Actually, I think that all the rest of these comments should be included
in the log. There's useful discussion here.
> Given that clashes between overlays and text properties are a
On Wed, 28 Dec 2011 14:31:31 +, David Edmondson d...@dme.org wrote:
Probably just for aficionados at the moment...
Actually, I think that all the rest of these comments should be included
in the log. There's useful discussion here.
Given that clashes between overlays and text properties
On Thu, 29 Dec 2011 16:05:39 +, David Edmondson d...@dme.org wrote:
What's the general feeling about this approach to producing tests for
the emacs UI? (That is, code the test in a .el file and call the
relevant function(s) from the test harness.)
I think it's a nice idea. It seems much
On Fri, 06 Jan 2012 15:10:57 -0500, Antoine Beaupré anar...@koumbit.org wrote:
Most patches I have submitted here haven't been accepted and I have to
painfully reroll my own packages every time there's a new release, which
has been a very frustrating experience. To see such a trivial patch
On Fri, 06 Jan 2012 00:29:39 +, Mark Walters
wrote:
> What is the best way of exporting/saving as text a mime-encoded email
> from the emacs interface (e.g, if I want to save a mime-encoded
> email containing a patch)?
Maybe you're looking for '|'? That will pipe the raw message to
On Thu, 05 Jan 2012 22:32:16 +0200, Jani Nikula wrote:
> In the search view it does exactly this.
I worry about race conditions in this case, though. I frequently
archive threads after I've read everything, but I still want to know if
new message to that thread come in. If I attempt to archive
On Thu, 5 Jan 2012 22:25:11 +0200, Jani Nikula wrote:
> Bikeshedding topic #1: How about making replying to just the sender the
> default
> in "notmuch reply", and having --reply-all option (instead of --no-reply-all)?
>
> Bikeshedding topic #2: How about binding 'r' to reply to just the
On Wed, 4 Jan 2012 15:26:52 +0200, Tomi Ollila tomi.oll...@iki.fi wrote:
In NEWS file, indentation for item descriptions is generally 2 spaces
but in a few cases there were 3 or 4 (4 caused different markdown
handling) space indentations. Indentation in those lines are brought
to consistent
On Tue, 3 Jan 2012 20:59:51 +0100, Karel Zak k...@redhat.com wrote:
I had to tweak your use of notmuch_database_find_message (I'm using
0.11_rc2) but otherwise it compiles fine.
Unfortunately, the latest package for Fedora is notmuch-0.5-4.fc15 ;-(
But I'm ready to accept patches to make
On Thu, 5 Jan 2012 22:25:11 +0200, Jani Nikula j...@nikula.org wrote:
Bikeshedding topic #1: How about making replying to just the sender the
default
in notmuch reply, and having --reply-all option (instead of --no-reply-all)?
Bikeshedding topic #2: How about binding 'r' to reply to just
On Thu, 05 Jan 2012 22:32:16 +0200, Jani Nikula j...@nikula.org wrote:
In the search view it does exactly this.
I worry about race conditions in this case, though. I frequently
archive threads after I've read everything, but I still want to know if
new message to that thread come in. If I
On Fri, 06 Jan 2012 00:29:39 +, Mark Walters markwalters1...@gmail.com
wrote:
What is the best way of exporting/saving as text a mime-encoded email
from the emacs interface (e.g, if I want to save a mime-encoded
email containing a patch)?
Maybe you're looking for '|'? That will pipe the
On Tue, 3 Jan 2012 20:59:51 +0100, Karel Zak wrote:
> > I had to tweak your use of notmuch_database_find_message (I'm using
> > 0.11_rc2) but otherwise it compiles fine.
>
> Unfortunately, the latest package for Fedora is notmuch-0.5-4.fc15 ;-(
>
> But I'm ready to accept patches to make it
On Wed, 4 Jan 2012 15:26:52 +0200, Tomi Ollila wrote:
> In NEWS file, indentation for item descriptions is generally 2 spaces
> but in a few cases there were 3 or 4 (4 caused different markdown
> handling) space indentations. Indentation in those lines are brought
> to consistent 2-space
On Tue, 3 Jan 2012 17:36:32 -0500, Peter Portante wrote:
> Is there a good test suite for notmuch?
Hey, Peter. Yes, there is a very good, extensive test suite for
notmuch. It can be run with "make test"
jamie.
-- next part --
A non-text attachment was scrubbed...
Name:
On Tue, 03 Jan 2012 17:09:39 -0500, Peter Portante wrote:
> I am interested in using notmuch from within emacs, but have not been
> able to get the latest version of notmuch (0.10.2) to compile under
> Fedora 16:
>
> [pportant at frodo notmuch-0.10.2]$ make
> Use "make V=1" to see the
On Tue, 3 Jan 2012 20:56:51 +0100, Gregor Zattler wrote:
> I replied to a PGP/MIME signed and encrypted e-mail and was
> astonished to realise that my reply was sent unencrypted (and
> unsigened for that matter).
Yikes! Sorry this happened, and I hope nothing too sensitive was
exposed.
Auto
On Tue, 03 Jan 2012 21:57:22 +0200, Jani Nikula wrote:
> The code's there, and talk is cheap... but I'd rather like to see a
> solution that would make it easy for users to add arbitrary tagging
> operations to key bindings, instead of a fixed binding for "deleted".
It's already easy for users
On Tue, 3 Jan 2012 20:59:51 +0100, Karel Zak wrote:
> Unfortunately, the latest package for Fedora is notmuch-0.5-4.fc15 ;-(
Yikes that's old (0.11 is being released eminently). There have been
quite a few important changes since then. Is there no one actively
maintaining the fedora package?
On Mon, 02 Jan 2012 17:14:58 +0100, Sebastian Spaeth
wrote:
> After a few weeks of notmuch abstinence I am being overwhelmed with 750
> new notmuch mails, and I really don't have the time or will (nor does my
> family approve) to spend enormous amounts of time on notmuch. I am
> already
This change looks slightly larger than it actually is, since I moved
the emacs section below the Performance and Memory Management
sections.
---
NEWS | 51 ---
1 files changed, 40 insertions(+), 11 deletions(-)
diff --git a/NEWS b/NEWS
index
The name was originally notmuch-indent-messages-width, which is
inconsistent with our variable naming convention.
---
emacs/notmuch-show.el |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index eee4da9..82d11c9 100644
---
The name was originally notmuch-indent-messages-width, which is
inconsistent with our variable naming convention.
---
Sorry, I forgot to fix the tests in the original patch.
emacs/notmuch-show.el |6 +++---
test/emacs|6 +++---
2 files changed, 6 insertions(+), 6 deletions(-)
901 - 1000 of 1627 matches
Mail list logo
