On Wed, 23 Apr 2014, Carl Worth wrote:
> Ah, then you've missed something different about my usage. I don't have
> any repository storing tags. My tags exist only in my notmuch
> database. The tool I want here is a simpler one, (think, "allow HTML
> export from HTML"). Heck, what I want could
Quoth David Mazieres on Apr 06 at 10:19 pm:
> Gaute Hope writes:
>
> > When one of the source files for a message is changed on disk, renamed,
> > deleted or a new source file is added. A configurable changed tag is
> > is added. The tag can be configured under the option 'changed_tags' in
> >
Hi Dave!
Quoth David Mazieres on Apr 23 at 2:00 am:
> Gaute Hope writes:
>
> > A db-tick or a _good_ ctime solution can as far as I can see solve both
> > David M's (correct me if I am wrong) and my purposes, as well as
> > probably have more use cases in the future. It would even be an
> >
We want the proper encoding and content-type to be set when sending the
mail, but human-readable plain-text for composing. So split the code in
two parts: the presentation and the transport conversion.
Signed-off-by: Felipe Contreras
---
vim/notmuch.vim | 34 +-
From: Paul Roberts
Signed-off-by: Felipe Contreras
---
vim/notmuch.vim | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/vim/notmuch.vim b/vim/notmuch.vim
index 25a16e9..0cb94f6 100644
--- a/vim/notmuch.vim
+++ b/vim/notmuch.vim
@@ -919,7 +919,8 @@ ruby
Seems it never really worked.
Signed-off-by: Felipe Contreras
---
vim/notmuch.vim | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/vim/notmuch.vim b/vim/notmuch.vim
index d7b310c..25a16e9 100644
--- a/vim/notmuch.vim
+++ b/vim/notmuch.vim
@@ -633,7 +633,7 @@ ruby << EOF
A few trivial updates, and an important fix.
Felipe Contreras (2):
Fix count_threads variable check
Improve the way messages are sent
Paul Roberts (1):
Make the html handler configurable
vim/notmuch.vim | 39 ---
1 file changed, 24 insertions(+), 15
Austin Clements writes:
> I'd like to have efficient change detection, too. In my case, I'd
> like to use it to support efficient live search and show updates. The
> design I'd sketched out for that used a log rather than ctimes, and
> I'm curious if you have thoughts on the relative merits
Austin Clements writes:
>> A middle ground might be to use the maximum of two values: 1) the
>> time-of-day at which notmuch started executing, and 2) the highest ctime
>> in the database plus 100 microseconds (leaving plenty of slop to store
>> timestamps as IEEE doubles with 52 significant
Excerpts from David Mazieres's message of 2014-04-23 11:00:10 +0200:
> Gaute Hope writes:
>
> > A db-tick or a _good_ ctime solution can as far as I can see solve both
> > David M's (correct me if I am wrong) and my purposes, as well as
> > probably have more use cases in the future. It would
Excerpts from David Bremner's message of 2014-04-23 00:05:02 +0200:
> Gaute Hope writes:
>
> >
> > I am talking about syncing tags to a maildir _folder_, not flags. It
> > could be implemented as maildir.synchronize is now, but it would be a
> > larger feature which could work in a lot of
On Wed, 23 Apr 2014, "W. Trevor King" wrote:
> * f55ff7e Drop the --get-query option
>
> I'd like to keep the in-Git config, so I'm -1 here.
FWIW I added the --get-query option as a convenience for accessing the
queries from a nmbug companion shell script (which isn't in the notmuch
repo
his email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20140423/36e123c3/attachment.pgp>
Gaute Hope writes:
>
> I am talking about syncing tags to a maildir _folder_, not flags. It
> could be implemented as maildir.synchronize is now, but it would be a
> larger feature which could work in a lot of different ways.
>
So to try and clarify the use case, this could be used to add a tag
Gaute Hope writes:
> A db-tick or a _good_ ctime solution can as far as I can see solve both
> David M's (correct me if I am wrong) and my purposes, as well as
> probably have more use cases in the future. It would even be an
> interesting direct search: show me everything that changed lately,
>
On Tue, 22 Apr 2014, Mark Walters wrote:
> LGTM +1
Looks good, and fixes the problem for me.
BR,
Jani.
>
> MW
>
> On Tue, 22 Apr 2014, Tomi Ollila wrote:
>> Users may have set core.abbrev=n, where n != 7 in their git config
>> file(s) which would give them different than expected version
W. Trevor King wk...@tremily.us writes:
I think that making nmbug and nmbug-status generally applicable for
other projects is a good target. I don't see any need to pull them
out into a stand-alone project to do that though.
For what it's worth, I don't disagree.
Does that mean your
On Wed, 23 Apr 2014, W. Trevor King wk...@tremily.us wrote:
* f55ff7e Drop the --get-query option
I'd like to keep the in-Git config, so I'm -1 here.
FWIW I added the --get-query option as a convenience for accessing the
queries from a nmbug companion shell script (which isn't in the notmuch
Excerpts from David Bremner's message of 2014-04-23 00:05:02 +0200:
Gaute Hope e...@gaute.vetsj.com writes:
I am talking about syncing tags to a maildir _folder_, not flags. It
could be implemented as maildir.synchronize is now, but it would be a
larger feature which could work in a lot
Jani Nikula j...@nikula.org writes:
On Wed, 23 Apr 2014, W. Trevor King wk...@tremily.us wrote:
* f55ff7e Drop the --get-query option
I'd like to keep the in-Git config, so I'm -1 here.
FWIW I added the --get-query option as a convenience for accessing the
queries from a nmbug companion
Excerpts from David Mazieres's message of 2014-04-23 11:00:10 +0200:
Gaute Hope e...@gaute.vetsj.com writes:
A db-tick or a _good_ ctime solution can as far as I can see solve both
David M's (correct me if I am wrong) and my purposes, as well as
probably have more use cases in the future.
On Wed, 23 Apr 2014, Carl Worth cwo...@cworth.org wrote:
Ah, then you've missed something different about my usage. I don't have
any repository storing tags. My tags exist only in my notmuch
database. The tool I want here is a simpler one, (think, allow HTML
export from HTML). Heck, what I
On Tue, Apr 22, 2014 at 11:01:09PM -0700, Carl Worth wrote:
W. Trevor King writes:
I think that making nmbug and nmbug-status generally applicable
for other projects is a good target. I don't see any need to
pull them out into a stand-alone project to do that though.
For what it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
W. Trevor King wk...@tremily.us writes:
So, “here's a goal to shoot for, and I'm happy with my fork. If
someone else wants to land patches like these upstream, I'm also happy
dropping my fork.” ;).
More just, Thanks for your code. I used it
Hi Dave!
Quoth David Mazieres on Apr 23 at 2:00 am:
Gaute Hope e...@gaute.vetsj.com writes:
A db-tick or a _good_ ctime solution can as far as I can see solve both
David M's (correct me if I am wrong) and my purposes, as well as
probably have more use cases in the future. It would even
Quoth David Mazieres on Apr 06 at 10:19 pm:
Gaute Hope e...@gaute.vetsj.com writes:
When one of the source files for a message is changed on disk, renamed,
deleted or a new source file is added. A configurable changed tag is
is added. The tag can be configured under the option
A few trivial updates, and an important fix.
Felipe Contreras (2):
Fix count_threads variable check
Improve the way messages are sent
Paul Roberts (1):
Make the html handler configurable
vim/notmuch.vim | 39 ---
1 file changed, 24 insertions(+), 15
We want the proper encoding and content-type to be set when sending the
mail, but human-readable plain-text for composing. So split the code in
two parts: the presentation and the transport conversion.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
vim/notmuch.vim | 34
From: Paul Roberts p...@stelo.org.uk
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
vim/notmuch.vim | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/vim/notmuch.vim b/vim/notmuch.vim
index 25a16e9..0cb94f6 100644
--- a/vim/notmuch.vim
+++ b/vim/notmuch.vim
@@
Seems it never really worked.
Signed-off-by: Felipe Contreras felipe.contre...@gmail.com
---
vim/notmuch.vim | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/vim/notmuch.vim b/vim/notmuch.vim
index d7b310c..25a16e9 100644
--- a/vim/notmuch.vim
+++ b/vim/notmuch.vim
@@ -633,7
Austin Clements amdra...@mit.edu writes:
A middle ground might be to use the maximum of two values: 1) the
time-of-day at which notmuch started executing, and 2) the highest ctime
in the database plus 100 microseconds (leaving plenty of slop to store
timestamps as IEEE doubles with 52
Tomi Ollila tomi.oll...@iki.fi writes:
Users may have set core.abbrev=n, where n != 7 in their git config
file(s) which would give them different than expected version strings
when building notmuch from git. This fixes the commit hash part of
version string to 7 hexadecimal values.
pushed to
32 matches
Mail list logo