From: Tomi Ollila <tomi.ollila@iki.fi>
To: Jesse Rosenthal <jrosenthal@jhu.edu>,
	Mark Walters <markwalters1009@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Avoid empty thread names if possible.
In-Reply-To: <87a94f2fe3.fsf@jhu.edu>
References: <87oatnakqy.fsf@jhu.edu> <87tx2nuvec.fsf@qmul.ac.uk>
	<87a94f2fe3.fsf@jhu.edu>
User-Agent: Notmuch/0.18.1+130~ga61922f (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-unknown-linux-gnu)
Date: Wed, 29 Oct 2014 15:32:03 +0200
Message-ID: <m2bnov57e4.fsf@guru.guru-group.fi>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

On Wed, Oct 29 2014, Jesse Rosenthal <jrosenthal@jhu.edu> wrote:

> By the way, this discussion brings up another problem. I wasn't able to
> write a test for this (to address the below concerns) because the test
> suite for thread-naming supplies some sort of auto-generated subject
> for threads with empty subjects. So we can't test behavior for dealing
> with empty subjects.
>
> Unfortunately, I don't know the history of the test suite, or why this
> auto-subject decisicion was made, so I don't feel comfortable just
> changing the behavior.

Autogeneration of (unique) headers when some header not given...

Shell could distinguish between unset and empty variable, but that would
proably make most users feel PITA to use it... (*)

... probably better altelnative could be some magic word, like 'none' to
make generate_message() set header in question empty (and first just
implement that "feature" to Subject header.

Tomi

(*) personally I'd be totally comfortable with it, though ;D