David Bremner writes:
> Michael J Gruber writes:
>
>> At first I thought we (notmuch) might have a flushing problem or such,
>> which we should prevent. But this clearly looks like a glib2
>> regression now which caused others' CI to fail, too. At least you're
>> prepared in case of incoming
David Bremner writes:
> I also noticed that it does not happen for all png image parts, but the
> pattern of what works and what does not is also unclear to me so far. I
> observed that the following function
>
> (defun hideit ()
> (interactive)
> (overlay-put (car (last (overlays-at
Preston Miller Firestone <0x504...@disroot.org> writes:
> a. notmuch-start-notmuch warns the user about everything, while
> notmuch-call-notmuch-process only warns on errors.
I don’t see any errors using a nearly similar approach. This might be from more
async support in emacs.
> b.
Jon Fineman writes:
> This occurs using either:
>
> notmuch version 0.37 and emacs version 29.1 on Debian trixie/sid X11/XFCE
>
> or
>
> OpenBSD OpenBSD 7.3-current (GENERIC.MP) #1327 X11/awsomewm.
>
> I received an email with a hidden image/png. When I click on it, the
> image displays fine.
Lars Kotthoff writes:
> Hi all,
>
> I was wondering whether there's a way to query threads that have a certain
> number of messages, in addition to matching the rest of the query. I'm trying
> to find threads where I have sent an email (easy enough by just matching
> "from") but where I
On Sat Aug 12, 2023 at 1:28 PM CDT, Lars Kotthoff wrote:
> Hi all,
>
> I was wondering whether there's a way to query threads that have a certain
> number of messages, in addition to matching the rest of the query. I'm trying
> to find threads where I have sent an email (easy enough by just
Kevin Boulain writes:
> I would say it would be best to run all the tests with the different
> instrumentations enabled (for the best coverage) but I don't know if
> there's a CI. Or if out-of-tree compilation is supported, I guess the
> ASan and TSan tests could recompile the library with the
>
On 2023-07-22 at 15:48 -03, David Bremner wrote:
>
> I can't get this test to fail at all. I'm not sure what to conclude from
> that. This is on a 20 core system running linux.
I can't really remember what I did at the time but I believe only the
test is instrumented and not the Notmuch library.
Michael J Gruber writes:
> This might be completely unrelated, but I recall a strange problem I
> had with asan (not tsan): We build without asan, but if asan is
> present for whatever reason then the tests are run nonetheless. So we
> had to disable asan tests explicitly. Is your sexp compiled
Am Sa., 22. Juli 2023 um 20:48 Uhr schrieb David Bremner :
>
> Kevin Boulain writes:
>
> > The test fails quite reliably for me:
> > T810-tsan: Testing run code with TSan enabled against the library
> >PASS create
> >PASS query
> >FAIL sexp query
>
> I can't get this test to
Kevin Boulain writes:
> +
> +inline Xapian::Query
> +_sexp_initial_query (_sexp_initial_t initial)
My first thought was that this should be static, but maybe it doesn't
matter in C++; I see the other inline functions in that file are not
declared static.
> +}
> +assert (!
Kevin Boulain writes:
> The test fails quite reliably for me:
> T810-tsan: Testing run code with TSan enabled against the library
>PASS create
>PASS query
>FAIL sexp query
I can't get this test to fail at all. I'm not sure what to conclude from
that. This is on a 20 core
Andy Smith writes:
>
> What this means is that I see a message that looks like this:
>
> From: Joe Bloggs via somelist
> Message-ID:
> Subject: Joe's original subject
> References: (from Joe's post)
> In-Reply-To: (from Joe's post)
>
> That then contains a message/rfc822
eduled-to-run nil
> + "True if `notmuch-hello' is scheduled to run during the next
> +re-display, and set to nil afterwards.")
The control flow here is already pretty complicaed. I hope that we can
simplify it (drop use run-at-time) before adding any more features.
Tomi Ollila writes:
>> fi
>>
>> +if [ -n "${LD_PRELOAD-}" ]; then
>
> Is it problem to chain LD_PRELOADs here ? I see later in this message
> there is LD_PRELOAD's concatenated with :'s (in case non-empty) ?
>
It is not a problem in general, but ASAN insists on being first in
LD_PRELOAD, so
David Bremner writes:
> This obsoletes the series at id:20230409142627.2216080-1-da...@tethera.net.
>
I have applied this series (with some fixes from Tomi) to master.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email
Tomi Ollila writes:
>> -LD_PRELOAD=${LD_PRELOAD:+:$LD_PRELOAD}:./${shim_file} notmuch-shared
>> "$@"
>> +LD_PRELOAD=${LD_PRELOAD:+:$LD_PRELOAD}:./${shim_file} $notmuch_cmd "$@"
>
> hmm, should the "chaining" be done on other order (i.e. the shim_file
> before anything if there... (that
On Thu, Jul 20 2023, David Bremner wrote:
> Thanks to discussion with Olly Betts and some perf runs, I realized
> the current clean up of deleted files from the database is somewhat
> wasteful since it modifies the message documents (by deleting the
> filename) before in most cases deleting the
Am Fr., 21. Juli 2023 um 03:40 Uhr schrieb David Bremner :
>
> Michael J Gruber writes:
>
> > I'm not sure we should or can work around 2.77.0's behaviour. (It
> > might get triggered by the add/remove trick.)
>
> Will FC39 definitely ship with 2.77.0 ?
There is still plenty of time, so I hope
Michael J Gruber writes:
> I'm not sure we should or can work around 2.77.0's behaviour. (It
> might get triggered by the add/remove trick.)
Will FC39 definitely ship with 2.77.0 ?
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe
Am Do., 20. Juli 2023 um 20:54 Uhr schrieb Michael J Gruber
:
>
> Hi there,
>
> funny failures again during the mass rebuild for the (not quite yet)
> upcoming Fedora rebuild. This test passed just a few weeks ago, so the
> failure is related to something else changing. But still it shows that
>
* David Bremner [2023-07-19 12:26]:
> "Peter P." writes:
> >
> > Thanks David,
> > $ notmuch dump --output=/tmp/dump
> > runs without errors, albeit the dumped file is only 6.9MB while the
> > xapian folder has 851MB. Is this correct?
>
> Yes, that sounds about right. The dump only includes
"Peter P." writes:
>
> Thanks David,
> $ notmuch dump --output=/tmp/dump
> runs without errors, albeit the dumped file is only 6.9MB while the
> xapian folder has 851MB. Is this correct?
Yes, that sounds about right. The dump only includes the tags (it should
more or less make sense if you
* David Bremner [2023-07-18 12:33]:
> "Peter P." writes:
>
> > I am getting
> > Error while compacting: inflate failed (invalid stored block lengths)
> > with notmuch 0.37-1+b1 on Debian stable. What can I do about this?
>
> Can you successfully make a backup using "notmuch dump" (or do
"Peter P." writes:
> I am getting
> Error while compacting: inflate failed (invalid stored block lengths)
> with notmuch 0.37-1+b1 on Debian stable. What can I do about this?
Can you successfully make a backup using "notmuch dump" (or do you have
a recent backup?). In that case I would
Hello David,
David Bremner writes:
>>> Is anyone interested in debugging this failure? I can provide a copy of
>>> a failing mail off-list but don't have time myself to dive into the gory
>>> details of PGP/MIME verification right now.
[...]
> I got as far as verifying that the problem occurs
David Bremner writes:
> Sascha Silbe writes:
>
>
>> Is anyone interested in debugging this failure? I can provide a copy of
>> a failing mail off-list but don't have time myself to dive into the gory
>> details of PGP/MIME verification right now.
>>
>
> Not sure I have much time to devote to it
Sascha Silbe writes:
> Is anyone interested in debugging this failure? I can provide a copy of
> a failing mail off-list but don't have time myself to dive into the gory
> details of PGP/MIME verification right now.
>
Not sure I have much time to devote to it myself, but if you send me one
of
On Sun, Jul 09 2023, David Bremner wrote:
Note: I almost commented cases where it was not ensured that variable
is defined, to notice later that those were actually defined for sure
-- so in some previous mails in this series I may have missed
same cases.
The comments for this message may be
On Sun, Jul 09 2023, David Bremner wrote:
> python3 will work for many people, and reduce the friction to running
> the tests without running configure first.
> ---
> test/test-lib-common.sh | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/test/test-lib-common.sh
On Sun, Jul 09 2023, David Bremner wrote:
> Messages can have empty bodies, but empty files are not messages.
> ---
> test/test-lib.sh | 8
> 1 file changed, 8 insertions(+)
>
> diff --git a/test/test-lib.sh b/test/test-lib.sh
> index 1a6525df..b5aa94dd 100644
> --- a/test/test-lib.sh
>
On Sun, Jul 09 2023, David Bremner wrote:
> When running the test suite without building first, it is desirable to
> have the tests consider these variables being undefined as equivalent
> to the feature not being present, and in particular for the tests not
> to generate errors.
> ---
...
> diff
Rudolf Adamkovič writes:
>
> Rudy
> From 278017d06bb986f4ec99118bfcfdec8dab970f2b Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Rudolf=20Adamkovi=C4=8D?=
> Date: Thu, 25 May 2023 16:22:08 +0200
> Subject: [PATCH 1/2] emacs: fix notmuch-hello layout when
> display-line-numbers-mode is on
>
> ---
>
Tim Culverhouse writes:
> Include the 'excluded' field in the structured output schema.
applied to master. Sorry it took so long,
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
David Bremner writes:
> In the decade (!) since this corpus was last updated, the keyserver
> network is essentially dead, and I have migrated gpg keys. Bump the
> version number as a clean way of switching signatures. Also update the
> instructions to suggest using "--locate-external-key" to
David Bremner writes:
> According to my reading of RFC5322, there is an obsolete syntax for
> Message-Id which permits folding whitespace (i.e. to be removed /
> ignored by parsers). In [1] Paul Wise observed that notmuch removed
> whitespace on indexing, but does not do any corresponding
>
David Bremner writes:
> The ownership is implicit in the const declaration (I think!), but
> that does not show up in the doxygen generated API docs.
Applied to master
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email
Am So., 9. Juli 2023 um 16:57 Uhr schrieb David Bremner :
>
> michaeljgruber+grubix+...@gmail.com writes:
>
> > From: Michael J Gruber
> >
> > Py 3.12 finally pulled the plug on the `SafeConfigParser` class which
> > has been deprecated since py 3.2.
>
> Applied to master.
>
> Apropos, how many
michaeljgruber+grubix+...@gmail.com writes:
> From: Michael J Gruber
>
> Py 3.12 finally pulled the plug on the `SafeConfigParser` class which
> has been deprecated since py 3.2.
Applied to master.
Apropos, how many people are still using the legacy bindings?
d
talled which reports
version 1.4.22-1 and I *might* have ran out of disk space in the not too
distant past.
> > >> 2) Move the database out of the way, re-run notmuch new,
> > >> and restore your state using "notmuch restore < notmuch-db.txt"
> > >
with handling
commit() failure on disk full.
> >> 2) Move the database out of the way, re-run notmuch new,
> >> and restore your state using "notmuch restore < notmuch-db.txt"
> >
> > I'd be fine regenerating the entire database without a backup dump even
(to notmuch-list only)
* David Bremner [2023-07-03 14:26]:
[...]
> >> 2) Move the database out of the way, re-run notmuch new,
> >> and restore your state using "notmuch restore < notmuch-db.txt"
> >
> > I'd be fine regenerating the entire datab
de is known/fixable. I'd guess probably
not fixable.
>> 2) Move the database out of the way, re-run notmuch new,
>> and restore your state using "notmuch restore < notmuch-db.txt"
>
> I'd be fine regenerating the entire database without a backup dump even,
>
xapian and include its messages below at the
end of this mail. Everyone please forgive me for pasting 1121 there. :)
> 2) Move the database out of the way, re-run notmuch new,
> and restore your state using "notmuch restore < notmuch-db.txt"
I'd be fine regenerating the entire d
e
parts of xapian, so write again.
1) install xapian-tools and run
$ xapian-check ~/.local/share/notmuch/default/xapian
This is mainly for (my) curiousity, but it may highlight some database
corruption or if xapian reports no errors that leans more towards a
notmuch bug.
2) Move the databa
Jan Detke writes:
> I got a problem using hooks with notmuch (Version 0.37-3). I specified
> the hook directory under [database] in my notmuch config. The script
> (post-new.sh) is executable and works when invoked manually in the
> terminal, but it does not get executed after invoking notmuch
>
On Fri, Jun 16 2023, michaeljgruber wrote:
> From: Michael J Gruber
>
> Py 3.12 finally pulled the plug on the `SafeConfigParser` class which
> has been deprecated since py 3.2.
>
> We use it in the legacy bindings only, so take the easy route of
> importing `ConfigParser` as `SafeConfigParser`
Paul Wise writes:
> This prevents data loss when users configure the search cache Maildir to be a
> real Maildir containing their real mail data, since the search cache Maildir
> is expected to contain only symlinks to the real mail data.
>
> Prevents:
Was there a change from V2? I might have
Paul Wise writes:
> This prevents data loss when users configure the search cache Maildir to be a
> real Maildir containing their real mail data, since the search cache Maildir
> is expected to contain only symlinks to the real mail data.
>
> Prevents:
v2 applied to master
original database will be there if something crashes.
> If I have to reindex it, that is going to take even longer, so I
> have to think about how much I want what is probably a very marginal
> amount of space back!
Compaction should be substantially faster than re-indexing.
Hi Andy,
I'm really glad the compaction was so successful!
I think the Xapian folks deserve the big credit for this, more than any
code specific to notmuch, (other than user interface and safety
checking/backup, etc.).
I'm really glad you're finding notmuch helpful. And I'm glad you felt
Hi Michael,
On Sun, Jun 18, 2023 at 01:36:30PM +0200, Michael J Gruber wrote:
> On my comparatively small db, gains are typically substantial
> (postlist, position), even though I compact from time to time.
Thanks for your help. The savings were indeed a lot more than I
expected (and the compact
Am Sa., 17. Juni 2023 um 23:49 Uhr schrieb Andy Smith :
>
> Hi,
>
> I'm using v0.31.4 on Debian 11. I have ~3.9 million messages in my
> archive and the notmuch database currently takes up 85GiB (though
> actually "only" 51GiB due to btrfs zstd:1 compression).
Wow ;)
> I did remove a few hundred
Michael J Gruber writes:
>
> This one I can fix by serializing the test suite. For whatever reasons
> it fails on newer Fedoras when looping through the different tree mode
> tests (in parallel).
>
>> T350-crypto
>> T357-index-decryption
Because parallel testing only affects running different
Am Di., 30. Mai 2023 um 18:57 Uhr schrieb Michael J Gruber
:
>
> Am Sa., 27. Mai 2023 um 14:31 Uhr schrieb David Bremner :
> >
> > Michael J Gruber writes:
> > >
> > > Are all gpg related tests emacs based? Either gpg or emacs is the red
> > > herring here, or both ...
> >
> > The issue (at least
Am Sa., 27. Mai 2023 um 14:31 Uhr schrieb David Bremner :
>
> Michael J Gruber writes:
> >
> > Are all gpg related tests emacs based? Either gpg or emacs is the red
> > herring here, or both ...
>
> The issue (at least on rawhide) seems to be the interaction between gpg
> and emacs
>
>
Am Sa., 27. Mai 2023 um 14:59 Uhr schrieb David Bremner :
>
> David Bremner writes:
>
> >
> > I'm not sure if this is the main issue, but in commit bf8aa34324cc91a
> > that key was replaced by an ed255519 key
> > 9A3AFE6C60065A148FD4B58A7E6ABE924645CC60
> >
> > Did the fedora sources get out of
Felipe Contreras writes:
> Signed-off-by: Felipe Contreras
> ---
> bindings/ruby/database.c | 45
> bindings/ruby/defs.h | 6 ++
> bindings/ruby/init.c | 2 ++
> 3 files changed, 53 insertions(+)
So, usual request about tests...
> +/*
>
Felipe Contreras writes:
> Signed-off-by: Felipe Contreras
> ---
> bindings/ruby/defs.h | 3 +++
> bindings/ruby/directory.c | 19 +++
> bindings/ruby/init.c | 1 +
> 3 files changed, 23 insertions(+)
>
> diff --git a/bindings/ruby/defs.h b/bindings/ruby/defs.h
>
Felipe Contreras writes:
> +
> +/*
> + * call-seq: DB.revision => Array
> + *
> + * Returns the commutted database revision and UUID.
typo.
> + */
> +VALUE
> +notmuch_rb_database_revision (VALUE self)
> +{
> +notmuch_database_t *db;
> +unsigned long rev;
> +const char *uuid;
> +
>
Felipe Contreras writes:
> In order to make it more extensible.
>
> No functional changes.
>
applied to master
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
David Bremner venit, vidit, dixit 2023-05-12 21:17:45:
> Michael J Gruber writes:
>
> > oh well, attachments ...
> >
>
> Can you encrypt to the key 6D92612D94E46381 interactively using an
> approriately simplified version of that command?
Took me a while, sorry. In that chroot:
```
sh-5.2#
On Sat, 2023-05-27 at 21:10 -0300, David Bremner wrote:
> If possible, please use git-send-email for future series.
Will do, I forgot about the --cover-letter option.
> This seems to have introduced a warning, and I think there's a bug.
>
> % notmuch mutt search tag:inbox
> Argument "new"
Paul Wise writes:
> I think a better option is to detect if the search cache Maildir is
> actually a Maildir and doesn't contain any data that could be lost.
>
> I have attached three patches I created to improve notmuch-mutt safety.
If possible, please use git-send-email for future series.
>
Paul Wise writes:
> This should be be slightly faster since it avoids forking a shell
> and is less code in and less dependencies for the script.
>
> Since String::ShellQuote isn't used elsewhere, drop mention of it.
applied to master.
d
___
notmuch
David Bremner writes:
>
> I'm not sure if this is the main issue, but in commit bf8aa34324cc91a
> that key was replaced by an ed255519 key
> 9A3AFE6C60065A148FD4B58A7E6ABE924645CC60
>
> Did the fedora sources get out of synch somehow?
>
> d
>
> PS. Currently spinning up a Fedora Rawhide VM to
Michael J Gruber writes:
>
> Are all gpg related tests emacs based? Either gpg or emacs is the red
> herring here, or both ...
The issue (at least on rawhide) seems to be the interaction between gpg
and emacs
https://dev.gnupg.org/T6481
A fix seems to be in progress. Do you have problems
Michael J Gruber writes:
> David Bremner venit, vidit, dixit 2023-05-12 21:17:45:
>> Michael J Gruber writes:
>>
>> > oh well, attachments ...
>> >
>>
>> Can you encrypt to the key 6D92612D94E46381 interactively using an
>> approriately simplified version of that command?
>
> Took me a while,
[now from the subscribed address, sorry]
David Bremner venit, vidit, dixit 2023-05-12 21:17:45:
> Michael J Gruber writes:
>
> > oh well, attachments ...
> >
>
> Can you encrypt to the key 6D92612D94E46381 interactively using an
> approriately simplified version of that command?
Took me a
Paul Wise writes:
> Suggested-by: isutf8 & check-all-the-things
Applied to master.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
s we discussed, I can't meaningfully review the vimscript parts (and
nobody else seems interested / willing). I've (re?) enabled push access
for you at
g...@git.notmuchmail.org:notmuch
For now the access is to everything under vim/. We can discuss direct
access for the ruby bin
Felipe Contreras writes:
> The order was wrong, right now `query.sort` doesn't return a number.
>
applied to master
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
David Bremner wrote:
> Carl Worth writes:
>
> > What it could also do is create some placeholder file like
> > .NOTMUCH-MUTT-OUTPUT-DIR when it writes its output. And then it could
> > check for that file's existence before removing a directory.
>
> Sounds reasonable to me. Would someone like
David Bremner writes:
> The notmuch git repo is now hosted in gitolite [1]. This will allow more
> fine-grained access control. There should not be any visible change to
> https access, but let me know if something broke.
Michael Gruber mentioned offlist that git:// cloning was broken. While I
Michael J Gruber writes:
> oh well, attachments ...
>
Can you encrypt to the key 6D92612D94E46381 interactively using an
approriately simplified version of that command?
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email
oh well, attachments ...
Am Fr., 12. Mai 2023 um 19:42 Uhr schrieb Michael J Gruber
:
>
> Am Do., 11. Mai 2023 um 22:49 Uhr schrieb David Bremner :
> >
> > Michael J Gruber writes:
> >
> ...
> > > T350-crypto: Testing PGP/MIME signature verification and decryption
> ...
> > > PASS signature
Am Do., 11. Mai 2023 um 22:49 Uhr schrieb David Bremner :
>
> Michael J Gruber writes:
>
...
> > T350-crypto: Testing PGP/MIME signature verification and decryption
...
> > PASS signature verification with signer key unavailable
> > ```
> > There the suite "hangs" for about 2 minutes, followed
Michael J Gruber writes:
> Building notmuch 0.37 with my usual spec-file as a rawhide-mock build
> (a local chroot for the development "version" of Fedora which will
> become Fedora 39) I see:
> ```
> T350-crypto: Testing PGP/MIME signature verification and decryption
> PASS emacs delivery of
David Bremner wrote:
> Felipe Contreras writes:
>
> > These are some trivial patches long overdue from upstream.
> >
> > They have been already sent in some form long time ago
> > id:20210418224851.88240-3-felipe.contre...@gmail.com, but hopefully in a
> > smaller batch they'll get merged.
>
>
Felipe Contreras writes:
> These are some trivial patches long overdue from upstream.
>
> They have been already sent in some form long time ago
> id:20210418224851.88240-3-felipe.contre...@gmail.com, but hopefully in a
> smaller batch they'll get merged.
>
applied to master. Of course I still
mohk...@kisara.moe writes:
> From: Mohsin Kaleem
>
thanks for writing such an extensive set of tests for the new
feature. All I'd ask is a bit more detail in the commit message.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe
mohk...@kisara.moe writes:
> From: Mohsin Kaleem
>
Apologies for the many messages. I think this commit message falls a bit
short of our usual standards (as well as a one line subject, we like to
have some kind of "why"). If you figure out the right answer to toggling
saved searches with
mohk...@kisara.moe writes:
> Lastly I've amended some calls to notmuch-tree and notmuch-unthreaded
> which didn't pass through the buffer local value of
> notmuch-search-oldest-first (and now notmuch-search-exclude).
> Examples of where I've done this
> + include notmuch-jump-search
if
mohk...@kisara.moe writes:
> + :excludedWhether to show mail with excluded tags in the
> + search. Possible values are `hide', `show',
> + or nil. Nil means use the default value of
> + `notmuch-search-hide-excluded'.
So if I
Mohsin Kaleem writes:
> We could workaround this by changing the semantics of the variable. Make
> it notmuch-search-show-excluded and default to nil so nothing has to be
> changed in existing functions that call notmuch-search. Or we could
> switch to using cl-defun and have the default value
David Bremner writes:
>> diff --git a/test/T310-emacs.sh b/test/T310-emacs.sh
>> index 9d0df187..b89a100e 100755
>> --- a/test/T310-emacs.sh
>> +++ b/test/T310-emacs.sh
>> @@ -1030,7 +1030,7 @@ End of search results.
>> YYY/notmuch_fail exited with status 1 (see *Notmuch errors* for more
>>
> diff --git a/test/T310-emacs.sh b/test/T310-emacs.sh
> index 9d0df187..b89a100e 100755
> --- a/test/T310-emacs.sh
> +++ b/test/T310-emacs.sh
> @@ -1030,7 +1030,7 @@ End of search results.
> YYY/notmuch_fail exited with status 1 (see *Notmuch errors* for more details)
> === ERROR ===
>
On Wed May 3, 2023 at 2:35 PM CDT, David Bremner wrote:
> > We have had some discussions on the pros and cons of more publically
> > documenting this interface, but for now you can find the documentation
> > in the source, in devel/schemata.
>
> See attached.
Perfect! Thanks!
--
Tim
David Bremner writes:
> "Tim Culverhouse" writes:
>
>> Hey everyone -
>>
>> I've scoured the manpages and website for some documentation on the JSON
>> output format, but haven't found what I'm looking for. For the most
>> part, the commands are easy to figure out, but `notmuch show` has me
>>
"Tim Culverhouse" writes:
> Hey everyone -
>
> I've scoured the manpages and website for some documentation on the JSON
> output format, but haven't found what I'm looking for. For the most
> part, the commands are easy to figure out, but `notmuch show` has me
> confused on the array nesting.
> I would find this helpful too.
I just implemented this for tags (patch attached). Turns out it is not needed
for authors as notmuch already distinguishes between matched and unmatched
authors -- I never noticed!.
The implementation could of course be debated and improved, but I just wanted
On Wed, 03 May 2023, Al Haji-Ali wrote:
> When I search for emails (in the CLI or Emacs), for example all those with
> the inbox tag, I get a list of threads with the names of all senders in the
> thread and all tags that are in the thread rather than in the matched
> messages.
>
> I find this
* 2023-05-02 16:44:22+0100, Al Haji-Ali wrote:
> When I search for emails (in the CLI or Emacs), for example all those
> with the inbox tag, I get a list of threads with the names of all
> senders in the thread and all tags that are in the thread rather than
> in the matched messages.
In Emacs
ID in `In-Reply-To` to be
grouped with unrelated messages from a completely separate thread).
But then I deleted the draft (including the file), ran `notmuch new` and re-ran
the script and the problematic ghost message was correctly reported.
So this approach would work to find un-referenced messages,
David Bremner writes:
> Al Haji-Ali writes:
>
>> So it does seem to be a lingering ghost message, but I am sure that there
>> are no messages in the database referring to this ID (except messages in
>> this current thread which have the ID in the message body).
>> I don't know why this
Side note for the morbidly curious: Getting notmuch-vim operational on
my production servers took some work. Gentoo Linux's net-mail/notmuch
ebuild does not currently create Ruby bindings (only Python).
Given that Gentoo supports packages having multiple versions installed
simultaneously, Ruby
On 22/04/2023, David Bremner wrote:
> You need to give the appropriate term prefix. Q for message id,
> or XREPLYTO or XREFERENCE as in my last message.
My apologies. I misunderstood the syntax.
>> The first one is the draft. The second hit is the reason I thought the
>> only place left for
>
> As long as some message refers to that ID, notmuch will create a "ghost
> message", used for threading.
You can look for a specific ghost message with something like
$ quest -btype:T -b id:Q -d .local/share/notmuch/default/xapian \
"type:ghost and
Al Haji-Ali writes:
> is completely unconnected the other 4 messages in the thread. Note
> that if I change the "In-Reply-To" field in this message to anything
> else, notmuch no longer groups these 5 messages into a single thread.
>
Yes, that's puzzling. I did not think about "ghost messages"
Thanks David for the script and the instruction. I am still not sure where
notmuch is getting the association between my 5 messages in the thread.
The attached pdf is the output of the script. As you can see the draft
"draft-m25y9oqhep@gmail.com" which contains the header
,
| From: Al
301 - 400 of 17173 matches
Mail list logo
