notmuch/util, branch debian/0.21-2 thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=debian%2F0.21-2 2015-09-26T10:37:35Z util: add strcmp_null, a strcmp that handles NULL parameters 2015-09-26T10:37:35Z Jani Nikula jani@nikula.org 2015-09-25T16:48:19Z urn:sha1:bcb695a716bf28691ac21f6faa56e93fd3210486 Add strcmp_null, a strcmp that handles NULL strings; in strcmp terms a NULL string is considered to be less than a non-NULL string. util: move strcase_equal and strcase_hash to util 2015-09-07T12:43:31Z Jani Nikula jani@nikula.org 2015-09-03T19:40:01Z urn:sha1:f460ad4e9a2516b05162cc57c2d3b0e8b814b0c2 For future use in both cli and lib. hex-escape: remove unused variable default_buf_size 2014-10-05T05:30:46Z Jani Nikula jani@nikula.org 2014-10-04T17:53:09Z urn:sha1:ad5c017b691227ebba8b8f0bf82a5171904a9145 Found by clang: CC -O2 util/hex-escape.o util/hex-escape.c:28:21: warning: unused variable 'default_buf_size' [-Wunused-const-variable] static const size_t default_buf_size = 1024; ^ 1 warning generated. util: Const version of strtok_len 2014-08-06T12:56:36Z Austin Clements amdragon@MIT.EDU 2014-08-01T02:09:52Z urn:sha1:9f0f30f7dea1b8fd888d774175ed96d802118b11 Because of limitations in the C type system, we can't a strtok_len that can work on both const string and non-const strings. The C library solves this by taking a const char* and returning a char* in functions like this (e.g., strchr), but that's not const-safe. Solve it by introducing strtok_len_c, a version of strtok_len for const strings. util: Make string-util.h C++-compatible 2014-07-31T10:11:25Z Austin Clements amdragon@MIT.EDU 2014-07-29T16:48:00Z urn:sha1:a5a47dab8776cffc6ffbd77c51933831a34279f1 util: add gz_readline 2014-04-12T10:59:44Z David Bremner david@tethera.net 2014-03-29T17:53:17Z urn:sha1:85d9219a62c23c3ff58b42a63b65390526b89b6b The idea is to provide a more or less drop in replacement for readline to read from zlib/gzip streams. Take the opportunity to replace malloc with talloc. util: Fix two corner-cases in boolean term quoting function 2014-03-15T18:05:06Z Austin Clements amdragon@MIT.EDU 2014-03-11T20:42:00Z urn:sha1:3fed6736a7ef8b8b1f05d0fabb136bdd3b5917ee Previously, make_boolean_term did not quote empty boolean terms or boolean terms that started with '('. These cases are incompatible with Xapian: empty terms cannot be omitted, and boolean terms that start with '(' trigger an alternate term quoting syntax. Fix this by quoting empty terms and terms that contain '('. util: make sanitize string available in string util for reuse 2014-03-09T13:13:30Z Jani Nikula jani@nikula.org 2014-02-03T19:51:43Z urn:sha1:029790d3ff6e9fccfed2214efac777b8c438e318 No functional changes. util: detect byte order 2013-11-27T11:43:29Z David Bremner david@tethera.net 2013-11-26T02:55:24Z urn:sha1:b9f0e6923d645a044f837d61a9343ea16d56504e Unfortunately old versions of GCC and clang do not provide byte order macros, so we re-invent them. If UTIL_BYTE_ORDER is not defined or defined to 0, we fall back to macros supported by recent versions of GCC and clang string-util: Disallow empty prefixes in parse_boolean_term 2013-01-08T00:55:21Z Austin Clements amdragon@MIT.EDU 2013-01-07T21:20:40Z urn:sha1:b4b22d37144c7820b435cea500fa4cfd1088b191 Xapian doesn't consider ":abc" to be a prefixed term. This makes parse_boolean_term similarly reject queries with an empty prefix.