| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
A "make" invocation still works from the top-level, but not from
down inside the lib directory yet.
|
| |
|
|
|
|
| |
The notmuch.c main program now uses GMime directly rather than using
these functions, and I'd rather not export any functions unless we
have good evidence that the functions are necessary.
|
| |
|
|
|
| |
Use GMime function to decode message-header values according to
RFC 2047.
|
| |
|
|
|
| |
This is just the raw message body for now, (so any MIME parsing will
be up to the consumer). And this will likely change in the future.
|
| |
|
|
|
|
|
| |
We're using a delimiter syntax that Keith is optimistic about
being able to easily parse in emacs. Note: We're not escaping
any occurrence of the delimiters in the message yet, so we'll
need to fix that.
|
| |
|
|
|
| |
And use this in "notmuch search" to display subject line as well as
thread ID.
|
| |
|
|
|
|
| |
Replacing them with calls to talloc_asprintf if possible, otherwise
to asprintf (with it's painful error-handling leaving the pointer
undefined).
|
| |
|
|
| |
Wow, lots of missing 'static' on internal functions.
|
| |
|
|
|
|
|
|
| |
When adding -Wextra we also add -Wno-ununsed-parameters since that
function means well enough, but is really annoying in practice.
So the warnings we fix here are basically all comparsions between
signed and unsigned values.
|
| |
|
|
|
|
| |
We were previously just doing fprintf;exit at each point, but I
wanted to add file and line-number details to all messages, so it
makes sense to use a single macro for that.
|
| |
|
|
|
|
|
| |
It's even enough to check if a "missing" header was accidentally
left off the list in the call to restrict_headers. (And it's
cheap since we only check in case no such header was found in the
message.)
|
|
|
This is in preparation for a new, public notmuch_message_t.
Eventually, the public notmuch_message_t is going to grow enough
features to need to be file-backed and will likely need everything
that's now in message-file.c. So we may fold these back into one
object/implementation in the future.
|
Carl Worth