Are you running the latest master?

Today's latest master, commit da10dae8.

~rjarry

Nothing has changed in this aspect:

• If my terminal emulator sends ^[[1;2P as <F13>:
  • I can map it in aerc as <F13>, aerc reacts to these mappings
  • aerc's :term doesn't recognize it: I run :term, launch cat there, press <F13>, see ^@
• If my terminal emulator sends ^[[25~ as <F13>:
  • aerc doesn't react to <F13> mappings
  • aerc's :term recognizes it correctly (cat in :term reports ^[[25~).

On Sun Sep 25, 2022 at 8:23 AM CDT, ~john1doe wrote:

~rockorager:

Partially :) I still have problems with Vim (though the mouse seems to work in some other applications, like the Midnight Commander, for example).

I run aerc, open :term, run vim -u NONE +'set mouse=a' +'set showcmd', and the cursor in Vim moves to some almost random locations when I click, while the showcmd option reports things like 18m, 22m, 11m etc in the statusline.

-- View on the web: https://todo.sr.ht/~rjarry/aerc/46#event-207115

Are you running the latest master? Robin just applied a patch that updated tcell-term, which has some rendering bug fixes (particularly some I found in vim)

~rockorager:

Partially :) I still have problems with Vim (though the mouse seems to work in some other applications, like the Midnight Commander, for example).

I run aerc, open :term, run vim -u NONE +'set mouse=a' +'set showcmd', and the cursor in Vim moves to some almost random locations when I click, while the showcmd option reports things like 18m, 22m, 11m etc in the statusline.

I don't have an <F13> key on my keyboard to reproduce the issue

Well, you can probably instruct your terminal emulator to map the required Escape sequence to any key? Or, as ~poldi1405 said, simply use <Shift-F1>.

The problem is, while we can map <F13> in aerc (and press <Shift-F1> in call this binding, it sure does work for me), it won't work in $EDITOR or :term. So, yes, as you said, some discrepancies between my terminal emulator, and the terminal emulator of aerc. Would be great to fix that somehow :)

(For anyone interested, there's a stupid workaround for this: I set in my terminal emulator <F13> to send some obscure Unicode symbol, which I won't use otherwise. And then map this symbol both in aerc and $EDITOR. This way, my <F13> key indeed works in both environments. But, of course, it's only an ugly crutch.)

Do you have the same issue with <F12>?

No, I don't.

You can try disabling mouse for aerc, and let the pager, $EDITOR or :term see the mouse events.

For me, this doesn't work.

I set mouse-enabled=false in aerc.conf, and the mouse didn't work both in aerc (expected) and in $EDITOR when composing / replying (my $EDITOR is Vim with set mouse=a) or :term's applications (like Midnight Commander, for instance). Just reporting :)

(aerv v.0.11.0)

If my terminal emulator sends <F13> as ^[[1;2P, then aerc does understand it (e.g., I can map it like <F13> :cf INBOX<Enter> in binds.conf). But in this case :term doesn't get it (cat in :term shows nothing if I press <F13>, and I can't map it in Vim, which I use for writing emails).

However, if my terminal emulator sends ^[[25~ as <F13>, then :term captures it OK (cat shows the correct value, and I can map it Vim, for instance), but aerc itself doesn't respond to it at all.

As a result, with aerc, I can't really use <F13> (and probably <F14>, <F15>, and so on).

Thank you.

Either it's just me, or this is such an old limitation that we all simply learned to live with it :)

So, for me, mouse doesn't work in either $EDITOR when composing/replying, or in the :term.

aerc 0.10.0-23-g83e0e26-dirty

This seems to be fixed in 0.9.0?

Can an option to disable the statusline messages be added? Or to limit them to some bare minimum at least, to print only errors and such?

It just keeps getting noiser and noiser with no opt-out at all.