On 10/12, David Bremner wrote:
> Also mislabeled -> mislabelled
That depends on which English spelling Notmuch conforms to. In American
English, "mislabeled" is correct. In British English, "mislabelled" is
correct. And I don't know about Canadian English, Australian English,
etc.
Lewis
__
On 02/12, Carl Worth wrote:
> At first glance I saw "terms ... after ... before" and thought that the
> after/before fields were for some sort of contextual context, but I
> finally figured out what those were actually for. So maybe it would help
> to add some text along the lines of "Limit to date
On 03/14, David Bremner wrote:
> Apparently some systems (MacOS?) have a system library called libutil
> and the name conflict causes problems.
Hello, David!
For reference, this issue was also discussed in the past at:
https://notmuchmail.org/pipermail/notmuch/2015/020728.html
Yes, macOS has
On 11/12, Austin Clements wrote:
> Quoth David Bremner on Nov 04 at 1:26 pm:
> > I agree it looks like a race condition. inotify sounds a bit
> > overcomplicated and perhaps non-portable? It should probably just
> > tolerate disappearing files better, consider that a warning.
>
> Inotify really *
Hello, Notmuchers!
What is the status of the Vim client? The last commit to
vim/notmuch.vim was over a year and a half ago (2015-01-23).
I'm also aware of two Vim clients on GitHub:
* https://github.com/felipec/notmuch-vim (last commit: 2014-05-22)
* https://github.com/imain/notmuch-vim (last
On 3/23/16 12:04 PM, Carl Worth wrote:
> I just installed the support for running 32-bit binaries again, so
> hopefully this will work now.
Yep, it works now. Thanks!
Lewis
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailma
Hello!
I just tried to push a minor fix to the wiki, but I get the following
error:
---8<---
$ git push
Counting objects: 3, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 310 bytes | 0 bytes/s, done.
Total 3 (delta 2), reused 0
On 12/9/15 9:39 PM, Daniel Kahn Gillmor wrote:
> +static notmuch_bool_t
> +_find_in_path(const char* path)
> +{
> +char *c = NULL, *save = NULL, *tok;
> +size_t n;
> +int dfd = -1;
> +notmuch_bool_t ret = FALSE;
> +
> +n = confstr(_CS_PATH, NULL, 0);
> +c = (char*)talloc_siz
On 12/11/15 3:56 PM, Tomi Ollila wrote:
>> +static const char*
>> +_notmuch_database_get_gpg_path (notmuch_database_t *notmuch)
>> +{
>> +#define try_gpg_path(z) if (!access(z, X_OK)) return z
>> +try_gpg_path("/usr/bin/gpg2");
>> +try_gpg_path("/bin/gpg2");
>> +try_gpg_path("/usr/bin/g
On 11/8/15 7:42 PM, Bart Bunting wrote:
> Hi,
>
> Not sure if it is appropriate to post to this list with muchsync
> questions but if not could someone let me know...
Hi, Bart.
I would say you should do what it says in the Contact section at the
bottom of the Muchsync website[1]:
Please email
On 7/17/15 7:11 AM, Suvayu Ali wrote:
> Hi,
>
> I'm trying to find those annoying emails which have useless plain
> text parts. As I recall, they had a phrase something along the lines
> of "not available in plain text" or "no plain text". So of course I
> searched for "plain text". But that ret
On 7/17/15 7:11 AM, Suvayu Ali wrote:
> Hi,
>
> I'm trying to find those annoying emails which have useless plain
> text parts. As I recall, they had a phrase something along the lines
> of "not available in plain text" or "no plain text". So of course I
> searched for "plain text". But that ret
On 6/30/15 4:29 PM, Nate Eagleson wrote:
> +# Mac OS X 10.6 has a built-in libutil.dylib that prevents ld from
> +# picking up notmuch's libutil.a. The best way to prefer our local
> +# libutil.a is to specify it via absolute path, which should work on
> +# all supported OSes.
> +LIBUTIL_PATH=${src
On 6/30/15 4:29 PM, Nate Eagleson wrote:
> +# Mac OS X 10.6 has a built-in libutil.dylib that prevents ld from
> +# picking up notmuch's libutil.a. The best way to prefer our local
> +# libutil.a is to specify it via absolute path, which should work on
> +# all supported OSes.
> +LIBUTIL_PATH=${src
On 6/3/15 1:00 AM, Tomi Ollila wrote:
> Now that I look at this, I think that having full path to
> util/libutil.a should be used (everywhere) and if there is need to use
> *system-provided* libutil, then -lutil is to be added to the command
> line...
>
> ... I think it is somewhat unfortunate (or
On 6/3/15 1:00 AM, Tomi Ollila wrote:
> Now that I look at this, I think that having full path to
> util/libutil.a should be used (everywhere) and if there is need to use
> *system-provided* libutil, then -lutil is to be added to the command
> line...
>
> ... I think it is somewhat unfortunate (or
The word "setup" is a noun, not a verb. Change occurrences of "setup"
where used as a verb to "set up".
---
The only user-visible change is to the short description of the setup
command in the "notmuch help" output. The rest of the changes are just
to source code comments or test case status me
The word "setup" is a noun, not a verb. Change occurrences of "setup"
where used as a verb to "set up".
---
The only user-visible change is to the short description of the setup
command in the "notmuch help" output. The rest of the changes are just
to source code comments or test case status me
Add NetBSD to the distribution list in the "Obtaining Notmuch" section.
Add Homebrew and pkgsrc to the list of third-party package managers for
OS X. Remove the word "Mac" from "Mac OS X" to get just "OS X" which
matches Apple's official naming.
---
index.mdwn | 3 ++-
1 file changed, 2 insertion
Add NetBSD to the distribution list in the "Obtaining Notmuch" section.
Add Homebrew and pkgsrc to the list of third-party package managers for
OS X. Remove the word "Mac" from "Mac OS X" to get just "OS X" which
matches Apple's official naming.
---
index.mdwn | 3 ++-
1 file changed, 2 insertion
On 3/6/15 1:05 AM, David Bremner wrote:
> "J. Lewis Muir" writes:
>
>> The install_name of libnotmuch.dylib on Mac OS X is what is written
>> into a program that links against it. If it is just the name of
>> the shared library file, as opposed to the full pat
On 3/6/15 1:05 AM, David Bremner wrote:
> "J. Lewis Muir" writes:
>
>> The install_name of libnotmuch.dylib on Mac OS X is what is written
>> into a program that links against it. If it is just the name of
>> the shared library file, as opposed to the full pat
The install_name of libnotmuch.dylib on Mac OS X is what is written
into a program that links against it. If it is just the name of the
shared library file, as opposed to the full path, the program won't be
able to find it when it runs and will abort. Instead, the install_name
should be the full
The install_name of libnotmuch.dylib on Mac OS X is what is written
into a program that links against it. If it is just the name of the
shared library file, as opposed to the full path, the program won't be
able to find it when it runs and will abort. Instead, the install_name
should be the full
On 2/26/15 1:04 PM, Tomi Ollila wrote:
> The commit message is just (IMO) somewhat confusing; what is this
>
> $ otool -L /opt/notmuch-current/lib/libnotmuch.dylib
>
> is there files /opt/notmuch-current/lib/libnotmuch.dylib and
> /opt/notmuch-current/lib/libnotmuch.3.dylib in the fs
Hi, Tomi.
On 2/26/15 1:04 PM, Tomi Ollila wrote:
> The commit message is just (IMO) somewhat confusing; what is this
>
> $ otool -L /opt/notmuch-current/lib/libnotmuch.dylib
>
> is there files /opt/notmuch-current/lib/libnotmuch.dylib and
> /opt/notmuch-current/lib/libnotmuch.3.dylib in the fs
Hi, Tomi.
On 2/25/15 1:34 AM, David Bremner wrote:
> Unfortunately we did not receive any feedback from Mac users in the
> meantime. It would be nice to know that your patch won't break the
> existing macports and brew packages. I suppose that those work
> because they install the libraries into a well know
On 2/25/15 1:34 AM, David Bremner wrote:
> Unfortunately we did not receive any feedback from Mac users in the
> meantime. It would be nice to know that your patch won't break the
> existing macports and brew packages. I suppose that those work
> because they install the libraries into a well know
On 9/5/14 7:47 AM, J. Lewis Muir wrote:
> On 9/4/14, 2:58 PM, David Bremner wrote:
>> "J. Lewis Muir" writes:
>>
>>> Hello.
>>>
>>> I submitted a patch [1] to fix a bug in how the notmuch shared
>>> library is built on Mac OS X, but p
On 9/4/14, 2:58 PM, David Bremner wrote:
> "J. Lewis Muir" writes:
>
>> Hello.
>>
>> I submitted a patch [1] to fix a bug in how the notmuch shared
>> library is built on Mac OS X, but perhaps it's not clear it fixes a
>> bug, so I wan
On 9/4/14, 2:58 PM, David Bremner wrote:
> "J. Lewis Muir" writes:
>
>> Hello.
>>
>> I submitted a patch [1] to fix a bug in how the notmuch shared
>> library is built on Mac OS X, but perhaps it's not clear it fixes a
>> bug, so I wan
Hello.
I submitted a patch [1] to fix a bug in how the notmuch shared library
is built on Mac OS X, but perhaps it's not clear it fixes a bug, so I
wanted to just request it be tagged as a bug for nmbug.
Thank you!
Lewis
[1] http://notmuchmail.org/pipermail/notmuch/2014/018956.html
Hello.
I submitted a patch [1] to fix a bug in how the notmuch shared library
is built on Mac OS X, but perhaps it's not clear it fixes a bug, so I
wanted to just request it be tagged as a bug for nmbug.
Thank you!
Lewis
[1] http://notmuchmail.org/pipermail/notmuch/2014/018956.html
The install_name of libnotmuch.dylib on Mac OS X is what is written
into a program that links against it. If it is just the name of the
shared library file, as opposed to the full path, the program won't be
able to find it when it runs and will abort. Instead, the install_name
should be the full
The install_name of libnotmuch.dylib on Mac OS X is what is written
into a program that links against it. If it is just the name of the
shared library file, as opposed to the full path, the program won't be
able to find it when it runs and will abort. Instead, the install_name
should be the full
35 matches
Mail list logo