2009-10-17 17:26:58 +02:00
|
|
|
/* notmuch - Not much of an email program, (just index and search)
|
|
|
|
*
|
|
|
|
* Copyright © 2009 Carl Worth
|
|
|
|
*
|
|
|
|
* 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 3 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program. If not, see http://www.gnu.org/licenses/ .
|
|
|
|
*
|
|
|
|
* Author: Carl Worth <cworth@cworth.org>
|
|
|
|
*/
|
|
|
|
|
2009-10-20 21:47:23 +02:00
|
|
|
#ifndef _GNU_SOURCE
|
|
|
|
#define _GNU_SOURCE /* for getline */
|
|
|
|
#endif
|
2009-10-23 23:31:01 +02:00
|
|
|
#include <stdio.h>
|
|
|
|
|
|
|
|
#include "notmuch.h"
|
2009-10-20 21:47:23 +02:00
|
|
|
|
2009-10-22 01:03:03 +02:00
|
|
|
/* This is separate from notmuch-private.h because we're trying to
|
|
|
|
* keep notmuch.c from looking into any internals, (which helps us
|
|
|
|
* develop notmuch.h into a plausible library interface).
|
|
|
|
*/
|
|
|
|
#include "xutil.h"
|
|
|
|
|
2009-10-20 21:47:23 +02:00
|
|
|
#include <stddef.h>
|
2009-10-17 17:26:58 +02:00
|
|
|
#include <string.h>
|
|
|
|
#include <sys/stat.h>
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
#include <sys/time.h>
|
2009-10-17 17:26:58 +02:00
|
|
|
#include <unistd.h>
|
|
|
|
#include <dirent.h>
|
|
|
|
#include <errno.h>
|
|
|
|
|
2009-10-21 06:03:30 +02:00
|
|
|
#include <talloc.h>
|
|
|
|
|
2009-10-25 23:53:27 +01:00
|
|
|
#define unused(x) x __attribute__ ((unused))
|
|
|
|
|
2009-10-25 18:22:41 +01:00
|
|
|
/* There's no point in continuing when we've detected that we've done
|
|
|
|
* something wrong internally (as opposed to the user passing in a
|
|
|
|
* bogus value).
|
|
|
|
*
|
|
|
|
* Note that __location__ comes from talloc.h.
|
|
|
|
*/
|
|
|
|
#define INTERNAL_ERROR(format, ...) \
|
|
|
|
do { \
|
|
|
|
fprintf(stderr, \
|
|
|
|
"Internal error: " format " (%s)\n", \
|
|
|
|
##__VA_ARGS__, __location__); \
|
|
|
|
exit (1); \
|
|
|
|
} while (0)
|
|
|
|
|
2009-10-17 17:26:58 +02:00
|
|
|
#define ARRAY_SIZE(arr) (sizeof (arr) / sizeof (arr[0]))
|
|
|
|
|
|
|
|
typedef int (*command_function_t) (int argc, char *argv[]);
|
|
|
|
|
|
|
|
typedef struct command {
|
|
|
|
const char *name;
|
|
|
|
command_function_t function;
|
|
|
|
const char *usage;
|
|
|
|
} command_t;
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
typedef struct {
|
2009-10-24 02:20:43 +02:00
|
|
|
int ignore_read_only_directories;
|
2009-10-25 17:14:16 +01:00
|
|
|
int saw_read_only_directory;
|
2009-10-24 02:20:43 +02:00
|
|
|
|
2009-10-24 00:22:14 +02:00
|
|
|
int total_files;
|
|
|
|
int processed_files;
|
|
|
|
int added_messages;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
struct timeval tv_start;
|
|
|
|
} add_files_state_t;
|
|
|
|
|
2009-10-22 00:59:11 +02:00
|
|
|
static void
|
|
|
|
chomp_newline (char *str)
|
|
|
|
{
|
|
|
|
if (str && str[strlen(str)-1] == '\n')
|
|
|
|
str[strlen(str)-1] = '\0';
|
|
|
|
}
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
/* Compute the number of seconds elapsed from start to end. */
|
2009-10-25 23:58:05 +01:00
|
|
|
static double
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
tv_elapsed (struct timeval start, struct timeval end)
|
|
|
|
{
|
|
|
|
return ((end.tv_sec - start.tv_sec) +
|
|
|
|
(end.tv_usec - start.tv_usec) / 1e6);
|
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static void
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
print_formatted_seconds (double seconds)
|
|
|
|
{
|
|
|
|
int hours;
|
|
|
|
int minutes;
|
|
|
|
|
2009-10-24 00:50:48 +02:00
|
|
|
if (seconds < 1) {
|
|
|
|
printf ("almost no time");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
if (seconds > 3600) {
|
|
|
|
hours = (int) seconds / 3600;
|
2009-10-20 03:30:48 +02:00
|
|
|
printf ("%dh ", hours);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
seconds -= hours * 3600;
|
|
|
|
}
|
|
|
|
|
2009-10-20 03:30:48 +02:00
|
|
|
if (seconds > 60) {
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
minutes = (int) seconds / 60;
|
2009-10-20 03:30:48 +02:00
|
|
|
printf ("%dm ", minutes);
|
|
|
|
seconds -= minutes * 60;
|
|
|
|
}
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-24 00:22:14 +02:00
|
|
|
printf ("%ds", (int) seconds);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static void
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
add_files_print_progress (add_files_state_t *state)
|
|
|
|
{
|
|
|
|
struct timeval tv_now;
|
2009-10-20 03:30:48 +02:00
|
|
|
double elapsed_overall, rate_overall;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
|
|
|
gettimeofday (&tv_now, NULL);
|
|
|
|
|
|
|
|
elapsed_overall = tv_elapsed (state->tv_start, tv_now);
|
2009-10-24 00:22:14 +02:00
|
|
|
rate_overall = (state->processed_files) / elapsed_overall;
|
|
|
|
|
|
|
|
printf ("Processed %d", state->processed_files);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-24 00:22:14 +02:00
|
|
|
if (state->total_files) {
|
|
|
|
printf (" of %d files (", state->total_files);
|
|
|
|
print_formatted_seconds ((state->total_files - state->processed_files) /
|
|
|
|
rate_overall);
|
|
|
|
printf (" remaining). \r");
|
|
|
|
} else {
|
|
|
|
printf (" files (%d files/sec.) \r", (int) rate_overall);
|
|
|
|
}
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
|
|
|
fflush (stdout);
|
|
|
|
}
|
|
|
|
|
2009-10-24 00:48:05 +02:00
|
|
|
/* Examine 'path' recursively as follows:
|
|
|
|
*
|
|
|
|
* o Ask the filesystem for the mtime of 'path' (path_mtime)
|
|
|
|
*
|
|
|
|
* o Ask the database for its timestamp of 'path' (path_dbtime)
|
|
|
|
*
|
|
|
|
* o If 'path_mtime' > 'path_dbtime'
|
|
|
|
*
|
|
|
|
* o For each regular file in 'path' with mtime newer than the
|
|
|
|
* 'path_dbtime' call add_message to add the file to the
|
|
|
|
* database.
|
|
|
|
*
|
|
|
|
* o For each sub-directory of path, recursively call into this
|
|
|
|
* same function.
|
|
|
|
*
|
|
|
|
* o Tell the database to update its time of 'path' to 'path_mtime'
|
2009-10-24 01:19:35 +02:00
|
|
|
*
|
|
|
|
* The 'struct stat *st' must point to a structure that has already
|
|
|
|
* been initialized for 'path' by calling stat().
|
2009-10-24 00:48:05 +02:00
|
|
|
*/
|
2009-10-25 23:58:05 +01:00
|
|
|
static notmuch_status_t
|
2009-10-24 01:19:35 +02:00
|
|
|
add_files_recursive (notmuch_database_t *notmuch,
|
|
|
|
const char *path,
|
|
|
|
struct stat *st,
|
|
|
|
add_files_state_t *state)
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
{
|
2009-10-24 00:39:11 +02:00
|
|
|
DIR *dir = NULL;
|
|
|
|
struct dirent *e, *entry = NULL;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
int entry_length;
|
|
|
|
int err;
|
2009-10-24 00:39:11 +02:00
|
|
|
char *next = NULL;
|
2009-10-24 00:48:05 +02:00
|
|
|
time_t path_mtime, path_dbtime;
|
2009-10-24 00:39:11 +02:00
|
|
|
notmuch_status_t status, ret = NOTMUCH_STATUS_SUCCESS;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-24 02:20:43 +02:00
|
|
|
/* If we're told to, we bail out on encountering a read-only
|
|
|
|
* directory, (with this being a clear clue from the user to
|
|
|
|
* Notmuch that new mail won't be arriving there and we need not
|
|
|
|
* look. */
|
|
|
|
if (state->ignore_read_only_directories &&
|
|
|
|
(st->st_mode & S_IWUSR) == 0)
|
|
|
|
{
|
2009-10-25 17:14:16 +01:00
|
|
|
state->saw_read_only_directory = TRUE;
|
2009-10-24 02:20:43 +02:00
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
|
2009-10-24 01:19:35 +02:00
|
|
|
path_mtime = st->st_mtime;
|
2009-10-24 00:48:05 +02:00
|
|
|
|
|
|
|
path_dbtime = notmuch_database_get_timestamp (notmuch, path);
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
dir = opendir (path);
|
|
|
|
if (dir == NULL) {
|
2009-10-24 00:48:05 +02:00
|
|
|
fprintf (stderr, "Error opening directory %s: %s\n",
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
path, strerror (errno));
|
2009-10-24 00:39:11 +02:00
|
|
|
ret = NOTMUCH_STATUS_FILE_ERROR;
|
|
|
|
goto DONE;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
entry_length = offsetof (struct dirent, d_name) +
|
|
|
|
pathconf (path, _PC_NAME_MAX) + 1;
|
|
|
|
entry = malloc (entry_length);
|
|
|
|
|
|
|
|
while (1) {
|
|
|
|
err = readdir_r (dir, entry, &e);
|
|
|
|
if (err) {
|
|
|
|
fprintf (stderr, "Error reading directory: %s\n",
|
|
|
|
strerror (errno));
|
2009-10-24 00:39:11 +02:00
|
|
|
ret = NOTMUCH_STATUS_FILE_ERROR;
|
|
|
|
goto DONE;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
if (e == NULL)
|
|
|
|
break;
|
|
|
|
|
2009-10-24 00:48:05 +02:00
|
|
|
/* If this directory hasn't been modified since the last
|
|
|
|
* add_files, then we only need to look further for
|
|
|
|
* sub-directories. */
|
|
|
|
if (path_mtime <= path_dbtime && entry->d_type != DT_DIR)
|
|
|
|
continue;
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
/* Ignore special directories to avoid infinite recursion.
|
|
|
|
* Also ignore the .notmuch directory.
|
|
|
|
*/
|
|
|
|
/* XXX: Eventually we'll want more sophistication to let the
|
|
|
|
* user specify files to be ignored. */
|
|
|
|
if (strcmp (entry->d_name, ".") == 0 ||
|
|
|
|
strcmp (entry->d_name, "..") == 0 ||
|
|
|
|
strcmp (entry->d_name, ".notmuch") ==0)
|
|
|
|
{
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2009-10-26 23:17:10 +01:00
|
|
|
next = talloc_asprintf (notmuch, "%s/%s", path, entry->d_name);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-24 01:19:35 +02:00
|
|
|
if (stat (next, st)) {
|
2009-10-24 00:39:11 +02:00
|
|
|
fprintf (stderr, "Error reading %s: %s\n",
|
|
|
|
next, strerror (errno));
|
|
|
|
ret = NOTMUCH_STATUS_FILE_ERROR;
|
|
|
|
continue;
|
|
|
|
}
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-24 01:19:35 +02:00
|
|
|
if (S_ISREG (st->st_mode)) {
|
2009-10-24 00:48:05 +02:00
|
|
|
/* If the file hasn't been modified since the last
|
|
|
|
* add_files, then we need not look at it. */
|
2009-10-24 01:19:35 +02:00
|
|
|
if (st->st_mtime > path_dbtime) {
|
2009-10-24 00:48:05 +02:00
|
|
|
state->processed_files++;
|
|
|
|
|
|
|
|
status = notmuch_database_add_message (notmuch, next);
|
|
|
|
switch (status) {
|
|
|
|
/* success */
|
|
|
|
case NOTMUCH_STATUS_SUCCESS:
|
|
|
|
state->added_messages++;
|
|
|
|
break;
|
|
|
|
/* Non-fatal issues (go on to next file) */
|
|
|
|
case NOTMUCH_STATUS_DUPLICATE_MESSAGE_ID:
|
|
|
|
/* Stay silent on this one. */
|
|
|
|
break;
|
|
|
|
case NOTMUCH_STATUS_FILE_NOT_EMAIL:
|
|
|
|
fprintf (stderr, "Note: Ignoring non-mail file: %s\n",
|
|
|
|
next);
|
|
|
|
break;
|
|
|
|
/* Fatal issues. Don't process anymore. */
|
|
|
|
case NOTMUCH_STATUS_XAPIAN_EXCEPTION:
|
2009-10-26 00:03:45 +01:00
|
|
|
case NOTMUCH_STATUS_OUT_OF_MEMORY:
|
|
|
|
fprintf (stderr, "Error: %s. Halting processing.\n",
|
|
|
|
notmuch_status_to_string (status));
|
2009-10-24 00:48:05 +02:00
|
|
|
ret = status;
|
|
|
|
goto DONE;
|
|
|
|
default:
|
2009-10-26 00:03:45 +01:00
|
|
|
case NOTMUCH_STATUS_FILE_ERROR:
|
|
|
|
case NOTMUCH_STATUS_NULL_POINTER:
|
|
|
|
case NOTMUCH_STATUS_TAG_TOO_LONG:
|
|
|
|
case NOTMUCH_STATUS_LAST_STATUS:
|
2009-10-25 18:22:41 +01:00
|
|
|
INTERNAL_ERROR ("add_message returned unexpected value: %d", status);
|
2009-10-24 00:48:05 +02:00
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
if (state->processed_files % 1000 == 0)
|
|
|
|
add_files_print_progress (state);
|
2009-10-20 08:08:49 +02:00
|
|
|
}
|
2009-10-24 01:19:35 +02:00
|
|
|
} else if (S_ISDIR (st->st_mode)) {
|
|
|
|
status = add_files_recursive (notmuch, next, st, state);
|
2009-10-24 00:39:11 +02:00
|
|
|
if (status && ret == NOTMUCH_STATUS_SUCCESS)
|
|
|
|
ret = status;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
}
|
|
|
|
|
2009-10-26 23:17:10 +01:00
|
|
|
talloc_free (next);
|
2009-10-24 00:39:11 +02:00
|
|
|
next = NULL;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
}
|
|
|
|
|
2009-10-25 06:11:38 +01:00
|
|
|
status = notmuch_database_set_timestamp (notmuch, path, path_mtime);
|
|
|
|
if (status && ret == NOTMUCH_STATUS_SUCCESS)
|
|
|
|
ret = status;
|
2009-10-24 00:48:05 +02:00
|
|
|
|
2009-10-24 00:39:11 +02:00
|
|
|
DONE:
|
|
|
|
if (next)
|
2009-10-26 23:17:10 +01:00
|
|
|
talloc_free (next);
|
2009-10-24 00:39:11 +02:00
|
|
|
if (entry)
|
|
|
|
free (entry);
|
|
|
|
if (dir)
|
|
|
|
closedir (dir);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-24 00:39:11 +02:00
|
|
|
return ret;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
}
|
|
|
|
|
2009-10-24 01:19:35 +02:00
|
|
|
/* This is the top-level entry point for add_files. It does a couple
|
|
|
|
* of error checks, and then calls into the recursive function,
|
|
|
|
* (avoiding the repeating of these error checks at every
|
|
|
|
* level---which would be useless becaues we already do a stat() at
|
|
|
|
* the level above). */
|
|
|
|
static notmuch_status_t
|
|
|
|
add_files (notmuch_database_t *notmuch,
|
|
|
|
const char *path,
|
|
|
|
add_files_state_t *state)
|
|
|
|
{
|
|
|
|
struct stat st;
|
|
|
|
|
|
|
|
if (stat (path, &st)) {
|
|
|
|
fprintf (stderr, "Error reading directory %s: %s\n",
|
|
|
|
path, strerror (errno));
|
|
|
|
return NOTMUCH_STATUS_FILE_ERROR;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (! S_ISDIR (st.st_mode)) {
|
|
|
|
fprintf (stderr, "Error: %s is not a directory.\n", path);
|
|
|
|
return NOTMUCH_STATUS_FILE_ERROR;
|
|
|
|
}
|
|
|
|
|
|
|
|
return add_files_recursive (notmuch, path, &st, state);
|
|
|
|
}
|
|
|
|
|
2009-10-17 17:26:58 +02:00
|
|
|
/* Recursively count all regular files in path and all sub-direcotries
|
|
|
|
* of path. The result is added to *count (which should be
|
|
|
|
* initialized to zero by the top-level caller before calling
|
|
|
|
* count_files). */
|
2009-10-25 23:58:05 +01:00
|
|
|
static void
|
2009-10-17 17:26:58 +02:00
|
|
|
count_files (const char *path, int *count)
|
|
|
|
{
|
|
|
|
DIR *dir;
|
2009-10-26 23:17:10 +01:00
|
|
|
struct dirent *e, *entry = NULL;
|
2009-10-17 17:26:58 +02:00
|
|
|
int entry_length;
|
|
|
|
int err;
|
|
|
|
char *next;
|
|
|
|
struct stat st;
|
|
|
|
|
|
|
|
dir = opendir (path);
|
|
|
|
|
|
|
|
if (dir == NULL) {
|
|
|
|
fprintf (stderr, "Warning: failed to open directory %s: %s\n",
|
|
|
|
path, strerror (errno));
|
2009-10-26 23:17:10 +01:00
|
|
|
goto DONE;
|
2009-10-17 17:26:58 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
entry_length = offsetof (struct dirent, d_name) +
|
|
|
|
pathconf (path, _PC_NAME_MAX) + 1;
|
|
|
|
entry = malloc (entry_length);
|
|
|
|
|
|
|
|
while (1) {
|
|
|
|
err = readdir_r (dir, entry, &e);
|
|
|
|
if (err) {
|
|
|
|
fprintf (stderr, "Error reading directory: %s\n",
|
|
|
|
strerror (errno));
|
|
|
|
free (entry);
|
2009-10-26 23:17:10 +01:00
|
|
|
goto DONE;
|
2009-10-17 17:26:58 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
if (e == NULL)
|
|
|
|
break;
|
|
|
|
|
2009-10-19 21:52:46 +02:00
|
|
|
/* Ignore special directories to avoid infinite recursion.
|
|
|
|
* Also ignore the .notmuch directory.
|
|
|
|
*/
|
|
|
|
/* XXX: Eventually we'll want more sophistication to let the
|
|
|
|
* user specify files to be ignored. */
|
2009-10-17 17:26:58 +02:00
|
|
|
if (strcmp (entry->d_name, ".") == 0 ||
|
2009-10-19 21:52:46 +02:00
|
|
|
strcmp (entry->d_name, "..") == 0 ||
|
|
|
|
strcmp (entry->d_name, ".notmuch") == 0)
|
2009-10-17 17:26:58 +02:00
|
|
|
{
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2009-10-26 23:17:10 +01:00
|
|
|
if (asprintf (&next, "%s/%s", path, entry->d_name) == -1) {
|
|
|
|
next = NULL;
|
|
|
|
fprintf (stderr, "Error descending from %s to %s: Out of memory\n",
|
|
|
|
path, entry->d_name);
|
|
|
|
continue;
|
|
|
|
}
|
2009-10-17 17:26:58 +02:00
|
|
|
|
|
|
|
stat (next, &st);
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
if (S_ISREG (st.st_mode)) {
|
2009-10-17 17:26:58 +02:00
|
|
|
*count = *count + 1;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
if (*count % 1000 == 0) {
|
|
|
|
printf ("Found %d files so far.\r", *count);
|
|
|
|
fflush (stdout);
|
|
|
|
}
|
|
|
|
} else if (S_ISDIR (st.st_mode)) {
|
2009-10-17 17:26:58 +02:00
|
|
|
count_files (next, count);
|
|
|
|
}
|
|
|
|
|
|
|
|
free (next);
|
|
|
|
}
|
|
|
|
|
2009-10-26 23:17:10 +01:00
|
|
|
DONE:
|
|
|
|
if (entry)
|
|
|
|
free (entry);
|
2009-10-17 17:26:58 +02:00
|
|
|
|
|
|
|
closedir (dir);
|
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static int
|
2009-10-25 23:53:27 +01:00
|
|
|
setup_command (unused (int argc), unused (char *argv[]))
|
2009-10-17 17:26:58 +02:00
|
|
|
{
|
2009-10-23 23:55:02 +02:00
|
|
|
notmuch_database_t *notmuch = NULL;
|
|
|
|
char *default_path, *mail_directory = NULL;
|
2009-10-20 21:47:23 +02:00
|
|
|
size_t line_size;
|
2009-10-17 17:26:58 +02:00
|
|
|
int count;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
add_files_state_t add_files_state;
|
|
|
|
double elapsed;
|
2009-10-20 03:30:48 +02:00
|
|
|
struct timeval tv_now;
|
2009-10-23 23:55:02 +02:00
|
|
|
notmuch_status_t ret = NOTMUCH_STATUS_SUCCESS;
|
2009-10-17 17:26:58 +02:00
|
|
|
|
|
|
|
printf ("Welcome to notmuch!\n\n");
|
|
|
|
|
|
|
|
printf ("The goal of notmuch is to help you manage and search your collection of\n"
|
|
|
|
"email, and to efficiently keep up with the flow of email as it comes in.\n\n");
|
|
|
|
|
|
|
|
printf ("Notmuch needs to know the top-level directory of your email archive,\n"
|
|
|
|
"(where you already have mail stored and where messages will be delivered\n"
|
|
|
|
"in the future). This directory can contain any number of sub-directories\n"
|
2009-10-20 08:08:49 +02:00
|
|
|
"and primarily just files with indvidual email messages (eg. maildir or mh\n"
|
|
|
|
"archives are perfect). If there are other, non-email files (such as\n"
|
|
|
|
"indexes maintained by other email programs) then notmuch will do its\n"
|
|
|
|
"best to detect those and ignore them.\n\n");
|
2009-10-17 17:26:58 +02:00
|
|
|
|
|
|
|
printf ("Mail storage that uses mbox format, (where one mbox file contains many\n"
|
|
|
|
"messages), will not work with notmuch. If that's how your mail is currently\n"
|
|
|
|
"stored, we recommend you first convert it to maildir format with a utility\n"
|
|
|
|
"such as mb2md. In that case, press Control-C now and run notmuch again\n"
|
|
|
|
"once the conversion is complete.\n\n");
|
|
|
|
|
2009-10-20 19:07:11 +02:00
|
|
|
|
|
|
|
default_path = notmuch_database_default_path ();
|
|
|
|
printf ("Top-level mail directory [%s]: ", default_path);
|
|
|
|
fflush (stdout);
|
2009-10-17 17:26:58 +02:00
|
|
|
|
2009-10-20 21:47:23 +02:00
|
|
|
getline (&mail_directory, &line_size, stdin);
|
2009-10-22 00:59:11 +02:00
|
|
|
chomp_newline (mail_directory);
|
2009-10-17 17:26:58 +02:00
|
|
|
|
2009-10-22 00:59:11 +02:00
|
|
|
printf ("\n");
|
2009-10-20 22:16:16 +02:00
|
|
|
|
2009-10-17 17:26:58 +02:00
|
|
|
if (mail_directory == NULL || strlen (mail_directory) == 0) {
|
|
|
|
if (mail_directory)
|
|
|
|
free (mail_directory);
|
2009-10-20 19:07:11 +02:00
|
|
|
mail_directory = default_path;
|
|
|
|
} else {
|
|
|
|
/* XXX: Instead of telling the user to use an environment
|
|
|
|
* variable here, we should really be writing out a configuration
|
|
|
|
* file and loading that on the next run. */
|
|
|
|
if (strcmp (mail_directory, default_path)) {
|
|
|
|
printf ("Note: Since you are not using the default path, you will want to set\n"
|
|
|
|
"the NOTMUCH_BASE environment variable to %s so that\n"
|
|
|
|
"future calls to notmuch commands will know where to find your mail.\n",
|
|
|
|
mail_directory);
|
|
|
|
printf ("For example, if you are using bash for your shell, add:\n\n");
|
|
|
|
printf ("\texport NOTMUCH_BASE=%s\n\n", mail_directory);
|
|
|
|
printf ("to your ~/.bashrc file.\n\n");
|
|
|
|
}
|
|
|
|
free (default_path);
|
2009-10-17 17:26:58 +02:00
|
|
|
}
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
notmuch = notmuch_database_create (mail_directory);
|
|
|
|
if (notmuch == NULL) {
|
|
|
|
fprintf (stderr, "Failed to create new notmuch database at %s\n",
|
|
|
|
mail_directory);
|
2009-10-23 23:55:02 +02:00
|
|
|
ret = NOTMUCH_STATUS_FILE_ERROR;
|
|
|
|
goto DONE;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
}
|
|
|
|
|
2009-10-17 17:26:58 +02:00
|
|
|
printf ("OK. Let's take a look at the mail we can find in the directory\n");
|
|
|
|
printf ("%s ...\n", mail_directory);
|
|
|
|
|
|
|
|
count = 0;
|
|
|
|
count_files (mail_directory, &count);
|
|
|
|
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
printf ("Found %d total files. That's not much mail.\n\n", count);
|
|
|
|
|
|
|
|
printf ("Next, we'll inspect the messages and create a database of threads:\n");
|
|
|
|
|
2009-10-24 02:20:43 +02:00
|
|
|
add_files_state.ignore_read_only_directories = FALSE;
|
2009-10-25 17:14:16 +01:00
|
|
|
add_files_state.saw_read_only_directory = FALSE;
|
2009-10-24 00:22:14 +02:00
|
|
|
add_files_state.total_files = count;
|
|
|
|
add_files_state.processed_files = 0;
|
|
|
|
add_files_state.added_messages = 0;
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
gettimeofday (&add_files_state.tv_start, NULL);
|
|
|
|
|
2009-10-24 00:39:11 +02:00
|
|
|
ret = add_files (notmuch, mail_directory, &add_files_state);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-20 03:30:48 +02:00
|
|
|
gettimeofday (&tv_now, NULL);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
elapsed = tv_elapsed (add_files_state.tv_start,
|
2009-10-20 03:30:48 +02:00
|
|
|
tv_now);
|
2009-10-24 01:00:24 +02:00
|
|
|
printf ("Processed %d %s in ", add_files_state.processed_files,
|
|
|
|
add_files_state.processed_files == 1 ?
|
|
|
|
"file" : "total files");
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
print_formatted_seconds (elapsed);
|
2009-10-24 00:50:48 +02:00
|
|
|
if (elapsed > 1) {
|
|
|
|
printf (" (%d files/sec.). \n",
|
|
|
|
(int) (add_files_state.processed_files / elapsed));
|
|
|
|
} else {
|
|
|
|
printf (". \n");
|
|
|
|
}
|
2009-10-24 00:57:39 +02:00
|
|
|
if (add_files_state.added_messages) {
|
|
|
|
printf ("Added %d %s to the database.\n\n",
|
|
|
|
add_files_state.added_messages,
|
|
|
|
add_files_state.added_messages == 1 ?
|
|
|
|
"message" : "unique messages");
|
|
|
|
}
|
2009-10-24 00:22:14 +02:00
|
|
|
|
|
|
|
printf ("When new mail is delivered to %s in the future,\n"
|
2009-10-24 02:20:43 +02:00
|
|
|
"run \"notmuch new\" to add it to the database.\n\n",
|
2009-10-24 00:22:14 +02:00
|
|
|
mail_directory);
|
notmuch: Start actually adding messages to the index.
This is the beginning of the notmuch library as well, with its
interface in notmuch.h. So far we've got create, open, close, and
add_message (all with a notmuch_database prefix).
The current add_message function has already been whittled down from
what we have in notmuch-index-message to add only references,
message-id, and thread-id to the index, (that is---just enough to do
thread-linkage but nothing for full-text searching).
The concept here is to do something quickly so that the user can get
some data into notmuch and start using it. (The most interesting stuff
is then thread-linkage and labels like inbox and unread.) We can
defer the full-text indexing of the body of the messages for later,
(such as in the background while the user is reading mail).
The initial thread-stitching step is still slower than I would like.
We may have to stop using libgmime for this step as its overhead is
not worth it for the simple case of just parsing the message-id,
references, and in-reply-to headers.
2009-10-19 05:56:30 +02:00
|
|
|
|
2009-10-24 00:39:11 +02:00
|
|
|
if (ret) {
|
|
|
|
printf ("Note: At least one error was encountered: %s\n",
|
|
|
|
notmuch_status_to_string (ret));
|
|
|
|
}
|
|
|
|
|
2009-10-23 23:55:02 +02:00
|
|
|
DONE:
|
|
|
|
if (mail_directory)
|
|
|
|
free (mail_directory);
|
|
|
|
if (notmuch)
|
|
|
|
notmuch_database_close (notmuch);
|
2009-10-24 00:39:11 +02:00
|
|
|
|
2009-10-23 23:55:02 +02:00
|
|
|
return ret;
|
2009-10-17 17:26:58 +02:00
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static int
|
2009-10-25 23:53:27 +01:00
|
|
|
new_command (unused (int argc), unused (char *argv[]))
|
2009-10-24 00:48:05 +02:00
|
|
|
{
|
|
|
|
notmuch_database_t *notmuch;
|
|
|
|
const char *mail_directory;
|
|
|
|
add_files_state_t add_files_state;
|
|
|
|
double elapsed;
|
|
|
|
struct timeval tv_now;
|
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
notmuch = notmuch_database_open (NULL);
|
|
|
|
if (notmuch == NULL) {
|
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
|
|
|
|
mail_directory = notmuch_database_get_path (notmuch);
|
|
|
|
|
2009-10-24 02:20:43 +02:00
|
|
|
add_files_state.ignore_read_only_directories = TRUE;
|
2009-10-25 17:14:16 +01:00
|
|
|
add_files_state.saw_read_only_directory = FALSE;
|
2009-10-24 00:48:05 +02:00
|
|
|
add_files_state.total_files = 0;
|
|
|
|
add_files_state.processed_files = 0;
|
|
|
|
add_files_state.added_messages = 0;
|
|
|
|
gettimeofday (&add_files_state.tv_start, NULL);
|
|
|
|
|
|
|
|
ret = add_files (notmuch, mail_directory, &add_files_state);
|
|
|
|
|
|
|
|
gettimeofday (&tv_now, NULL);
|
|
|
|
elapsed = tv_elapsed (add_files_state.tv_start,
|
|
|
|
tv_now);
|
|
|
|
if (add_files_state.processed_files) {
|
2009-10-24 01:00:24 +02:00
|
|
|
printf ("Processed %d %s in ", add_files_state.processed_files,
|
|
|
|
add_files_state.processed_files == 1 ?
|
|
|
|
"file" : "total files");
|
2009-10-24 00:48:05 +02:00
|
|
|
print_formatted_seconds (elapsed);
|
2009-10-24 00:50:48 +02:00
|
|
|
if (elapsed > 1) {
|
|
|
|
printf (" (%d files/sec.). \n",
|
|
|
|
(int) (add_files_state.processed_files / elapsed));
|
|
|
|
} else {
|
|
|
|
printf (". \n");
|
|
|
|
}
|
2009-10-24 00:48:05 +02:00
|
|
|
}
|
|
|
|
if (add_files_state.added_messages) {
|
2009-10-24 00:57:39 +02:00
|
|
|
printf ("Added %d new %s to the database (not much, really).\n",
|
|
|
|
add_files_state.added_messages,
|
|
|
|
add_files_state.added_messages == 1 ?
|
|
|
|
"message" : "messages");
|
2009-10-24 00:48:05 +02:00
|
|
|
} else {
|
2009-10-24 02:25:23 +02:00
|
|
|
printf ("No new mail---and that's not much.\n");
|
2009-10-24 00:48:05 +02:00
|
|
|
}
|
|
|
|
|
2009-10-25 17:14:16 +01:00
|
|
|
if (elapsed > 1 && ! add_files_state.saw_read_only_directory) {
|
|
|
|
printf ("\nTip: If you have any sub-directories that are archives (that is,\n"
|
|
|
|
"they will never receive new mail), marking these directores as\n"
|
|
|
|
"read-only (chmod u-w /path/to/dir) will make \"notmuch new\"\n"
|
|
|
|
"much more efficient (it won't even look in those directories).\n");
|
|
|
|
}
|
|
|
|
|
2009-10-24 00:48:05 +02:00
|
|
|
if (ret) {
|
2009-10-25 17:14:16 +01:00
|
|
|
printf ("\nNote: At least one error was encountered: %s\n",
|
2009-10-24 00:48:05 +02:00
|
|
|
notmuch_status_to_string (ret));
|
|
|
|
}
|
|
|
|
|
|
|
|
DONE:
|
|
|
|
if (notmuch)
|
|
|
|
notmuch_database_close (notmuch);
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static int
|
2009-10-17 17:26:58 +02:00
|
|
|
search_command (int argc, char *argv[])
|
|
|
|
{
|
2009-10-25 06:16:10 +01:00
|
|
|
void *local = talloc_new (NULL);
|
|
|
|
notmuch_database_t *notmuch = NULL;
|
|
|
|
notmuch_query_t *query;
|
2009-10-26 07:12:20 +01:00
|
|
|
notmuch_thread_results_t *results;
|
|
|
|
notmuch_thread_t *thread;
|
2009-10-26 22:46:14 +01:00
|
|
|
notmuch_tags_t *tags;
|
2009-10-25 06:16:10 +01:00
|
|
|
char *query_str;
|
|
|
|
int i;
|
|
|
|
notmuch_status_t ret = NOTMUCH_STATUS_SUCCESS;
|
|
|
|
|
|
|
|
notmuch = notmuch_database_open (NULL);
|
|
|
|
if (notmuch == NULL) {
|
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* XXX: Should add xtalloc wrappers here and use them. */
|
|
|
|
query_str = talloc_strdup (local, "");
|
|
|
|
|
|
|
|
for (i = 0; i < argc; i++) {
|
|
|
|
if (i != 0)
|
|
|
|
query_str = talloc_asprintf_append (query_str, " ");
|
|
|
|
|
|
|
|
query_str = talloc_asprintf_append (query_str, "%s", argv[i]);
|
|
|
|
}
|
|
|
|
|
|
|
|
query = notmuch_query_create (notmuch, query_str);
|
|
|
|
if (query == NULL) {
|
|
|
|
fprintf (stderr, "Out of memory\n");
|
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
|
2009-10-26 07:12:20 +01:00
|
|
|
for (results = notmuch_query_search_threads (query);
|
|
|
|
notmuch_thread_results_has_more (results);
|
|
|
|
notmuch_thread_results_advance (results))
|
2009-10-25 06:16:10 +01:00
|
|
|
{
|
2009-10-26 22:46:14 +01:00
|
|
|
int first = 1;
|
|
|
|
|
2009-10-26 07:12:20 +01:00
|
|
|
thread = notmuch_thread_results_get (results);
|
2009-10-25 06:16:10 +01:00
|
|
|
|
2009-10-26 22:46:14 +01:00
|
|
|
printf ("%s (", notmuch_thread_get_thread_id (thread));
|
|
|
|
|
|
|
|
for (tags = notmuch_thread_get_tags (thread);
|
|
|
|
notmuch_tags_has_more (tags);
|
|
|
|
notmuch_tags_advance (tags))
|
|
|
|
{
|
|
|
|
if (! first)
|
|
|
|
printf (" ");
|
|
|
|
printf ("%s", notmuch_tags_get (tags));
|
|
|
|
first = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
printf (")\n");
|
2009-10-25 06:16:10 +01:00
|
|
|
|
2009-10-26 07:12:20 +01:00
|
|
|
notmuch_thread_destroy (thread);
|
2009-10-25 06:16:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
notmuch_query_destroy (query);
|
|
|
|
|
|
|
|
DONE:
|
|
|
|
if (notmuch)
|
|
|
|
notmuch_database_close (notmuch);
|
|
|
|
talloc_free (local);
|
|
|
|
|
|
|
|
return ret;
|
2009-10-17 17:26:58 +02:00
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static int
|
2009-10-25 23:53:27 +01:00
|
|
|
show_command (unused (int argc), unused (char *argv[]))
|
2009-10-17 17:26:58 +02:00
|
|
|
{
|
2009-10-20 08:41:31 +02:00
|
|
|
fprintf (stderr, "Error: show is not implemented yet.\n");
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static int
|
2009-10-20 08:41:31 +02:00
|
|
|
dump_command (int argc, char *argv[])
|
|
|
|
{
|
2009-10-26 17:20:32 +01:00
|
|
|
FILE *output = NULL;
|
2009-10-24 17:06:23 +02:00
|
|
|
notmuch_database_t *notmuch = NULL;
|
2009-10-21 06:03:30 +02:00
|
|
|
notmuch_query_t *query;
|
2009-10-26 06:11:09 +01:00
|
|
|
notmuch_message_results_t *results;
|
2009-10-21 06:03:30 +02:00
|
|
|
notmuch_message_t *message;
|
|
|
|
notmuch_tags_t *tags;
|
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
if (argc) {
|
|
|
|
output = fopen (argv[0], "w");
|
|
|
|
if (output == NULL) {
|
|
|
|
fprintf (stderr, "Error opening %s for writing: %s\n",
|
2009-10-21 19:12:11 +02:00
|
|
|
argv[0], strerror (errno));
|
2009-10-21 06:03:30 +02:00
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
output = stdout;
|
|
|
|
}
|
|
|
|
|
|
|
|
notmuch = notmuch_database_open (NULL);
|
|
|
|
if (notmuch == NULL) {
|
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
|
2009-10-21 07:40:37 +02:00
|
|
|
query = notmuch_query_create (notmuch, "");
|
2009-10-21 06:03:30 +02:00
|
|
|
if (query == NULL) {
|
|
|
|
fprintf (stderr, "Out of memory\n");
|
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
|
|
|
|
notmuch_query_set_sort (query, NOTMUCH_SORT_MESSAGE_ID);
|
|
|
|
|
2009-10-26 06:11:09 +01:00
|
|
|
for (results = notmuch_query_search_messages (query);
|
|
|
|
notmuch_message_results_has_more (results);
|
|
|
|
notmuch_message_results_advance (results))
|
2009-10-21 06:03:30 +02:00
|
|
|
{
|
2009-10-21 23:02:51 +02:00
|
|
|
int first = 1;
|
2009-10-26 06:11:09 +01:00
|
|
|
message = notmuch_message_results_get (results);
|
2009-10-21 06:03:30 +02:00
|
|
|
|
|
|
|
fprintf (output,
|
|
|
|
"%s (", notmuch_message_get_message_id (message));
|
|
|
|
|
|
|
|
for (tags = notmuch_message_get_tags (message);
|
|
|
|
notmuch_tags_has_more (tags);
|
|
|
|
notmuch_tags_advance (tags))
|
|
|
|
{
|
|
|
|
if (! first)
|
|
|
|
fprintf (output, " ");
|
|
|
|
|
|
|
|
fprintf (output, "%s", notmuch_tags_get (tags));
|
|
|
|
|
|
|
|
first = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
fprintf (output, ")\n");
|
2009-10-21 07:27:56 +02:00
|
|
|
|
|
|
|
notmuch_message_destroy (message);
|
2009-10-21 06:03:30 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
notmuch_query_destroy (query);
|
|
|
|
|
|
|
|
DONE:
|
|
|
|
if (notmuch)
|
|
|
|
notmuch_database_close (notmuch);
|
2009-10-26 17:20:32 +01:00
|
|
|
if (output && output != stdout)
|
2009-10-21 06:03:30 +02:00
|
|
|
fclose (output);
|
|
|
|
|
|
|
|
return ret;
|
2009-10-20 08:41:31 +02:00
|
|
|
}
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static int
|
2009-10-20 08:41:31 +02:00
|
|
|
restore_command (int argc, char *argv[])
|
|
|
|
{
|
2009-10-26 17:20:32 +01:00
|
|
|
FILE *input = NULL;
|
2009-10-24 17:06:23 +02:00
|
|
|
notmuch_database_t *notmuch = NULL;
|
2009-10-22 01:03:03 +02:00
|
|
|
char *line = NULL;
|
2009-10-25 23:39:53 +01:00
|
|
|
size_t line_size;
|
|
|
|
ssize_t line_len;
|
2009-10-22 01:03:03 +02:00
|
|
|
regex_t regex;
|
|
|
|
int rerr;
|
|
|
|
int ret = 0;
|
|
|
|
|
|
|
|
if (argc) {
|
|
|
|
input = fopen (argv[0], "r");
|
|
|
|
if (input == NULL) {
|
|
|
|
fprintf (stderr, "Error opening %s for reading: %s\n",
|
|
|
|
argv[0], strerror (errno));
|
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
printf ("No filename given. Reading dump from stdin.\n");
|
|
|
|
input = stdin;
|
|
|
|
}
|
|
|
|
|
|
|
|
notmuch = notmuch_database_open (NULL);
|
|
|
|
if (notmuch == NULL) {
|
|
|
|
ret = 1;
|
|
|
|
goto DONE;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Dump output is one line per message. We match a sequence of
|
|
|
|
* non-space characters for the message-id, then one or more
|
|
|
|
* spaces, then a list of space-separated tags as a sequence of
|
|
|
|
* characters within literal '(' and ')'. */
|
|
|
|
xregcomp (®ex,
|
|
|
|
"^([^ ]+) \\(([^)]*)\\)$",
|
|
|
|
REG_EXTENDED);
|
|
|
|
|
|
|
|
while ((line_len = getline (&line, &line_size, input)) != -1) {
|
|
|
|
regmatch_t match[3];
|
|
|
|
char *message_id, *tags, *tag, *next;
|
|
|
|
notmuch_message_t *message;
|
|
|
|
notmuch_status_t status;
|
|
|
|
|
|
|
|
chomp_newline (line);
|
|
|
|
|
|
|
|
rerr = xregexec (®ex, line, 3, match, 0);
|
|
|
|
if (rerr == REG_NOMATCH)
|
|
|
|
{
|
|
|
|
fprintf (stderr, "Warning: Ignoring invalid input line: %s\n",
|
|
|
|
line);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
|
|
|
message_id = xstrndup (line + match[1].rm_so,
|
|
|
|
match[1].rm_eo - match[1].rm_so);
|
|
|
|
tags = xstrndup (line + match[2].rm_so,
|
|
|
|
match[2].rm_eo - match[2].rm_so);
|
|
|
|
|
|
|
|
if (strlen (tags)) {
|
|
|
|
|
|
|
|
message = notmuch_database_find_message (notmuch, message_id);
|
|
|
|
if (message == NULL) {
|
2009-10-23 15:08:22 +02:00
|
|
|
fprintf (stderr, "Warning: Cannot apply tags to missing message: %s (",
|
2009-10-22 01:03:03 +02:00
|
|
|
message_id);
|
|
|
|
}
|
|
|
|
|
|
|
|
next = tags;
|
|
|
|
while (next) {
|
|
|
|
tag = strsep (&next, " ");
|
|
|
|
if (*tag == '\0')
|
|
|
|
continue;
|
2009-10-23 15:08:22 +02:00
|
|
|
if (message) {
|
|
|
|
status = notmuch_message_add_tag (message, tag);
|
|
|
|
if (status) {
|
|
|
|
fprintf (stderr,
|
|
|
|
"Error applying tag %s to message %s:\n",
|
|
|
|
tag, message_id);
|
|
|
|
fprintf (stderr, "%s\n",
|
|
|
|
notmuch_status_to_string (status));
|
|
|
|
}
|
|
|
|
} else {
|
2009-10-25 17:20:13 +01:00
|
|
|
fprintf (stderr, "%s%s",
|
|
|
|
tag == tags ? "" : " ", tag);
|
2009-10-22 01:03:03 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2009-10-23 15:08:22 +02:00
|
|
|
if (message)
|
|
|
|
notmuch_message_destroy (message);
|
|
|
|
else
|
|
|
|
fprintf (stderr, ")\n");
|
2009-10-22 01:03:03 +02:00
|
|
|
}
|
|
|
|
free (message_id);
|
|
|
|
free (tags);
|
|
|
|
}
|
|
|
|
|
|
|
|
regfree (®ex);
|
|
|
|
|
|
|
|
DONE:
|
|
|
|
if (line)
|
|
|
|
free (line);
|
|
|
|
if (notmuch)
|
|
|
|
notmuch_database_close (notmuch);
|
2009-10-26 17:20:32 +01:00
|
|
|
if (input && input != stdin)
|
|
|
|
fclose (input);
|
2009-10-22 01:03:03 +02:00
|
|
|
|
|
|
|
return ret;
|
2009-10-17 17:26:58 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
command_t commands[] = {
|
|
|
|
{ "setup", setup_command,
|
2009-10-24 02:20:43 +02:00
|
|
|
"Interactively setup notmuch for first use.\n\n"
|
2009-10-17 17:26:58 +02:00
|
|
|
"\t\tInvoking notmuch with no command argument will run setup if\n"
|
2009-10-20 08:41:31 +02:00
|
|
|
"\t\tthe setup command has not previously been completed." },
|
2009-10-24 00:48:05 +02:00
|
|
|
{ "new", new_command,
|
2009-10-24 02:20:43 +02:00
|
|
|
"Find and import any new messages.\n\n"
|
|
|
|
"\t\tScans all sub-directories of the database, adding new files\n"
|
|
|
|
"\t\tthat are found. Note: \"notmuch new\" will skip any\n"
|
|
|
|
"\t\tread-only directories, so you can use that to mark\n"
|
|
|
|
"\t\tdirectories that will not receive any new mail."},
|
2009-10-17 17:26:58 +02:00
|
|
|
{ "search", search_command,
|
2009-10-20 08:41:31 +02:00
|
|
|
"<search-term> [...]\n\n"
|
|
|
|
"\t\tSearch for threads matching the given search terms.\n"
|
|
|
|
"\t\tOnce we actually implement search we'll document the\n"
|
|
|
|
"\t\tsyntax here." },
|
2009-10-17 17:26:58 +02:00
|
|
|
{ "show", show_command,
|
2009-10-20 08:41:31 +02:00
|
|
|
"<thread-id>\n\n"
|
|
|
|
"\t\tShow the thread with the given thread ID (see 'search')." },
|
|
|
|
{ "dump", dump_command,
|
|
|
|
"[<filename>]\n\n"
|
|
|
|
"\t\tCreate a plain-text dump of the tags for each message\n"
|
|
|
|
"\t\twriting to the given filename, if any, or to stdout.\n"
|
|
|
|
"\t\tThese tags are the only data in the notmuch database\n"
|
|
|
|
"\t\tthat can't be recreated from the messages themselves.\n"
|
|
|
|
"\t\tThe output of notmuch dump is therefore the only\n"
|
|
|
|
"\t\tcritical thing to backup (and much more friendly to\n"
|
|
|
|
"\t\tincremental backup than the native database files." },
|
|
|
|
{ "restore", restore_command,
|
|
|
|
"<filename>\n\n"
|
|
|
|
"\t\tRestore the tags from the given dump file (see 'dump')." }
|
2009-10-17 17:26:58 +02:00
|
|
|
};
|
|
|
|
|
2009-10-25 23:58:05 +01:00
|
|
|
static void
|
2009-10-17 17:26:58 +02:00
|
|
|
usage (void)
|
|
|
|
{
|
|
|
|
command_t *command;
|
2009-10-25 23:39:53 +01:00
|
|
|
unsigned int i;
|
2009-10-17 17:26:58 +02:00
|
|
|
|
|
|
|
fprintf (stderr, "Usage: notmuch <command> [args...]\n");
|
|
|
|
fprintf (stderr, "\n");
|
2009-10-20 08:41:31 +02:00
|
|
|
fprintf (stderr, "Where <command> and [args...] are as follows:\n");
|
2009-10-17 17:26:58 +02:00
|
|
|
fprintf (stderr, "\n");
|
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE (commands); i++) {
|
|
|
|
command = &commands[i];
|
|
|
|
|
|
|
|
fprintf (stderr, "\t%s\t%s\n\n", command->name, command->usage);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
main (int argc, char *argv[])
|
|
|
|
{
|
|
|
|
command_t *command;
|
2009-10-25 23:39:53 +01:00
|
|
|
unsigned int i;
|
2009-10-17 17:26:58 +02:00
|
|
|
|
|
|
|
if (argc == 1)
|
|
|
|
return setup_command (0, NULL);
|
|
|
|
|
|
|
|
for (i = 0; i < ARRAY_SIZE (commands); i++) {
|
|
|
|
command = &commands[i];
|
|
|
|
|
|
|
|
if (strcmp (argv[1], command->name) == 0)
|
|
|
|
return (command->function) (argc - 2, &argv[2]);
|
|
|
|
}
|
|
|
|
|
2009-10-20 08:41:31 +02:00
|
|
|
/* Don't complain about "help" being an unknown command when we're
|
|
|
|
about to provide exactly what's wanted anyway. */
|
|
|
|
if (strcmp (argv[1], "help") == 0 ||
|
|
|
|
strcmp (argv[1], "--help") == 0)
|
|
|
|
{
|
|
|
|
fprintf (stderr, "The notmuch mail system.\n\n");
|
2009-10-26 17:13:19 +01:00
|
|
|
usage ();
|
|
|
|
return 0;
|
2009-10-20 08:41:31 +02:00
|
|
|
} else {
|
|
|
|
fprintf (stderr, "Error: Unknown command '%s'\n\n", argv[1]);
|
2009-10-26 17:13:19 +01:00
|
|
|
usage ();
|
|
|
|
return 1;
|
2009-10-20 08:41:31 +02:00
|
|
|
}
|
2009-10-17 17:26:58 +02:00
|
|
|
}
|