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>
|
|
|
|
*/
|
|
|
|
|
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 "notmuch.h"
|
|
|
|
|
2009-10-20 21:47:23 +02:00
|
|
|
#ifndef _GNU_SOURCE
|
|
|
|
#define _GNU_SOURCE /* for getline */
|
|
|
|
#endif
|
|
|
|
|
2009-10-17 17:26:58 +02:00
|
|
|
#include <stdio.h>
|
|
|
|
#include <stdlib.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/types.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-20 21:47:23 +02:00
|
|
|
#include <glib.h> /* g_strdup_printf */
|
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-20 03:30:48 +02:00
|
|
|
int total_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
|
|
|
int count;
|
|
|
|
struct timeval tv_start;
|
|
|
|
} add_files_state_t;
|
|
|
|
|
|
|
|
/* Compute the number of seconds elapsed from start to end. */
|
|
|
|
double
|
|
|
|
tv_elapsed (struct timeval start, struct timeval end)
|
|
|
|
{
|
|
|
|
return ((end.tv_sec - start.tv_sec) +
|
|
|
|
(end.tv_usec - start.tv_usec) / 1e6);
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
print_formatted_seconds (double seconds)
|
|
|
|
{
|
|
|
|
int hours;
|
|
|
|
int minutes;
|
|
|
|
|
|
|
|
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-20 03:30:48 +02:00
|
|
|
printf ("%02ds", (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
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
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-20 03:30:48 +02:00
|
|
|
rate_overall = (state->count) / elapsed_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
|
|
|
|
2009-10-20 03:30:48 +02:00
|
|
|
printf ("Added %d of %d messages (",
|
|
|
|
state->count, state->total_messages);
|
|
|
|
print_formatted_seconds ((state->total_messages - state->count) /
|
|
|
|
rate_overall);
|
2009-10-21 09:32:30 +02:00
|
|
|
printf (" remaining). \r");
|
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);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Recursively find all regular files in 'path' and add them to the
|
|
|
|
* database. */
|
|
|
|
void
|
|
|
|
add_files (notmuch_database_t *notmuch, const char *path,
|
|
|
|
add_files_state_t *state)
|
|
|
|
{
|
|
|
|
DIR *dir;
|
|
|
|
struct dirent *entry, *e;
|
|
|
|
int entry_length;
|
|
|
|
int err;
|
|
|
|
char *next;
|
|
|
|
struct stat st;
|
2009-10-20 08:08:49 +02:00
|
|
|
notmuch_status_t 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
|
|
|
|
|
|
|
dir = opendir (path);
|
|
|
|
|
|
|
|
if (dir == NULL) {
|
|
|
|
fprintf (stderr, "Warning: failed to open directory %s: %s\n",
|
|
|
|
path, strerror (errno));
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
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);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (e == NULL)
|
|
|
|
break;
|
|
|
|
|
|
|
|
/* 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;
|
|
|
|
}
|
|
|
|
|
|
|
|
next = g_strdup_printf ("%s/%s", path, entry->d_name);
|
|
|
|
|
|
|
|
stat (next, &st);
|
|
|
|
|
|
|
|
if (S_ISREG (st.st_mode)) {
|
2009-10-20 08:08:49 +02:00
|
|
|
status = notmuch_database_add_message (notmuch, next);
|
|
|
|
if (status == NOTMUCH_STATUS_FILE_NOT_EMAIL) {
|
|
|
|
fprintf (stderr, "Note: Ignoring non-mail file: %s\n",
|
|
|
|
next);
|
|
|
|
} else {
|
|
|
|
state->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
|
|
|
if (state->count % 1000 == 0)
|
|
|
|
add_files_print_progress (state);
|
|
|
|
} else if (S_ISDIR (st.st_mode)) {
|
|
|
|
add_files (notmuch, next, state);
|
|
|
|
}
|
|
|
|
|
|
|
|
free (next);
|
|
|
|
}
|
|
|
|
|
|
|
|
free (entry);
|
|
|
|
|
|
|
|
closedir (dir);
|
|
|
|
}
|
|
|
|
|
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). */
|
|
|
|
void
|
|
|
|
count_files (const char *path, int *count)
|
|
|
|
{
|
|
|
|
DIR *dir;
|
|
|
|
struct dirent *entry, *e;
|
|
|
|
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));
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
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);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
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;
|
|
|
|
}
|
|
|
|
|
|
|
|
next = g_strdup_printf ("%s/%s", path, entry->d_name);
|
|
|
|
|
|
|
|
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);
|
|
|
|
}
|
|
|
|
|
|
|
|
free (entry);
|
|
|
|
|
|
|
|
closedir (dir);
|
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
setup_command (int argc, char *argv[])
|
|
|
|
{
|
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_database_t *notmuch;
|
2009-10-20 19:07:11 +02:00
|
|
|
char *mail_directory, *default_path;
|
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-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
|
|
|
mail_directory = NULL;
|
|
|
|
getline (&mail_directory, &line_size, stdin);
|
2009-10-20 19:07:11 +02:00
|
|
|
printf ("\n");
|
2009-10-17 17:26:58 +02:00
|
|
|
|
2009-10-20 22:16:16 +02:00
|
|
|
if (mail_directory &&
|
|
|
|
mail_directory[strlen(mail_directory)-1] == '\n')
|
|
|
|
{
|
|
|
|
mail_directory[strlen(mail_directory)-1] = '\0';
|
|
|
|
}
|
|
|
|
|
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);
|
|
|
|
free (mail_directory);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
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-20 03:30:48 +02:00
|
|
|
add_files_state.total_messages = 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.count = 0;
|
|
|
|
gettimeofday (&add_files_state.tv_start, NULL);
|
|
|
|
|
|
|
|
add_files (notmuch, mail_directory, &add_files_state);
|
|
|
|
|
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);
|
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 ("Added %d total messages in ", add_files_state.count);
|
|
|
|
print_formatted_seconds (elapsed);
|
|
|
|
printf (" (%d messages/sec.). \n", (int) (add_files_state.count / elapsed));
|
|
|
|
|
|
|
|
notmuch_database_close (notmuch);
|
2009-10-17 17:26:58 +02:00
|
|
|
|
|
|
|
free (mail_directory);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
search_command (int argc, char *argv[])
|
|
|
|
{
|
|
|
|
fprintf (stderr, "Error: search is not implemented yet.\n");
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
show_command (int argc, char *argv[])
|
|
|
|
{
|
2009-10-20 08:41:31 +02:00
|
|
|
fprintf (stderr, "Error: show is not implemented yet.\n");
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
dump_command (int argc, char *argv[])
|
|
|
|
{
|
2009-10-21 06:03:30 +02:00
|
|
|
FILE *output;
|
|
|
|
notmuch_database_t *notmuch = NULL;
|
|
|
|
notmuch_query_t *query;
|
|
|
|
notmuch_results_t *results;
|
|
|
|
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",
|
|
|
|
argv[1], strerror (errno));
|
|
|
|
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);
|
|
|
|
|
|
|
|
for (results = notmuch_query_search (query);
|
|
|
|
notmuch_results_has_more (results);
|
|
|
|
notmuch_results_advance (results))
|
|
|
|
{
|
|
|
|
message = notmuch_results_get (results);
|
|
|
|
|
|
|
|
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))
|
|
|
|
{
|
|
|
|
int first = 1;
|
|
|
|
|
|
|
|
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);
|
|
|
|
if (output != stdout)
|
|
|
|
fclose (output);
|
|
|
|
|
|
|
|
return ret;
|
2009-10-20 08:41:31 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
int
|
|
|
|
restore_command (int argc, char *argv[])
|
|
|
|
{
|
|
|
|
fprintf (stderr, "Error: restore is not implemented yet.\n");
|
2009-10-17 17:26:58 +02:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
|
|
|
command_t commands[] = {
|
|
|
|
{ "setup", setup_command,
|
2009-10-20 08:41:31 +02:00
|
|
|
"Interactively setup notmuch for first use.\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-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
|
|
|
};
|
|
|
|
|
|
|
|
void
|
|
|
|
usage (void)
|
|
|
|
{
|
|
|
|
command_t *command;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
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;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
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");
|
|
|
|
} else {
|
|
|
|
fprintf (stderr, "Error: Unknown command '%s'\n\n", argv[1]);
|
|
|
|
}
|
2009-10-17 17:26:58 +02:00
|
|
|
usage ();
|
|
|
|
exit (1);
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|