Jani Nikula writes:
> On Fri, 02 May 2014, dm-list-email-notmuch at scs.stanford.edu wrote:
>>
>> I'm using a pretty standard maildir++ layout. For example, underneath
>> my database.path I have a bunch of mail in directories such as:
>>
>> .INBOX.Main/{new,cur}
>> .mail.class/{new,cur}
Wildcard matching was a feature of the probabilistic prefix, and we no
longer have it for the boolean prefix. Also note that top-level folder
can now be searched.
---
NEWS | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/NEWS b/NEWS
index
Hi
Before checking other things: have you run notmuch new? That's needed to
update the database. It is an irreversible update so notmuch-0.17 will
not work with the updated database.
The update should save a dump of the tags before updating but you might
want to do that manually too (and maybe
---
doc/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/.gitignore b/doc/.gitignore
index a60fb31e9419..f0cbb9c27b24 100644
--- a/doc/.gitignore
+++ b/doc/.gitignore
@@ -1,2 +1,3 @@
+*.pyc
docdeps.mk
_build
--
1.9.2
Sort the file while at it.
---
test/.gitignore | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/test/.gitignore b/test/.gitignore
index 97e024878728..4081cee6da18 100644
--- a/test/.gitignore
+++ b/test/.gitignore
@@ -1,9 +1,11 @@
-test-results
-corpus.mail
Good for me, thank you.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 310 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20140502/ccfe5e73/attachment.pgp>
gging script that can be killed at any
> point and restarted. (You're right that post-new has a concurrency
> issue, but we should fix that in its own right.)
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size
__
>> notmuch mailing list
>> notmuch at notmuchmail.org
>> http://notmuchmail.org/mailman/listinfo/notmuch
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 310 byte
This version LGTM +1.
Best wishes
Mark
On Thu, 01 May 2014, Jani Nikula wrote:
> Some archives may use a more complicated scheme for referring to
> messages than just concatenated url and message-id. In particular,
> patchwork requires a query to translate message-id to a patchwork
> patch
I don't like the wildcard bit as an important part of the change was the
removal of stemming. Perhaps keep exact in the headline and in the body
say explicitly what the changes are no stemming, no wildcards (except
globbing), etc (maybe case sensitivity is different?)
Best wishes
Mark
On
Version 2 passes all tests and LGTM. +1
Best wishes
Mark
On Fri, 02 May 2014, David Edmondson wrote:
> v1:
>
> This patch set allows a user to specify a list of tags to be
> added/removed to messages discovered during "notmuch new".
>
> Two use-cases are envisaged:
> 1) A chunk of
Mark Walters writes:
> Hi
>
> Before checking other things: have you run notmuch new? That's needed to
> update the database. It is an irreversible update so notmuch-0.17 will
> not work with the updated database.
No, I haven't. Okay, so that must be it. Sorry for bothering people.
The
Add a simple set of tests for adding, removing and both adding and
removing tags when running "notmuch new".
---
test/T540-new-tags.sh | 28
1 file changed, 28 insertions(+)
create mode 100755 test/T540-new-tags.sh
diff --git a/test/T540-new-tags.sh
---
NEWS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS b/NEWS
index bcd311d..13ae593 100644
--- a/NEWS
+++ b/NEWS
@@ -12,6 +12,12 @@ Command-Line Interface
This option suppresses the progress and summary reports.
+`notmuch new` allows tag addition/removal to be specified
+
+
Describe the addition of command line tags for "notmuch new".
---
doc/man1/notmuch-new.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/man1/notmuch-new.rst b/doc/man1/notmuch-new.rst
index 787ed78..84203de 100644
--- a/doc/man1/notmuch-new.rst
+++
Add support for specifying a set of tags to be added/removed from
messages added to the database by 'notmuch new'. These tags are
addition to those specified in .notmuch-config. They can be used to
override the pre-configured tags (e.g. -inbox).
---
notmuch-new.c | 5 +
tag-util.c| 20
Rather than hand-coding the application of tags to new messages, use
the existing tag_op_list_apply().
fixup.
---
notmuch-new.c | 31 ---
tag-util.c| 8
tag-util.h| 10 +++---
3 files changed, 31 insertions(+), 18 deletions(-)
diff --git
rmail/notmuch/attachments/20140502/0cd7d669/attachment.pgp>
.asc
Type: application/pgp-signature
Size: 310 bytes
Desc: not available
URL:
<http://notmuchmail.org/pipermail/notmuch/attachments/20140502/a9efa182/attachment.pgp>
On Fri, May 02 2014, Felipe Contreras wrote:
> Tomi Ollila wrote:
>
>> PS: does vim frontend lack id:message-id feature --
>
> What feature?
In Emacs MUA, when one presses ENTER (or clicks mouse) on top of
text containing id: the client opens that particular message.
> --
> Felipe Contreras
On Fri, May 02 2014, David Bremner wrote:
> Felipe Contreras writes:
>
>>
>>> Also NEWS for these changes are missing.
>>
>> Shouldn't the NEWS be written by the maintainers? In fact, aren't they
>> the ones that decide if something is worth mentioning in the NEWS or
>> not?
>>
>
> Hi Felipe;
>
Felipe Contreras writes:
>
>> Also NEWS for these changes are missing.
>
> Shouldn't the NEWS be written by the maintainers? In fact, aren't they
> the ones that decide if something is worth mentioning in the NEWS or
> not?
>
Hi Felipe;
I guess for the Vim/ruby stuff you're best positioned to
Quoth David Edmondson on May 02 at 9:15 am:
> This patch set allows a user to specify a list of tags to be
> added/removed to messages discovered during "notmuch new".
>
> Two use-cases are envisaged:
> 1) A chunk of messages was just dumped into the configured
>directory by hand,
Hey, I'm playing around with the head of the git repository
(bc64cdce289d84be2550c4fccb1f008d15eaeb0e) to try to figure out how the
new folder: prefixes work, as folders are a critical part of how I
organize my mail. (Since tags are not hierarchical, folders are the
best way for me to group mail
---
NEWS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS b/NEWS
index bcd311d..13ae593 100644
--- a/NEWS
+++ b/NEWS
@@ -12,6 +12,12 @@ Command-Line Interface
This option suppresses the progress and summary reports.
+`notmuch new` allows tag addition/removal to be specified
+
+
Describe the addition of command line tags for "notmuch new".
---
doc/man1/notmuch-new.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/man1/notmuch-new.rst b/doc/man1/notmuch-new.rst
index 787ed78..84203de 100644
--- a/doc/man1/notmuch-new.rst
+++
Add support for specifying a set of tags to be added/removed from
messages added to the database by 'notmuch new'. These tags are
addition to those specified in .notmuch-config. They can be used to
override the pre-configured tags (e.g. -inbox).
---
notmuch-new.c | 5 +
tag-util.c| 20
Rather than hand-coding the application of tags to new messages, use
the existing tag_op_list_apply().
---
notmuch-new.c | 31 ---
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/notmuch-new.c b/notmuch-new.c
index d269c7c..b53401a 100644
---
This patch set allows a user to specify a list of tags to be
added/removed to messages discovered during "notmuch new".
Two use-cases are envisaged:
1) A chunk of messages was just dumped into the configured
directory by hand, and the user doesn't want the 'inbox' tag
applied to
Jani Nikula writes:
> ---
> NEWS | 7 +++
> 1 file changed, 7 insertions(+)
pushed jani's 5 patches, and an amended version of mine
Add support for specifying a set of tags to be added/removed from
messages added to the database by 'notmuch new'. These tags are
addition to those specified in .notmuch-config. They can be used to
override the pre-configured tags (e.g. -inbox).
---
notmuch-new.c | 5 +
tag-util.c| 20
This patch set allows a user to specify a list of tags to be
added/removed to messages discovered during notmuch new.
Two use-cases are envisaged:
1) A chunk of messages was just dumped into the configured
directory by hand, and the user doesn't want the 'inbox' tag
applied to
Add a simple set of tests for adding, removing and both adding and
removing tags when running notmuch new.
---
test/T540-new-tags.sh | 28
1 file changed, 28 insertions(+)
create mode 100755 test/T540-new-tags.sh
diff --git a/test/T540-new-tags.sh
Rather than hand-coding the application of tags to new messages, use
the existing tag_op_list_apply().
---
notmuch-new.c | 31 ---
1 file changed, 16 insertions(+), 15 deletions(-)
diff --git a/notmuch-new.c b/notmuch-new.c
index d269c7c..b53401a 100644
---
Describe the addition of command line tags for notmuch new.
---
doc/man1/notmuch-new.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/man1/notmuch-new.rst b/doc/man1/notmuch-new.rst
index 787ed78..84203de 100644
--- a/doc/man1/notmuch-new.rst
+++
---
NEWS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS b/NEWS
index bcd311d..13ae593 100644
--- a/NEWS
+++ b/NEWS
@@ -12,6 +12,12 @@ Command-Line Interface
This option suppresses the progress and summary reports.
+`notmuch new` allows tag addition/removal to be specified
+
On Fri, May 02 2014, Felipe Contreras felipe.contre...@gmail.com wrote:
Tomi Ollila wrote:
PS: does vim frontend lack id:message-id feature --
What feature?
In Emacs MUA, when one presses ENTER (or clicks mouse) on top of
text containing id:message-id the client opens that particular
The documentation for `notmuch-search-line-faces' says:
The attributes defined for matching tags are merged, with later
attributes overriding earlier.
A comment in `notmuch-search-color-line', which implements this, says:
;; Reverse the list so earlier entries take precedence
Clearly these
v1:
This patch set allows a user to specify a list of tags to be
added/removed to messages discovered during notmuch new.
Two use-cases are envisaged:
1) A chunk of messages was just dumped into the configured
directory by hand, and the user doesn't want the 'inbox' tag
applied
Describe the addition of command line tags for notmuch new.
---
doc/man1/notmuch-new.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/man1/notmuch-new.rst b/doc/man1/notmuch-new.rst
index 787ed78..84203de 100644
--- a/doc/man1/notmuch-new.rst
+++
Rather than hand-coding the application of tags to new messages, use
the existing tag_op_list_apply().
fixup.
---
notmuch-new.c | 31 ---
tag-util.c| 8
tag-util.h| 10 +++---
3 files changed, 31 insertions(+), 18 deletions(-)
diff --git
Add support for specifying a set of tags to be added/removed from
messages added to the database by 'notmuch new'. These tags are
addition to those specified in .notmuch-config. They can be used to
override the pre-configured tags (e.g. -inbox).
---
notmuch-new.c | 5 +
tag-util.c| 20
Add a simple set of tests for adding, removing and both adding and
removing tags when running notmuch new.
---
test/T540-new-tags.sh | 28
1 file changed, 28 insertions(+)
create mode 100755 test/T540-new-tags.sh
diff --git a/test/T540-new-tags.sh
---
NEWS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/NEWS b/NEWS
index bcd311d..13ae593 100644
--- a/NEWS
+++ b/NEWS
@@ -12,6 +12,12 @@ Command-Line Interface
This option suppresses the progress and summary reports.
+`notmuch new` allows tag addition/removal to be specified
+
Version 2 passes all tests and LGTM. +1
Best wishes
Mark
On Fri, 02 May 2014, David Edmondson d...@dme.org wrote:
v1:
This patch set allows a user to specify a list of tags to be
added/removed to messages discovered during notmuch new.
Two use-cases are envisaged:
1) A chunk of
I don't like the wildcard bit as an important part of the change was the
removal of stemming. Perhaps keep exact in the headline and in the body
say explicitly what the changes are no stemming, no wildcards (except
globbing), etc (maybe case sensitivity is different?)
Best wishes
Mark
On
This version LGTM +1.
Best wishes
Mark
On Thu, 01 May 2014, Jani Nikula j...@nikula.org wrote:
Some archives may use a more complicated scheme for referring to
messages than just concatenated url and message-id. In particular,
patchwork requires a query to translate message-id to a
---
doc/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/doc/.gitignore b/doc/.gitignore
index a60fb31e9419..f0cbb9c27b24 100644
--- a/doc/.gitignore
+++ b/doc/.gitignore
@@ -1,2 +1,3 @@
+*.pyc
docdeps.mk
_build
--
1.9.2
___
notmuch
Sort the file while at it.
---
test/.gitignore | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/test/.gitignore b/test/.gitignore
index 97e024878728..4081cee6da18 100644
--- a/test/.gitignore
+++ b/test/.gitignore
@@ -1,9 +1,11 @@
-test-results
-corpus.mail
Quoth David Edmondson on May 02 at 9:15 am:
This patch set allows a user to specify a list of tags to be
added/removed to messages discovered during notmuch new.
Two use-cases are envisaged:
1) A chunk of messages was just dumped into the configured
directory by hand, and the
Wildcard matching was a feature of the probabilistic prefix, and we no
longer have it for the boolean prefix. Also note that top-level folder
can now be searched.
---
NEWS | 13 +++--
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/NEWS b/NEWS
index
Good for me, thank you.
signature.asc
Description: PGP signature
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
Hey, I'm playing around with the head of the git repository
(bc64cdce289d84be2550c4fccb1f008d15eaeb0e) to try to figure out how the
new folder: prefixes work, as folders are a critical part of how I
organize my mail. (Since tags are not hierarchical, folders are the
best way for me to group mail
Jani Nikula j...@nikula.org writes:
Sort the file while at it.
pushed to master.
d
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
On Fri, 02 May 2014, dm-list-email-notm...@scs.stanford.edu wrote:
Hey, I'm playing around with the head of the git repository
(bc64cdce289d84be2550c4fccb1f008d15eaeb0e) to try to figure out how the
new folder: prefixes work, as folders are a critical part of how I
organize my mail. (Since
Mark Walters markwalters1...@gmail.com writes:
Hi
Before checking other things: have you run notmuch new? That's needed to
update the database. It is an irreversible update so notmuch-0.17 will
not work with the updated database.
No, I haven't. Okay, so that must be it. Sorry for
Jani Nikula j...@nikula.org writes:
On Fri, 02 May 2014, dm-list-email-notm...@scs.stanford.edu wrote:
I'm using a pretty standard maildir++ layout. For example, underneath
my database.path I have a bunch of mail in directories such as:
.INBOX.Main/{new,cur}
.mail.class/{new,cur}
Hello David,
On Fri, May 02, 2014 at 02:16:07PM -0700, David Mazieres expires 2014-07-31 PDT
wrote:
Mark Walters markwalters1...@gmail.com writes:
Before checking other things: have you run notmuch new? That's needed to
update the database. It is an irreversible update so notmuch-0.17
On Fri, May 02, 2014 at 09:57:49PM -0700,
dm-list-email-notm...@scs.stanford.edu wrote:
Worse, because of my poor performance, I was hoping to segregate
messages by year. So it would be:
2013/.mail.class
2013/.mail.voicemail
2014/.mail.class
2014/.mail.voicemail
All the way
59 matches
Mail list logo
