Thanks to Austin's prodding and debugging and pointing out contradictory
evidence I have looked into this bug in more detail and think I have got
the actual cause this time.
Having chased it all down I think there is a one line fix. Since I had
already written the rest of the email when I
Thanks to Austin's prodding and debugging and pointing out contradictory
evidence I have looked into this bug in more detail and think I have got
the actual cause this time.
Having chased it all down I think there is a one line fix. Since I had
already written the rest of the email when I
Quoth Jameson Graef Rollins on Sep 04 at 8:50 am:
> On Wed, Sep 04 2013, Austin Clements wrote:
> >> Now, some mime parts have subparts and to avoid overwriting the
> >> sub-part data notmuch checks and if part data is already recorded it
> >> does not overwrite it.
> >>
> >> Now with lazy part
Quoth Mark Walters on Sep 04 at 8:30 am:
> The lazy part handling had a subtle bug. Notmuch stores the part
> information as a text property with the displayed part so attachment
> handling (saving viewing etc work).
s/ work)/) work/
>
> Now, some mime parts have subparts and to avoid
On Wed, Sep 04 2013, Austin Clements wrote:
>> Now, some mime parts have subparts and to avoid overwriting the
>> sub-part data notmuch checks and if part data is already recorded it
>> does not overwrite it.
>>
>> Now with lazy part handling this could fail: there is already part
>> data
The lazy part handling had a subtle bug. Notmuch stores the part
information as a text property with the displayed part so attachment
handling (saving viewing etc work).
Now, some mime parts have subparts and to avoid overwriting the
sub-part data notmuch checks and if part data is already
The lazy part handling had a subtle bug. Notmuch stores the part
information as a text property with the displayed part so attachment
handling (saving viewing etc work).
Now, some mime parts have subparts and to avoid overwriting the
sub-part data notmuch checks and if part data is already
Quoth Mark Walters on Sep 04 at 8:30 am:
The lazy part handling had a subtle bug. Notmuch stores the part
information as a text property with the displayed part so attachment
handling (saving viewing etc work).
s/ work)/) work/
Now, some mime parts have subparts and to avoid overwriting
Quoth Jameson Graef Rollins on Sep 04 at 8:50 am:
On Wed, Sep 04 2013, Austin Clements amdra...@mit.edu wrote:
Now, some mime parts have subparts and to avoid overwriting the
sub-part data notmuch checks and if part data is already recorded it
does not overwrite it.
Now with lazy part
On Wed, Sep 04 2013, Austin Clements amdra...@mit.edu wrote:
Now, some mime parts have subparts and to avoid overwriting the
sub-part data notmuch checks and if part data is already recorded it
does not overwrite it.
Now with lazy part handling this could fail: there is already part
data
10 matches
Mail list logo