| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2020-02-13 | lib: fix an out of bounds panic in the server | Daniel Martà | |
| If the message doesn't contain ':', we don't properly discard the message, so we end up slicing it like msg[:-1]. This can be reproduced if one runs 'aerc foo', as the server receives 'foo' as the message. 'aerc foo' still doesn't do anything very user friendly, but at least it doesn't panic horribly. While at it, do the 'got message' log at the very beginning, so that the user can see what message the server got before reporting the command as invalid. Signed-off-by: Daniel Martà <mvdan@mvdan.cc> | |||
| 2019-09-29 | Print success to socket if no error was thrown | Heiko Carrasco | |
| When Reto Brunners patch is applied (which works really well for me), the user gets to see the message returned by AercServer. Since this is nil if no errors were thrown it prints "result: <nil>" to the cmd. This patch fixes that by just returning success instead of the error message when err != nil. | |||
| 2019-07-29 | Fix test failures | Drew DeVault | |
| 2019-07-19 | Forward mailto links to server via ./aerc <mailto> | Drew DeVault | |
| 2019-07-19 | Add Unix socket for communicating with aerc | Drew DeVault | |
 |
index : aerc | |
| A pretty good email client | cos |
| summaryrefslogtreecommitdiff |