@soywod, Thanks for heads up! It's always a pleasure communicating with you :)

@soywod, thanks for the explanation, did subscribe to this GitHub issue :)

@soywod, thanks, great news! :)

However, I noticed this one thing: the himalaya I tried earlier (in April, 2023, version 0.7.3), would truncate long Subject lines, as it's shown in the help, like this:

https://i.imgur.com/mCyrxN9.png

The latest master I tried just now, tries to wrap those, which not only looks awful but also conflicts with the rows number (printing out more rows than requested):

https://i.imgur.com/6dbun2e.png

Not sure if this is directly related to this your width fixing commit, or was it changed prior to that, just wanted to let you know :)

~skejg hopefully this is what you were looking for: https://lists.sr.ht/~rjarry/aerc-devel/patches/53626

If i set the default-menu-cmd to something like this:

default-menu-cmd=sort | fzf

...then directories related mappings, like :menu -d :cf<Enter>, work just fine.

However, calling the :attach mapping like this:

[compose::review]
a = :menu :attach<Enter>

...then seems to break. And if I remove this sort | part from default-menu-cmd, then the above mapping starts to work again.

May be that's some relics from the times when aerc had file-picker-cmd? And in case of :attach, default-menu-cmd is parsed somehow different?

~rockorager

Again, thanks for your reply. As I said, I'm probably missing something here. But the problem is that with tcell the setup I described above was working for me in kitty / alacritty / xterm / whatever. And with vaxis it does not.

Of course, I'm open to update or change it. But to what exactly? What should I put in .Xresources, for instance, as translations for !Ctrl <Key>Return to map then <C-CR> in Vim that would work inside and outside vaxis?

F31 is encoded as \E[18;5~ in legacy encodings

I'm probably missing something but if I add this to kitty.conf:

map ctrl+enter send_text all \x1b[18;5~

Then Vim sees it as <C-F7>.

Would be great if we could use Ctrl+Left/Right to navigate by word in aerc itself just as we can everywhere else :)

On Wed Feb 21, 2024 at 9:51 AM CST, ~skejg wrote:

Hi! Thanks for your reply!

This should be working already [...] Is it by chance in aerc you don't get them?

Indeed, my bad, in :term they work. Probably, as you say, because vaxis does support them, and in :term my .inputrc or .vimrc do map them to some actions, like this:

"\e[1;3C": forward-word

or this:

nnoremap <S-Right> :tabmove +1<CR>

Now, would it be possible to bring the readline-like mappings (or maybe user's .inputrc?) to aerc itself? Like, I personally only interested in one thing: moving by word in To: / Subject: fileds and in aerc's : command line. It so frustrating that you can do it everywhere but not in aerc... :)

Yeah, this should be possible. Can you make an issue on the aerc tracker?

Again, ~rockorager, thanks for the reply -- and for your code, too!

I will add it and the others up to F20 (34~)

But why limit oneself to F20? :) Why support F20 but not F36? Here's my use case, and maybe you could advise me better, but as of now I use these sort of excessive functional keys to solve some very practical porblems -- like, to add mappings to keys terminals usually don't really capture out of the box. E.g., let's say, :

• If I launch alacritty without a config
• ...And launch vim without a config inside it
• ...Then :nnoremap <C-CR> :echo "yay"<CR> will do nothing.

However

• If I map <C-CR> in alacritty.toml to some <F31>
• And map <F31> <C-CR> in .vimrc
• Then :nnoremap <C-CR> :echo "yay"<CR> in vim will actually work!

What do you think? But then again, maybe I'm missing something... :)