| Age | Commit message (Collapse) | Author |
|---|
|
We had a lot of back and forth about the name of this directory, but
nothing very conclusive. In the end, I just chose "devel" just to move
on.
|
|
I recently discussed fixing this with Austin, but want to record it
here just in case we don't remember to fix it right away.
|
|
Additional detail is available in this mail message:
id:8739itagad.fsf@yoom.home.cworth.org
|
|
Various typo fixes in auxiliary text files included with the source,
(README, TODO, etc.).
Signed-off-by: Pieter Praet <pieter@praet.org>
Edited-by: Carl Worth <cworth@cworth.org> Restricted to just text files.
|
|
We recently noticed on the mailing list a case where a message wasn't
properly connected to its parent. We should fix that of course.
|
|
As recently discussed on the mailing list. See, for example:
id:"874o5m802d.fsf@servo.factory.finestructure.net"
|
|
Such as:
mkdir build
cd build
../configure
make
This is implemented by having the configure script set a srcdir
variable in Makefile.config, and then sprinkling $(srcdir) into
various make rules. We also use vpath directives to convince GNU make
to find the source files from the original source directory.
|
|
This would be a handy feature that many people would expect to just
work.
|
|
This feature has been mentioned in the TODO file (more than once) for
quite some time now.
|
|
Seems a fairly obvious shortcoming to have survived this long.
|
|
Getting things listed here means that I can safely archive away those
messages without worrying that the ideas will get lost.
|
|
To more easily support those folks that want to Bcc with every
message.
|
|
This should allow the build to be much more automatically portable
to compilers with different sets of warning options.
|
|
Without this, trying to link with the gold linker would fail, (which meant
that notmuch could not be compiled out of the box on recent Fedora, nor
even on Debian when the binutils-gold package is installed).
|
|
This can be handy for scripts which need to extract just a thread ID from
a search term, for example.
|
|
We've done a lot of work recently without also taking care to update
the TODO file to indicate the progress.
|
|
Which would also allow the recently added test of sending an email
message with the emacs interface to be a little more honest about the
From address.
|
|
Just don't want to forget about things that people have pointed out.
|
|
I had previously thought Xapian only offered an estimate for the
number of results that might match a search. But Olly let me know
that we can easily ask for Xapian to provide the exact count.
|
|
To avoid accidentally archiving messages that have not been read.
|
|
I discussed these on the list while wrapping up the 0.3 release. They
may not make it in for that, but I don't want to forget them at least.
|
|
We can't fit all the authors and the various changed subjects in 80
columns, but it would be great is isearch could still find these, (and
automatically expand the hidden content as necessary).
|
|
It was noted today in IRC that libnotmuch is not yet careful about
wrapping all Xapian calls with try/catch blocks to print nicer error
messages. It seems it would be natural to audit that at the same time
as doing the symbol-hiding work.
|
|
One of these is a bad bug I noticed this morning, (archiving messages I had
never read when going through a search of "tag:inbox and tag:to-me" and
hitting space bar).
The other ideas came from recent conversations with Dirk and Eric.
|
|
Recent coding around the "*" feature suggests some improvements that
we could make, (some of which might push us into writing a custom
query parser rather than using the one that exists in Xapian).
|
|
There's a potential simplification of notmuch-reply.c and some emacs
improvements that might require extending message-mode to a
notmuch-message-mode.
|
|
This bug was recently noted in a commit message, so we should hold
onto it until we've passed it along to the GMime project.
|
|
The recent fix to handle utf8 in the JSON output is the kind of bug
I'd never like to see again, (so that I'd like the test suite to be
helping us track that).
|
|
Since database upgrades can be fairly painful, we'll want to do all of
these within a single release.
|
|
This is a feature that we just added without a test case.
|
|
Both of these ideas were recently discussed on the mailing list.
|
|
When trying to restore the current position, if the "current" thread
no longer appears in the buffer, then '=' moves to the current line
instead. When near the end of the buffer, the "current" line should
be counted as the number of lines from the end.
|
|
This was suggested by Srinivasa and is intended to make it easier to
integrate notmuch into an mbox-loving mail client.
|
|
I just tried (and failed) to write a test for the recent magic
inference of phrase searches. That's a feature that makes me *really*
uncomfortable to not have an automated test. But I believe the
proposed modularization of the test suite should reduce some quoting
nightmares, so will hopefully make this easier.
|
|
Adding this to our TODO list so that it doesn't get forgotten.
|
|
There's been a lot of good work done, and we've been doing a generally
poor job of noticing when some of the tasks we've completed were
already on our TODO list.
So here's a careful scan, removing all items I could find that have
already been done.
|
|
What we print and how we print it are orthogonal options, so --format
shouldn't change what messages are printed.
|
|
We've been using --output in IRC and on the mailing list for a while,
(someone had the good sense to point out that --for would defeat
command-line completion since it's a prefix of the proposed --format).
|
|
These were collected either from the mailing list of from IRC
conversations. The good ideas probably aren't mine, and the mistakes
probably are.
|
|
The notmuch_query_count_messages functions duplicates a lot of code
undesirably.
|
|
Similar to the way thread-viewing was broken after a thread was
archived, (and recently fixed), tag manipulation has also been broken
when the thread no longer matches the current search.
This also means that the behavior of '+' and '-' are now different
than that of '*'. The '+' and '-' bindings now return to the previous
behavior old affecting all messages in the thread, (and not simply
those matching the search).
I actually prefer this behavior, since otherwise a '-' operation on a
thread might not actually remove the tag from the thread, (since it
could operate on a subset of the thread and not hit all messages with
the given tag).
So I'd now like to fix '*' to be consistent with '+' and '-', for
which we add an item to TODO.
|
|
This would provide support for "muted" threads, as well as allowing for negative
filtering based on messages not matched by the original search, (but present in
threads that do have at least one matched message).
|
|
Marten Veldthuis pointed out on the mailing list that intentional
spoofing is something that the user should be told about.
|
|
This bug was recently discussed on the mailing list:
id:878wdifu13.fsf@yoom.home.cworth.org
so note one idea for fixing it.
|
|
Sometime I'll stop misspelling things so much, honets.
|
|
A new item from IRC discussion, (speeding up "notmuch restore"), as
well as a bug I just hit myself, (content from citations is not being
indexed).
While here, notce that several items have recently been completed ('?'
now displays documentation, not function names; we have a search
binding from notmush-show-mode; and "notmuch new" responds to SIGINT
by flushing). Finally, the item regarding optimizing chunky searching
is irrelevant since we dropped chunky searching in favor of the much
better streamed searching.
|
|
It's unconditional for a very short time. We expect to soon be
building it only if necessary.
|
|
Since we need to do this for portability, (some systems don't have a
strndup function), we might as well do it unconditionally. There's
almost no disadvantage to doing so, and this has the advantages of not
requiring a configure-time check nor having two different
implementations, one of which would often be less tested.
|
|
It's a bug that processing currently stops when it hits a read-only
file. This is yet another case we'll want our test suite to cover.
|
|
|
