for characters?
Thanks,
David
_______
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
This was driving me nuts for months.
David
___________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
HJhY3RvciDwn5Od?=
That subject line alone triggers the problem, because any search
returning that thread triggers the problem. When decoded, the subject
line ends with unicode code point 0x1F4DD (MEMO). Indeed, if I open up
a fresh emacs, and, independent of notmuch, type "C-x 8 RET memo RET"
Hey,
I'm using notmuch with mutt-kz. I'm running dspam (a bayesian spam classifier),
so I've got an imap folder called "learn_spam" and a folder called "learn_ham"
(for training dspam). Both folders are periodically emptied by dspam. I want to
define
David Bremner writes:
> Amadeusz Żołnowski writes:
>
>> What's more surprising is that there is a test case in notmuch test
>> suite which test whether after modifing tag of a mail it is moved from
>> new/ to cur/. Yes, it should be moved on any tag modification
Amadeusz =C5=BBo=C5=82nowski writes:
> What's more surprising is that there is a test case in notmuch test
> suite which test whether after modifing tag of a mail it is moved from
> new/ to cur/. Yes, it should be moved on any tag modification if I
> understand correctly. But
g the flags (which is
the same as what would happen if you set the tags manually with the
"notmuch tag" command).
A maildir file in the new/ directory can't have any tags (except the
implicit unread flag, which is indicated by the absence of "S" in the
end of the filenam
at there's a very simple answer, in which case
>> sticking it in the man page might be nice.
>
> I can't think of a simple, safe, and fast answer.
Okay, thanks. At least I wasn't missing something obvious.
> 2) when the lastmod changes go in, it seems lik
Sorry if this question is answered somewhere, but I'm wondering: What
is the best way to enable and disable maildir.synchronize_flags?
It seems that disabling it should simply be safe. But re-enabling, one
risks losing tags, as the next notmuch new will cause old maildir flags
to overrid
te so it wasn't
in my calendar."
I'm wondering if others have this problem and have figured the easiest
way to integrate notmuch with some kind of calendaring software that
generates ics or text/calendar attachments.
Thanks,
David
___________
notm
out also referring to Foo, fooing,
> and bar/foo.
>
> In your layout, if you also had 2013/.bar.foo, folder:foo would match
> that as well. To not match that, you would have to include each
> folder:.foo.xxx in the search.
First, thanks for the response. The responsiveness and frien
my maildirs have to have names like:
2013/.foo.foo
2013/.foo.bar
2013/.foo.baz
2014/.foo.foo
2014/.foo.bar
2014/.foo.baz
So if I want a way to aggregate all my foo mail in a single search,
right now I just ask for folder:foo. Will there be any
/{new,cur}
>> .mail.class/{new,cur}
>> .mail.voicemail/{new,cur}
>> ...
> Here's additional commentary on the specific queries.
>
>> linux7$ ./notmuch count folder:mail
>> 0
>> linux8$ ./notmuch count folder:.mail
>>
riod. For example, using notmuch as notmuch-0.17 and
./notmuch as notmuch-0.18-rc2+2~gbc64cdc, here's what I get:
linux2$ notmuch count folder:mail
16257
linux3$ notmuch count folder:mail.class
1896
linux4$ notmuch count folder:mail.voicemail
34
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 dou
it safer against the stuck-in-queue cases,
> but mails with older Date: headers would definitely get missed.
>
> The current output of notmuch count "*" is the same on both the client
> and the server, so it seems I didn't run into this problem yet (maybe I
> was
lly be
> used. Not to be discouraging ;).
The CLI is trivial. We'll just add another search keyword ctime
analogous to date.
As far as updating the test suite, etc., it's almost certain that the
core notmuch developers would be unsatisfied with whatever I've done,
since the code
't know whether the change was local or remote.
> How did you solve this?
Why don't you just set maildir.synchronize_flags=true? When I
synchronize mail across machines, I start by concurrently running
"notmuch new" on both the local and remote machines, which picks up all
th
=$MATCH
> }
interesting, I'll try hacking around that…
> Or if you are willing to switch to maildrop it has pcre and proper
> submatches.
or I may switch to maildrop, I used it at one point with courier for my
imag installation, but always stuck to procmail before switching to sup,
and
Hello,
I would like to report my experience with notmuch (newbie here).
I absolutely love it. I would like very much to continue using it, but I am
having a speed issue from inside Emacs.
I have installed notmuch 0.9, on OS X 10.6, using of course the chert database
format. I am also using
From: Dima Kogan
---
Hi.
I made a few improvements to the emacs UI. This patch allows the user to scroll
through the most recent searches with C-up and C-down while in the search box.
dima
emacs/notmuch-hello.el | 49 +--
1 files changed, 42
files to be compiled in this
+# See Makefile.local for the list of files to be compiled in this
# directory.
all:
$(MAKE) -C .. all
--
1.7.4.4
___
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch
From: Dima Kogan
---
Here's another improvement. In the notmuch-show display this binds '[' to
expand all the children messages (replies). Analogously ']' collapses all the
children messages.
dima
emacs/notmuch-show.el | 34 ++
At Tue, 25 Jan 2011 10:08:12 +1030,
Tim Stoakes wrote:
>
> I do something like this by using some shell scripts with formail, to
> 'store' notmuch tags into the X-Label headers of the individual mails.
> Offlineimap then syncs these headers. If I need the tags to become
One of the features I would like to see from notmuch is an easier
ability to synchronize tags across machines. At the very least, I
would need either incremental dump and restore, or some way to
communicate arbitrary tags to a local imap server that shares
notmuch's maildir (much as no
25 matches
Mail list logo
