<feed xmlns='http://www.w3.org/2005/Atom'>
<title>aerc/worker, branch 0.5.2</title>
<subtitle>mirror of ~rjarry's aerc fork - a pretty good email client
</subtitle>
<id>https://git.tilde.institute/akspecs/aerc/atom?h=0.5.2</id>
<link rel='self' href='https://git.tilde.institute/akspecs/aerc/atom?h=0.5.2'/>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/'/>
<updated>2020-10-11T07:18:45Z</updated>
<entry>
<title>imap: add sort support</title>
<updated>2020-10-11T07:18:45Z</updated>
<author>
<name>Reto Brunner</name>
<email>reto@labrat.space</email>
</author>
<published>2020-09-12T13:05:02Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=b6bcf89784605aa8baa982677de9d8d8ddbaa404'/>
<id>urn:sha1:b6bcf89784605aa8baa982677de9d8d8ddbaa404</id>
<content type='text'>
</content>
</entry>
<entry>
<title>notmuch: rename method to SetFlag</title>
<updated>2020-09-27T17:00:58Z</updated>
<author>
<name>Reto Brunner</name>
<email>reto@labrat.space</email>
</author>
<published>2020-09-27T17:00:58Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=c48f228fa5ac57984af78e19713929224874aa8b'/>
<id>urn:sha1:c48f228fa5ac57984af78e19713929224874aa8b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>notmuch: close tag object</title>
<updated>2020-09-24T19:24:44Z</updated>
<author>
<name>Reto Brunner</name>
<email>reto@labrat.space</email>
</author>
<published>2020-09-24T19:24:44Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=6654c970e6400e3d97344a8c982770a36e6f78ba'/>
<id>urn:sha1:6654c970e6400e3d97344a8c982770a36e6f78ba</id>
<content type='text'>
</content>
</entry>
<entry>
<title>handle message unknown charset error</title>
<updated>2020-08-31T20:00:28Z</updated>
<author>
<name>Jeff Martin</name>
<email>jeffmartin@gmail.com</email>
</author>
<published>2020-08-21T18:58:30Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=0acb28645fe73d488b82d2915add6c262028bbe3'/>
<id>urn:sha1:0acb28645fe73d488b82d2915add6c262028bbe3</id>
<content type='text'>
This change handles message parse errors by printing the error when the
user tries to view the message. Specifically only handling unknown
charset errors in this patch, but there are many types of invalid
messages that can be handled in this way.

aerc currently leaves certain messages in the msglist in the pending
(spinner) state, and I'm unable to view or modify the message. aerc also
only prints parse errors with message when they are initially loaded.
This UX is a little better, because you can still see the header info
about the message, and if you try to view it, you will see the specific
error.
</content>
</entry>
<entry>
<title>base models.Address on the mail.Address type</title>
<updated>2020-08-20T17:18:57Z</updated>
<author>
<name>Reto Brunner</name>
<email>reto@labrat.space</email>
</author>
<published>2020-08-19T10:01:45Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=c84630714405a1e93766a6a6c023801302a3ea66'/>
<id>urn:sha1:c84630714405a1e93766a6a6c023801302a3ea66</id>
<content type='text'>
This allows us to hook into the std libs implementation of parsing related stuff.
For this, we need to get rid of the distinction between a mailbox and a host
to just a single "address" field.

However this is already the common case. All but one users immediately
concatenated the mbox/domain to a single address.

So this in effects makes it simpler for most cases and we simply do the
transformation in the special case.
</content>
</entry>
<entry>
<title>Add support for :rmdir</title>
<updated>2020-08-19T09:38:57Z</updated>
<author>
<name>ARaspiK</name>
<email>araspik@protonmail.com</email>
</author>
<published>2020-08-18T20:27:23Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=fe1cabb077cf6c6cb3de122b3f5532acbeba8c85'/>
<id>urn:sha1:fe1cabb077cf6c6cb3de122b3f5532acbeba8c85</id>
<content type='text'>
The `:rmdir` command removes the current directory (`-f` is required if
the directory is not empty).

This is not supported on the notmuch backend.

An issue with the maildir backend is that some sync programs (e.g.
offlineimap) may recover the directory after it is deleted.  They need
to specifically be configured to accept deletions, or special commands
need to be executed (e.g. `offlineimap --delete-folder`) to properly
delete folders.

A danger of using this on the IMAP backend is that it is possible for a
new message to be added to the directory and for aerc to not show it
immediately (due to a slow connection) - using `:rmdir` at this moment
(with `-f` if the directory already contains messages) would delete the
directory and the new message that just arrived (and all other
contents).  This is documented in aerc(1) so that users are aware of
possible risks.
</content>
</entry>
<entry>
<title>improve date parsing for notmuch/maildir</title>
<updated>2020-08-10T06:00:52Z</updated>
<author>
<name>Reto Brunner</name>
<email>reto@labrat.space</email>
</author>
<published>2020-07-26T23:48:22Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=f1a0fd20d6d30fb1203ffa3cb9f4004476acfdb3'/>
<id>urn:sha1:f1a0fd20d6d30fb1203ffa3cb9f4004476acfdb3</id>
<content type='text'>
If a message date would fail to parse, the worker would never receive
the MessageInfo it asked for, and so it wouldn't display the message.

The problem is the spec for date formats is too lax, so trying to ensure
we can parse every weird date format out there is not a strategy we want
to pursue. On the other hand, preventing the user from reading and
working with a message due to the error format is also not a solution.

The maildir and notmuch workers will now fallback to the internal date, which
is based on the received header if we can't parse the format of the Date header.

The UI will also fallback to the received header whenever the date header can't
be parsed.

This patch is based on the work done by Lyudmil Angelov &lt;lyudmilangelov@gmail.com&gt;
But tries to handle a parsing error a bit more gracefully instead of just returning
the zero date.
</content>
</entry>
<entry>
<title>notmuch: manually close notmuch objects</title>
<updated>2020-08-07T07:49:57Z</updated>
<author>
<name>Reto Brunner</name>
<email>reto@labrat.space</email>
</author>
<published>2020-08-07T07:49:47Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=7a9fe3824f49905f46700a4620cce97fdd32b3eb'/>
<id>urn:sha1:7a9fe3824f49905f46700a4620cce97fdd32b3eb</id>
<content type='text'>
There seems to be some race with the automatic closing that should happen
in theory... close it manually where we can to avoid the issue
</content>
</entry>
<entry>
<title>maildir: Provide nicer error message on invalid url</title>
<updated>2020-07-27T16:26:57Z</updated>
<author>
<name>Tero Koskinen</name>
<email>tero.koskinen@iki.fi</email>
</author>
<published>2020-07-25T08:11:13Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=f81cc2803cca4a5213a9d4514ddae8417c23f8ee'/>
<id>urn:sha1:f81cc2803cca4a5213a9d4514ddae8417c23f8ee</id>
<content type='text'>
If accounts.conf contains an invalid maildir url, return a nice
error instead of panicking.

Log a couple of different error cases to provide extra
information about the error to the user.
</content>
</entry>
<entry>
<title>Remove hard coded bodystruct path everywhere</title>
<updated>2020-07-27T07:19:27Z</updated>
<author>
<name>Reto Brunner</name>
<email>reto@labrat.space</email>
</author>
<published>2020-06-19T15:58:08Z</published>
<link rel='alternate' type='text/html' href='https://git.tilde.institute/akspecs/aerc/commit/?id=c574a838fa89bf46bf7188442f400b206b04df95'/>
<id>urn:sha1:c574a838fa89bf46bf7188442f400b206b04df95</id>
<content type='text'>
Aerc usually used the path []int{1} if it didn't know what the proper path is.
However this only works for multipart messages and breaks if it isn't one.

This patch removes all the hard coding and extracts the necessary helpers to lib.
</content>
</entry>
</feed>
