~rjarry/aerc#52: 
Seems like aerc and its :term understand <F13> differently

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.

Status
REPORTED
Submitter
~john1doe
Assigned to
No-one
Submitted
a month ago
Updated
7 days ago
Labels
No labels applied.

~rjarry 15 days ago

Hi,

I don't have an <F13> key on my keyboard to reproduce the issue. However, I assume this is due to discrepancies between your own terminal emulator in which you are running aerc itself, and the terminal emulator of aerc (based on libvterm) which is used to execute $EDITOR, $PAGER and :term.

Do you have the same issue with <F12>?

~poldi1405 9 days ago

F13-F24 are rarely there as physical keys. You can try Shift+F1…Shift+F12

~john1doe 7 days ago

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.

Register here or Log in to comment, or comment via email.