This is a more permanent location for them, allowing users to recover
drafts across reboots.

Changelog-changed: Move drafts to ${XDG_STATE_HOME:-$HOME/.local/state}
 from /tmp. On many systems, /tmp is destroyed on reboots, so this
 change will allow users a better chance at being able to recover
 a draft.
Signed-off-by: Tristan Partin <tristan@partin.io>
---
 app/compose.go              | 2 +-
 commands/account/recover.go | 3 ++-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/app/compose.go b/app/compose.go
[message trimmed]

On Wed Oct 23, 2024 at 10:50 AM CST, Andrew Jeffery wrote:
> Enable the filtering to use the standard FilterList function, including
> fuzzy filtering if configured. Also enable case-insensitive matching.
>
> Changelog-changed: Path completion now uses the normal filtering
>  mechanism, respecting case sensitivity and the fuzzy completion option.
> Signed-off-by: Andrew Jeffery <dev@jeffas.net>
> ---
>  commands/testdata/Foobar |  0
>  commands/util.go         | 65 ++++++++++++++++++++++++++++++----------
>  commands/util_test.go    | 15 ++++++----
>  3 files changed, 60 insertions(+), 20 deletions(-)
>  create mode 100644 commands/testdata/Foobar
>

History is more like application state than a cache you would just want
to blow away. Let's reflect that in the path for the history file.

Changelog-changed: The location of the command history file has
 changed to ${XDG_STATE_HOME:-$HOME/.local/state}/aerc/history.
Signed-off-by: Tristan Partin <tristan@partin.io>

---

v2: Removed backwards compat.

---
 commands/history.go |  4 ++--
 lib/xdg/xdg.go      | 13 +++++++++++++
[message trimmed]

On Tue Oct 22, 2024 at 8:28 PM CST, Syed Fasiuddin wrote:
> On Wed Oct 23, 2024 at 6:28 AM IST, Tim Culverhouse wrote:
>
>> Do we really need this level of backwards compat for a history file?? Curious
>> what everyone thinks.
>
> I would suggest, we read the history file from previous location and
> delete it. Then write the previous history and all new history to the
> new location.

If this is what people want, I'm happy to implement it. I'm also happy 
to just not have any backwards compat. aerc has been happy in the past 
to break user configs.

History is more like application state than a cache you would just want
to blow away. Let's reflect that in the path for the history file.

Changelog-changed: The default location of the command history file
 has changed to ${XDG_STATE_HOME:-$HOME/.local/state}/aerc/history. The
 change accounts for backwards compatibility however, and will continue
 to use the original location for as long as it exists.
Signed-off-by: Tristan Partin <tristan@partin.io>
---
 commands/history.go |  8 +++++++-
 lib/xdg/xdg.go      | 13 +++++++++++++
 2 files changed, 20 insertions(+), 1 deletion(-)

diff --git a/commands/history.go b/commands/history.go
[message trimmed]

On Sun Sep 22, 2024 at 6:10 AM EDT, Thomas Teixeira wrote:
> Hi !
> A few days ago, it started making the switch from neomutt to aerc and I'm 
> really glad I did.
> However, my editors' colors were not working at all for a few days making it 
> impossible to use aerc.
>
> I first tracked it down as vaxis using colons as its truecolor delimiter instead of 
> semicolons and `st` not supporting those.
> I custom patched my st but colors were "off". 
> It took me an  embarasingly long time to found out that by default vaxis does 
> palette approximation. 
> It only uses truecolors if the `COLORTERM` variable is set or if the 
> _XTGETTCAP_ response contains "RGB". I never thought of the former and the latter 

On Sat Sep 14, 2024 at 4:48 AM EDT, Rocky wrote:
> To whomever may assist me,
>
> Hello, I’m rocky.go.lucky, and I’m excited to get started with aerc,
> but I’m having some setup issues with the TLS certificate pinning
> involved with Proton Mail Bridge. I sense macOS handles this
> differently than Linux.
>
> I’m trying to set up aerc on macOS with Proton Mail Bridge and split
> accounts. I went through the normal account creation dialog, and then
> added the two other split accounts using the `:new-account` command.
>
> I started with this tutorial from the official wiki:
> https://man.sr.ht/~rjarry/aerc/providers/protonmail.md

Right now, copy-to-replied is an account wide setting. Unfortunately, 
I interact with mailing lists[0] that send me a copy of the email I sent 
already, so this means that I get two copies of an email, which is 
unproductive. I'd love the ability to set it per folder. I find this 
setting most valuable when I am using SourceHut lists. I haven't tried 
mailman (is postgres mailmain?), so I can't confirm how this setting 
interacts there.

[0]: lists.postgresql.org...

-- 
Tristan Partin
https://tristan.partin.io

Pretty much all of these errors are us passing non-const format strings
to various methods. In C land, this is a large security issue. I would
assume the same stands in Go. Thank you golangci-lint!

Signed-off-by: Tristan Partin <tristan@partin.io>
---
 GNUmakefile                     |  2 +-
 app/authinfo.go                 | 10 ++++------
 app/dirlist.go                  |  4 ++--
 app/dirtree.go                  |  4 ++--
 app/getpasswd.go                |  2 +-
 app/listbox.go                  |  8 +++-----
 app/pgpinfo.go                  |  2 +-
 lib/crypto/gpg/gpgbin/gpgbin.go |  2 +-
[message trimmed]

On Thu Sep 19, 2024 at 9:13 AM CDT, Bence Ferdinandy wrote:
> Currently if you want to explore what templates resolve to, it's a bit
> of pain. Add an echo command that doesn't do anything, other than prints
> the string that is its argument with the templates resolved.
>
> Implements: https://todo.sr.ht/~rjarry/aerc/277
> Changelog-added: Added :echo command that prints its arguments with
>  templates resolved.
> Signed-off-by: Bence Ferdinandy <bence@ferdinandy.com>
> ---
>  commands/echo.go | 26 ++++++++++++++++++++++++++
>  doc/aerc.1.scd   |  3 +++
>  2 files changed, 29 insertions(+)
>  create mode 100644 commands/echo.go