Hello list,
I use notmuch with the Emacs frontend and multiple accounts. I’d like
it to set the domain part of Message-Id header of any mail I compose to
something sensible, e.g. the FQDN of the host (which does not seem to be
easy, see [0]) or the domain part of the From header.
I was thinking
David Bremner writes:
> Thomas Schneider writes:
>
>> Hello list,
>>
>> I use notmuch with the Emacs frontend and multiple accounts. I’d like
>> it to set the domain part of Message-Id header of any mail I compose to
>> something sensible, e.g. the FQDN of
This way, one can build for a different Ruby than $PATH/ruby
(e. g. different versions, or Ruby in other paths).
Signed-off-by: Thomas Schneider
---
bindings/Makefile.local | 2 +-
configure | 11 ++-
test/test-lib.sh| 2 +-
3 files changed, 12 insertions(+), 3
Tomi Ollila writes:
> On Mon, Jun 11 2018, Daniel Kahn Gillmor wrote:
>
>> Make printmimestructure work in python3 as well as python2.
>>
>> PEP 394 suggests that python scripts that work with both python2 and
>> python3 should have a #!/usr/bin/python command line, so do that too.
>
> I did not
Hi,
I discovered an issue in notmuch new: when deleting a large amount of
messages (so that it takes long and displays “$time remaining”), it does
not clean the line afterwards:
---
$ pwd
/home/qsx/.maildir/fnord
$ tar xf /tmp/mails.tar
$ notmuch new
Processed 9001 total files in 4s (2113 files/s
>From notmuch-insert(1):
> If the new message is a duplicate of an existing message in the
> database (it has same Message-ID), it will be added to the maildir
> folder and notmuch database, but the tags will not be changed.
It might however be desired to apply the new tags even when the message
David Bremner writes:
> Just to be clear, I wasn't commenting on whether it was the right thing
> to do or not, just whether it would be hard. It seems likely to be
> annoying to at least some people to have messages show up as unread
> again (or whatever the tags are) when new copies arrive.
Oh
David Bremner writes:
> We're using more or less the default for Emacs (you can see the details
> in .dir-locals.el).
Maybe I misunderstood, but this doesn’t really look like Emacs’ defaults
for C.
> I'm a bit dubious that we want to re-whitespace everything, but I'd
> certainly be receptive to
It seems to work so far and doesn’t depend on Ruby’s MakeMakefile, as
the current Makefile does. However, there is currently no way to
configure a certain Ruby version to build against (the first one that
works is used).
Given that the Ruby bindings themselves are a bit unmaintained, it might
mak
David Bremner writes:
> 'qsx' reported a bug on #notmuch with notmuch-dump and large stored
> queries. This test will pass (on my machine) if the value of `repeat'
> is made smaller.
Feel free to add 'Reported-By: Thomas Schneider
Hi Gaute,
Gaute Hope writes:
> lieer v1.1 has been released with a bunch of minor fixes, and also the
> ability to (experimentally) send e-mail as a primitive sendmail stand-in.
>
> https://github.com/gauteh/lieer
That’s nice to hear. I see the release on GitHub, but are you going to
upload
Hi,
Notmuch mailinglist writes:
> My email is from Protonmail and I use sieve filters to organise my mail as
> needed into folders.
> Mbsync creates a folder structure which mirrors what is on my proton mail
> account.
> But is it possible for notmuch to create tags based on the folders within
not match.
Signed-off-by: Thomas Schneider
---
I discovered this when building with Clang:
qsx@naboo ~/src/notmuch (git)-[tags/0.32.2]
% gcc -o /dev/null compat/have_strcasestr.c; echo $?
compat/have_strcasestr.c: In function ‘main’:
compat/have_strcasestr.c:10:13: warning: implicit declaration of
Hi,
it would be nice if the error message notmuch shows when an uncaught
exception occurs was more helpful to the user. It could at least show
the exception message (`e->what()` iirc), which would have helped in
this case.
From IRC:
% notmuch new
libc++abi: terminating due to uncaught excepti
Tomi Ollila writes:
> On Fri, Dec 02 2022, Thomas Schneider wrote:
>
>> As per strcasestr(3) of glibc and FreeBSD, the header that defines
>> strcasestr() is string.h, not strings.h. This may cause compilation,
>> and thus detection whether an (optimised) version is av
15 matches
Mail list logo