Austin Clements writes:
> I'm not sure if it's a bad idea or not, but it's materially different
> from the tags in the config. The tags in the config persist and any
> call to notmuch new from any source (cron, 'G' in Emacs, etc.) will
> pick them up. Tags specified on the command line don't
Quoth David Bremner on Jul 12 at 4:08 pm:
> Austin Clements writes:
>
> > What happens when this script dies in the middle (say, your computer
> > loses power or notmuch tag conflicts with something else on the write
> > lock)? One advantage of the standard "new" tag approach is that it's
> >
Austin Clements amdra...@mit.edu writes:
I'm not sure if it's a bad idea or not, but it's materially different
from the tags in the config. The tags in the config persist and any
call to notmuch new from any source (cron, 'G' in Emacs, etc.) will
pick them up. Tags specified on the command
Austin Clements writes:
> What happens when this script dies in the middle (say, your computer
> loses power or notmuch tag conflicts with something else on the write
> lock)? One advantage of the standard "new" tag approach is that it's
> easy to write a stateless post-new tagging script that
Austin Clements amdra...@mit.edu writes:
What happens when this script dies in the middle (say, your computer
loses power or notmuch tag conflicts with something else on the write
lock)? One advantage of the standard new tag approach is that it's
easy to write a stateless post-new tagging
Quoth David Bremner on Jul 12 at 4:08 pm:
Austin Clements amdra...@mit.edu writes:
What happens when this script dies in the middle (say, your computer
loses power or notmuch tag conflicts with something else on the write
lock)? One advantage of the standard new tag approach is that
On Fri, May 02 2014, Austin Clements wrote:
>> 2) A periodic mail processing script wants to add new messages to
>>the database, then process those newly added messages to add
>>convenience tags, etc. without worrying about the user or other
>>instances of the script
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
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
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,
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
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
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
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
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
15 matches
Mail list logo
