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 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
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.
d
[1] a front end for git, see https://gitolite.com
signature.asc
Description: PGP signature
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
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
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
> 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 ===
>
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
"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.
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 bo
>
> 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"
Al Haji-Ali writes:
> I changed the message, removed "B" from "References" and deleted the
> files of all old (and intermediate) drafts that have "B" in
> "References". But no matter what I do, I have "B" grouped with "D"
> and any other messages which I create with "In-Reply-To" being "A".
James Cook writes:
> It is possible that a short note indicating that detailed descriptions
> will follow, placed at the top of the man page and/or at the top of the
> "Functions" section, would have saved me from my impatience. I think I
> do tend to read the first sentence or two of a man page
James Cook writes:
> Hi list,
>
> If I'm not mistaken, calling notmuch_database_open_with_config with
> config_path = NULL causes notmuch to try to find the config file
> automatically.
>
> It would be nice if that were documented in the notmuch(3) man page. I
> can try drafting a patch if that
Jakub Wilk writes:
> ---
> doc/man1/notmuch-config.rst | 2 +-
> doc/man1/notmuch-git.rst | 4 ++--
> doc/man7/notmuch-sexp-queries.rst | 8
> doc/notmuch-emacs.rst | 6 +++---
> 4 files changed, 10 insertions(+), 10 deletions(-)
applied to master,
thanks
Felipe Contreras writes:
> Not used anymore now that we return an array of strings directly.
series applied to master, with one whitespace tweak in patch 2/3
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to
Paul Wise writes:
> that changes the meaning of the query but I couldn't find any way to
> prevent an arbitrary Message-Id from inserting parentheses into the
> query. Also notmuch converts Message-Id (test)@hostname to just
> @hostname in the Xapian database. I think that right now I am not
Paul Wise writes:
> So I think that it would be good if there were a library for notmuch
> query construction that would take care of all the different quoting
> levels, Message-Id munging etc. This could then get language bindings
> so that notmuch based tools and MUAs could use them for
We generate output to stderr for BROKEN tests, which are not failures,
so tell the test runner not to fail because of output on stderr.
---
debian/tests/control | 17 +
1 file changed, 17 insertions(+)
create mode 100644 debian/tests/control
diff --git a/debian/tests/control
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.
We know the test suite is tied to bash anyway, so this is a simple
fix.
---
test/T060-count.sh | 2 +-
We put some effort into testing the built copy rather than some
installed copy. On the other hand for people like packagers, testing
the installed copy is also of interest.
When NOTMUCH_TEST_INSTALLED is set to a nonempty value, tests do not
require a built notmuch tree or running configure.
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
+++ b/test/test-lib.sh
@@ -388,6 +388,14 @@
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 b/test/test-lib-common.sh
index 18fa29c0..4d14e0b3 100644
---
Compared to the previous version [1], the first patch is now applied,
and the setup for running without configure now relies on the various
NOTMUCH_HAVE_* environment variables working OK when unset. This
allows eliminating the "defaults.sh". There is also some added
documentation on how to use
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 to make a patch for
notmuch-mutt?
Paul Wise writes:
> +search($results_dir, $remove_dups, qq{thread:"{id:$mid}"});
did you test this with a message-id with spaces in it? the quoting is a
delicate.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email
Felipe Contreras writes:
> On Tue, Apr 4, 2023 at 12:54 PM David Bremner wrote:
>>
>> This sounds right. Can we use the detection of missing messages in
>> wr_export to reset the appropriate counters? It looks like yes, given
>> the call to store_lastmod.
Felipe Contreras writes:
> On Mon, Apr 3, 2023 at 6:37 PM David Bremner wrote:
> Or we could say that after jumping a certain threshold of lastmod we
> delete all the messages and start from scratch, perhaps every 1000
> revisions.
>
> Or maybe the query could gene
Felipe Contreras writes:
>
> I'm not familiar with git-annex, I would need to see an example of
> such merging happening.
I was confused, git-annex is using the builtin merge strategy "union",
which is not eliminating duplicates or sorting, so probably not
applicable here. I still have to try
Felipe Contreras writes:
>
> That should work to update existing tags, but how are we going to
> detect if a message has disappeared? Or is that not a thing?
Indeed the same thought had occurred to me not long ago. I remembered
(belately) that I'd been through some similar thought process with
David Bremner writes:
> Indeed that speeds up the initial clone on this machine from 39 minutes
> (I switched machines) to 30s. I will play with it a bit more, and report
> back.
It's not a showstopper, but "git pull" takes about 1/2 the wall time
(about 2/3 of the CPU ti
Felipe Contreras writes:
> By distributing the files in multiple directories like notmuch-git
> does using BLAKE2b, the operation is much faster.
>
> I've pushed the changes, now there's a dependency, but you can just
> `gem install blake2b`.
>
> I'm able to clone the database of the performance
Fulvio Pizzigoni writes:
>
> After this my .mutt directory (~ 4 GB di mail-boxess) appears so:
> fulvio@linux:~$ ll .mutt
> totale 12
> drwxr-xr-x 2 fulvio fulvio 4096 18 feb 20.32 cur
> drwxr-xr-x 2 fulvio fulvio 4096 18 feb 20.32 new
> drwxr-xr-x 2 fulvio fulvio 4096 18 feb 20.32 tmp
Hi
David Bremner writes:
>
> I'm intrigued (and indeed I hadn't really thought about the degree to
> which we were re-inventing git-fast-import and friends); however so far
> my experiments did not get far enough to say anything conclusive.
>
I did manage to finish, about 70
Sometimes merging is not what we want with tags; in particular it
tends to keep tags in the local repo that have been removed elsewhere.
This commit provides a new reset command; the reset itself is trivial,
but the work is to provide a safety check that uses the existing
--force and
Felipe Contreras writes:
> Hi,
>
> I noticed you promoted notmuch-git as a user tool to toy around with it.
>
> Very quickly I realized that most of what it does is something I've
> been working on for at least 10 years: making git work with other
> tools.
>
> I presume you haven't heard of git
David Bremner writes:
> This obsoletes the series starting with
>
> id:20220903232839.1473915-2-da...@tethera.net
>
> Compared to that series this is rebased against master, it has some
> more tests (including both positive and negative tests) and it
> documents
Felipe Contreras writes:
> We don't need a Tags enumerable object only for a small number of strings, we
> can just get them directly.
>
> This fixes an interaction problem where we might request two tags iterables
> from the same message:
>
> tags_0 = notmuch_message_get_tags(message);
I
Kevin Boulain writes:
> This replaces two instances of Xapian::Query::MatchAll with the
> equivalent but thread-safe alternative Xapian::Query(std::string()).
> Xapian::Query::MatchAll maintains an internal pointer to a refcounted
> Xapian::Internal::QueryTerm.
>
Applied to master, thanks, and
Felipe Contreras writes:
> Essentially we want to do notmuch_database_open_with_config() and load the
> default database.
>
Applied to master. Thanks for this change, both are things I'd wanted to
fix.
d
___
notmuch mailing list --
Kevin Boulain writes:
> It wasn't covered, though it shares most of its implementation with
> notmuch_message_remove_all_properties.
I have applied this series to master, with one commit added in the
middle
commit 336334996750240608d5f29ed5dd8e40a69c4d79
Author: David Bremner
Date: T
Kevin Boulain writes:
> These two functions don't fail gracefully when editing a removed
> message:
> BROKEN edit property on removed message without uncaught exception
> --- T610-message-property.20.EXPECTED 2023-02-27 11:33:25.792764376
> +
> +++
Kevin Boulain writes:
>
> Yeah, talloc's documentation confirms that when the context is free'd
> every child is also free'd. Not quite sure what style is preferred
> (explicit or implicit, implicit sure leads to nicer code here).
In general implicit de-allocation is fine.
Kevin Boulain writes:
> On 2023-03-03 at 00:39 +02, Tomi Ollila wrote:
>> Somehow testkey1 = testvalue1 disappeared from the test code (which is
>> probably expected -- perhaps the commit message of the *change* 1/2
>> tried to point to that ;D)
>
> Yes, that proves
Kevin Boulain writes:
> +== stderr ==
> +A Xapian exception occurred at message-property.cc:XXX: No termlist for
> document 54
> +EOF
> +test_expect_equal_file EXPECTED OUTPUT
> +
> +add_email_corpus
Hi Kevin;
Thanks for the speedy update. I hate to do this but I think the message
is now
Felipe Contreras writes:
> We don't need a FileNames enumerable object only for a small number of
> strings,
> we can just get them directly.
>
> This iterator is meant to be transient and works only once, so we better just
> iterate it once.
>
> This is the same approach I took with the Tags
Kevin Boulain writes:
> Since libnotmuch exposes a C interface there's no way for clients to
> diff --git a/test/T610-message-property.sh b/test/T610-message-property.sh
> index 944e1810..f7cabe4d 100755
> --- a/test/T610-message-property.sh
> +++ b/test/T610-message-property.sh
> @@ -363,7
Atanas Janackovski writes:
> I have justed strated using `notmuch' in Emacs (doom configuration), and I
> love
> it! However, there are a couple of things I'd like help with.
>
> 1. I have a number of accounts that I use. How do I configure my config to
> save
>draft messages based on the
Antoine Beaupré writes:
>
> Still, one has to wonder: if emacs can just dump core if someone messes
> with my eln-cache, that's... bad, no?
Yes, it is bad, but the native compilation functionality is new, so
hopefully things will get better over time.
Kevin Boulain writes:
> Likely missed in 86cbd215e, when notmuch_query_search_messages_st was
> renamed to notmuch_query_search_messages.
> ---
Applied to master, thanks.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an
Kevin Boulain writes:
> This is what can be expected from the tests when they fail:
>== stderr ==
> +==
> +WARNING: ThreadSanitizer: data race (pid=207931)
> + Read of size 1 at 0x7b1001a0 by thread T2:
> +#0 memcpy (libtsan.so.2+0x62506)
> +#1 void
Kevin Boulain writes:
>
> Thoughts? Should clients using the library gate every function call to
> Notmuch behind a lock instead?
Ideally that should not be necessary. On the other hand, it may take some time
to fix
issues with concurrent access.
> I can also start a discussion in sfsexp's
Kevin Boulain writes:
> Likely missed in 86cbd215e, when notmuch_query_search_messages_st was
> renamed to notmuch_query_search_messages.
> ---
> lib/notmuch.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/notmuch.h b/lib/notmuch.h
> index ce375c04..73e246e0
David Bremner writes:
> Alex Murray writes:
>
> I tried replacing indent-rigidly with a simplified version the and that
> leaves the image inserted, but unfortunately doesn't indent it
> properly. If you want to play with it, my half working patch is
> attached.
>
but then
apparently deleted by indent-rigidly (probably because it looks like
whitespace).
I tried replacing indent-rigidly with a simplified version the and that
leaves the image inserted, but unfortunately doesn't indent it
properly. If you want to play with it, my half working patch is
attached
Antoine Beaupré writes:
> When I have the attached email in my `inbox` and hit ENTER on the email
> (notmuch-search-show-thread here), Emacs crashes completely with:
>
> fév 22 11:57:10 angela emacs[112721]:
>
Kevin Boulain writes:
> The documentation of MatchNothing says it's thread-safe.
>
> If you'd like, I'm happy to submit a patch (likely very small, given the
> limited number of occurrences) after I review a bit more the
> documentation and the code (I'm just starting with Notmuch and Xapian so
David Bremner writes:
> Apparently the macro setq-local only takes two arguments in Emacs 26.1
> ---
> emacs/notmuch-tree.el | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/emacs/notmuch-tree.el b/emacs/notmuch-tree.el
> index 1477
Kevin Boulain writes:
> So, is Notmuch expected to be thread safe? There are some indications it
> should be (e.g.: lib/init.cc has locking) but all instances of
> Xapian::Query::MatchAll would have to be replaced.
> Xapian states it's thread safe:
>
Apparently the macro setq-local only takes two arguments in Emacs 26.1
---
emacs/notmuch-tree.el | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/emacs/notmuch-tree.el b/emacs/notmuch-tree.el
index 14775d59..b58fa6a6 100644
--- a/emacs/notmuch-tree.el
+++
David Bremner writes:
> This one use a more reasonable error code. As far as showing up every
> time, it does if I use --full-scan. That is the same (for me) as
> non-email files.
series applied to master.
d
___
notmuch mailing list -
"Jose A. Ortega Ruiz" writes:
> On Mon, Dec 26 2022, David Bremner wrote:
>
>> Amended by db: Copy docstring to manual and edit for presentation. Add
>> two tests.
>
> Thanks for the grunt work, David. Just a comment on a sloppy comment of
> mine below:
>
Jon Fineman writes:
> When I try and open one specific email, I get a message of
> "Fontifying..." and then the mouse pointer turns into a watch.
>
> If I C-G it breaks out and shows the email message with a red warning
> at the top of "[some mark read tag changes may have failed]", but
> since
David Bremner writes:
> Michael J Gruber writes:
>
>>
>> Yes, the extra ones all are ghosts, and I slowly remember that they
>> scared me in the past already ...
>>
>> These ghosts appear to be pretty common. It happens all the time that
>> I am joine
Michael J Gruber writes:
>
> Yes, the extra ones all are ghosts, and I slowly remember that they
> scared me in the past already ...
>
> These ghosts appear to be pretty common. It happens all the time that
> I am joined to an existing discussion thread where I do not have all
> references.
I
The most interesting case is probably tags with a small number of
uses, since these could be typos or similar errors.
---
test/T083-sexpr-count.sh | 8
1 file changed, 8 insertions(+)
diff --git a/test/T083-sexpr-count.sh b/test/T083-sexpr-count.sh
index 858aa8bf..1be3f62d 100755
---
---
test/T083-sexpr-count.sh | 21 +
1 file changed, 21 insertions(+)
diff --git a/test/T083-sexpr-count.sh b/test/T083-sexpr-count.sh
index f3010d11..858aa8bf 100755
--- a/test/T083-sexpr-count.sh
+++ b/test/T083-sexpr-count.sh
@@ -112,4 +112,25 @@ notmuch@notmuchmail.org
In this initial commit, support all term based fields, but only
document/test the thread size feature.
---
lib/parse-sexp.cc| 65 ++--
test/T083-sexpr-count.sh | 30 +++
2 files changed, 79 insertions(+), 16 deletions(-)
create mode
---
test/T083-sexpr-count.sh | 85
1 file changed, 85 insertions(+)
diff --git a/test/T083-sexpr-count.sh b/test/T083-sexpr-count.sh
index e825ef3d..f3010d11 100755
--- a/test/T083-sexpr-count.sh
+++ b/test/T083-sexpr-count.sh
@@ -27,4 +27,89 @@ cat
---
test/T083-sexpr-count.sh | 8
1 file changed, 8 insertions(+)
diff --git a/test/T083-sexpr-count.sh b/test/T083-sexpr-count.sh
index 1be3f62d..b1c0a3ac 100755
--- a/test/T083-sexpr-count.sh
+++ b/test/T083-sexpr-count.sh
@@ -141,4 +141,12 @@ test_begin_subtest "no tag is used less
This updates and obsoletes the series at [1]. The backend that
constructs queries is unmodified from that series, but the parser now
allows the use of count modifier in several more places. Basically
there is not much more code to maintain to do it for any field based
on terms (notably not date),
on few / many messages.
+ *
+ * This file is part of notmuch.
+ *
+ * Copyright © 2023 David Bremner
+ *
+ * This program is free software: you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation, either version
Michael J Gruber writes:
> That is really weird:
> ```
> xapian-delve -t G00021229 .
> Posting List for term 'G00021229' (termfreq 115, collfreq 0,
> wdf_max 0): 146259 ...
> ```
> with 115 record numbers, all different.
> Doing `xapian-delve -1r` for each of them and grepping
Michael J Gruber writes:
>
> It has 5, as confirmed by the search output and that of `notmuch
> count`. But it is matched by `count 115`.
> `xapian-check` is happy. (There used to be some issue with additional
> thread entries at some point.)
>
> Michael
A simple test to try is
% xapian-delve
Michael J Gruber writes:
> I am getting a few surprising matches, e.g.
> ```
> notmuch search --query=sexp '(thread (count 115)))'
> thread:00021229 2021-05-17 [5/5] Michael J Gruber ... redacted
> notmuch count --exclude=false thread:00021229
> 5
> ```
> It could be some
on few / many messages.
+ *
+ * This file is part of notmuch.
+ *
+ * Copyright © 2023 David Bremner
+ *
+ * This program is free software: you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation, either version
So for this only supports counting messages in threads, and the sexp
based query parser. It seems useful to expand it to other fields
(from, e.g.). I'm not sure how motivated I am to shim this into the
infix query parser, but we will see how it goes.
---
lib/parse-sexp.cc | 35 ---
test/T081-sexpr-search.sh | 6 ++
2 files changed, 38 insertions(+), 3 deletions(-)
diff --git a/lib/parse-sexp.cc b/lib/parse-sexp.cc
index 9cadbc13..1faa9023 100644
--- a/lib/parse-sexp.cc
+++ b/lib/parse-sexp.cc
@@
Vishal Chourasia writes:
> Thanks! Installing the emacs-notmuch package from epel 8 worked.
>
Great, thanks for letting us know.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-le...@notmuchmail.org
Vishal Chourasia writes:
> On 2/7/23 19:53, David Bremner wrote:
>> Which distribution? At least on Debian based distributions, the emacs
>> interface is packaged seperately as elpa-notmuch
> RHEL
Fedora has a separate emacs-notmuch package. Perhaps that also exists
Vishal Chourasia writes:
> Greetings,
>
>
> where can I find the notmuch.el file when notmuch was installed from the
> distribution's package repository?
>
> # notmuch --version
> notmuch 0.35
Which distribution? At least on Debian based distributions, the emacs
interface is packaged
Daniel Kahn Gillmor writes:
> it appears that by positioning the point somewhere within the link and
> doing "M-x shr-copy-url" i can copy the target of the link to the kill
> ring.
> I think it can be added to the mode-map in emacs/notmuch-show.el. does
> anyone have a preference about what
ricardomart...@riseup.net writes:
> Ok, so I tested this. I tried stopping the systemd unit of the emacs
> server, opened an emacs instance, and started the server from within
> emacs (M-x server-start ). Connected to this server in a new frame
> ($ emacsclient -nc) and tried executing notmuch
ricardomart...@riseup.net writes:
>
> When I try to run notmuch from the emacsclient instance (M-x notmuch
> ), I get an error
> "notmuch count --batch failed
> Please check that the notmuch CLI is new enough to support `count
> --batch'. In general we recommend running matching versions of
> the
be an order of magnitude faster when deleting
large numbers of mail messages or reorganizing your mail directory
structure.
You can download muchsync from the usual place:
https://www.muchsync.org/
Enjoy,
David
___
notmuch mailing list -- notmuch
Daniel Kahn Gillmor writes:
> Just a nudge on this patch:
>
> any chance we can have it applied in the notmuch tree?
>
> --dkg
>
Applied to master.
d
___
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to
inwit writes:
> Save a list of every tag change in the new variable notmuch-tag-history.
> ---
> Storing the full history of tags can prove useful for a) repeated tag
> changes as in [0] and b) eventually logging and undoing tag changes.
>
> This is my first commit in elisp. I expect turbulences
Tomi Ollila writes:
>
> Good progress -- bash has:
>
> $ bash -c 'set' | grep UID
> EUID=1001
> UID=1001
I made that change.
> another question is whether test_subtest_broken_for_root
> is good name. perhaps it is tolerable enough
I couldn't think of anything better, but am happy to search
We pre-parse into a list of compiled regular expressions to avoid
calling regexc on the hot (indexing) path. As explained in the code
comment, this cannot be done lazily with reasonable error reporting,
at least not without touching a lot of the code in index.cc.
---
lib/database-private.h | 4
Higher level processing as a list of regular expressions and
documentation will follow.
---
lib/config.cc| 3 +++
lib/notmuch.h| 1 +
test/T030-config.sh | 1 +
test/T055-path-config.sh | 1 +
test/T590-libconfig.sh | 5 +
5 files changed, 11 insertions(+)
diff
quot;
+notmuch config set index.as_text '['
+notmuch reindex '*' >& OUTPUT
+cat< EXPECTED
+Error in index.as_text: Invalid regular expression: [
+EOF
+test_expect_equal_file EXPECTED OUTPUT
+
+test_done
diff --git a/test/corpora/indexing/fake-pdf:2,S
b/test/corpora/indexing/fake-
This obsoletes the series starting with
id:20220903232839.1473915-2-da...@tethera.net
Compared to that series this is rebased against master, it has some
more tests (including both positive and negative tests) and it
documents the non-anchoredness of the involved regex search.
File permission errors e.g., are hard to trigger as root.
---
test/T050-new.sh | 1 +
test/T150-tagging.sh | 1 +
test/test-lib.sh | 6 ++
3 files changed, 8 insertions(+)
diff --git a/test/T050-new.sh b/test/T050-new.sh
index cb67889c..240c1810 100755
--- a/test/T050-new.sh
+++
We generate output to stderr for BROKEN tests, which are not failures,
so tell the test runner not to fail because of output on stderr.
---
debian/tests/control | 13 +
test/T800-asan.sh| 8 ++--
test/defaults.sh | 2 +-
3 files changed, 20 insertions(+), 3 deletions(-)
201 - 300 of 13215 matches
Mail list logo
