On Thu Aug 8, 2024 at 11:37 AM EDT, Tim Culverhouse wrote:
> On Wed Aug 7, 2024 at 8:20 PM CDT, Dian Fay wrote:
> > I just found this trying to figure the same thing out. I'm seeing the
> > same behavior on wezterm and vanilla xterm in Arch/Wayland, no
> > multiplexing involved.
>
> In wezterm, this should work if you enable kitty keyboard.
>
> The issue is that <C-h> is encoded as 0x08, which *can* mean backspace, but also
> 0x7f can mean backspace. Terminfo *can* give you this information, however many
> terminals allow the user to modify this at runtime so it isn't very reliable.
> Also our TUI library has the expressed goal of *not* using terminfo.
>
> So - <C-h> in the absence of kitty keyboard does not map to a key in the TUI

I just found this trying to figure the same thing out. I'm seeing the
same behavior on wezterm and vanilla xterm in Arch/Wayland, no
multiplexing involved.

On Tue Jul 16, 2024 at 11:08 AM EDT, Coco Liliace wrote:
> On Tue Jul 16, 2024 at 10:36 PM CST, Tim Culverhouse wrote:
> > So the issue is that tmux is sending Ctrl+h as 0x08 (which is correct). Vaxis is
> > translating this to a backspace keypress - because some terminals use 0x08 as
> > backspace. *Most* use 0x7F as backspace nowadays.
> >
> > Tcell was using terminfo to decide which of those two keys was actually
> > backspace - which is why it worked there. Vaxis doesn't use terminfo so it isn't
> > privvy to this knowledge and assumes that both 0x08 *and* 0x7f are backspace.
> >

On Wed Feb 15, 2023 at 11:43 AM EST, Moritz Poldrack wrote:
> On Wed Feb 15, 2023 at 5:41 PM CET, Dian M Fay wrote:
> > but I definitely see short writes in aerc _without_ HTTP etc issues.
>
> Thanks for confirming. Could you provide us with a logfile?
>
> -- 
> Moritz Poldrack
> https://moritz.sh

Here's a duly censored snippet starting seven minutes before a short
write error (or longer, since the previous entry is from 08:57:33). aerc
was idle in the inbox of account1, and another minute after the initial
error continues to short-write until I notice and quit the program.

Yes, I accept!

On Mon Feb 20, 2023 at 12:59 PM EST, Robin Jarry wrote:
> Hi all,
>
> as you may know, aerc is currently distributed under the MIT license.
> This prevents from shipping aerc with notmuch support always enabled
> (notmuch being GPL).
>
> After some multiple reported issues when building from source and
> countless discussions on IRC, it was suggested to change the licensing
> of aerc to GPL. Most downstream distributions already build aerc with
> notmuch support enabled anyways. This means that a lot of people are
> using aerc with GPL contamination.

No, I'm on a desktop and only sleep the monitor. The computer is either
on or off.

On Wed Feb 15, 2023 at 11:45 AM EST, Robin Jarry wrote:
> Moritz Poldrack, Feb 15, 2023 at 17:43:
> > On Wed Feb 15, 2023 at 5:41 PM CET, Dian M Fay wrote:
> > > but I definitely see short writes in aerc _without_ HTTP etc issues.
> >
> > Thanks for confirming. Could you provide us with a logfile?
>
> I also see that regularly. Would it be correlated to your computer
> waking up from sleep?

I've got it writing to a logfile now -- I can't reliably reproduce it so
it's probably going to take a few days or so.

On Wed Feb 15, 2023 at 11:43 AM EST, Moritz Poldrack wrote:
> On Wed Feb 15, 2023 at 5:41 PM CET, Dian M Fay wrote:
> > but I definitely see short writes in aerc _without_ HTTP etc issues.
>
> Thanks for confirming. Could you provide us with a logfile?
>
> -- 
> Moritz Poldrack
> https://moritz.sh

Nope, wired fiber. I'm often on a VPN and that occasionally goes
sideways to the point that I notice other connections (e.g. HTTP)
interrupted or degraded until I reconnect, but I definitely see short
writes in aerc _without_ HTTP etc issues.

On Wed Feb 15, 2023 at 2:27 AM EST, Moritz Poldrack wrote:
> Hi, short writes are usually caused by a bad connection to the server.
> Are you on mobile data or a similarly unstable medium?
> -- 
> Moritz Poldrack
> https://moritz.sh

I sometimes see this error ("accountname: short write") while idle in
the list view, but it also occasionally interrupts email sending --
nothing in Sent, reply flag not set, no evidence anything ever happened.

Only IMAP accounts, I think I've seen it with multiple providers
including gmail but I haven't been tracking it systematically.

hi there! Thank you for developing this, I've wanted a dead-simple
address book for aerc for a while now. I just added 0.1.2 to Arch's user
repository at https://aur.archlinux.org/packages/aercbook-bin .

A couple of suggestions as well, I don't know if I'll have time in the
near future to try hacking on them myself:

- remove unmatchable entries from the list and free up <tab> to move to
  the next field if none remain (when I copy+pasted the mailing list
  address into this message it still displayed the finder and wanted to
  include one of my contacts)
- parse shortcuts in the book filepath ("~/.config/aerc/book.txt") or
  use XDG_CONFIG_HOME somehow; I almost always start aerc from the home
  directory so it's unlikely to be a problem but it is a potential weird

On Fri Jun 10, 2022 at 2:12 PM EDT, Robin Jarry wrote:
> Hey there,
>
> Would you happen to connect with your account main password ?
>
> https://support.google.com/accounts/answer/6010255?hl=en
>
> This is now rejected by Google. You need to enable 2FA and create an app specific password for aerc.

Yes I did -- that worked, thank you!