~rockorager

St. Paul, MN

https://timculverhouse.com/

Trackers

~rockorager/vaxis

Last active 2 days ago

~rockorager/go-jmap

Last active 5 months ago

~rockorager/shtc

Last active 9 months ago

~rockorager/hutui

Last active 11 months ago

~rockorager/tcell-term

Last active 1 year, 3 months ago

#14 Emacs cursor jumps around in terminal 16 days ago

Comment by ~rockorager on ~rockorager/vaxis

Tim Culverhouse referenced this ticket in commit 4e50bf4.

REPORTED RESOLVED FIXED

#13 Don't wrap when printing a month ago

Ticket created by ~rockorager on ~rockorager/vaxis

Don't wrap lines when printing. This can mess up selection mechanisms in terminals / tmux. Instead, use \n or hard reposition the cursor when lines change.

#234 office365 cannot reconnect a month ago

Comment by ~rockorager on ~rjarry/aerc

On Tue Mar 5, 2024 at 9:35 AM CST, ~gilcu3 wrote:

I have an office365 account working with IMAP through the mutt_oauth2.py script. After some time the connection is lost, and the log shows:

INFO  2024/03/05 16:03:42.093341 account.go:307: [unilu] disconnected.
ERROR 2024/03/05 16:03:42.095804 account.go:409: [unilu] connection error: imap client not connected: attempt reconnect
ERROR 2024/03/05 16:03:42.095845 status.go:133: unilu: imap client not connected: attempt reconnect
DEBUG 2024/03/05 16:03:42.095862 status.go:108: unilu: imap client not connected: attempt reconnect
ERROR 2024/03/05 16:03:42.096902 account.go:415: [unilu] unexpected error: AUTHENTICATE failed.
ERROR 2024/03/05 16:03:42.096925 status.go:133: unilu: AUTHENTICATE failed.
DEBUG 2024/03/05 16:03:42.096933 status.go:108: unilu: AUTHENTICATE failed.
ERROR 2024/03/05 16:03:42.768229 account.go:415: [unilu] unexpected error: AUTHENTICATE failed.: time: invalid duration "16251752662s"
ERROR 2024/03/05 16:03:42.768287 status.go:133: unilu: AUTHENTICATE failed.: time: invalid duration "16251752662s"
DEBUG 2024/03/05 16:03:42.768301 status.go:108: unilu: AUTHENTICATE failed.: time: invalid duration "16251752662s"

By using the :connect command the account connects again without issues.

For this account it also happens that the INBOX folder does not show new messages (although the number of messages does change automatically on the left view). Just mentioning in case it is somehow related.

This error is because the ParseDuration function is overflowing. We do math.Pow(1.8, retires). When retries == 40, this equals that duration. ParseDuration expects a uint64 / nanoseconds...so 1 second == 1 billion nanoseconds...so the maximum parseable duration in seconds is 9,223,372,036. We should probably add a protection to this method and max out our retry timer!

I'm not sure why you are failing to connect the first 39 times though.

-- Tim

#12 Support function keys after F12 a month ago

on ~rockorager/vaxis

~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?

#12 Support function keys after F12 a month ago

Comment by ~rockorager on ~rockorager/vaxis

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>.

In legacy encodings, these are the same key. Using kitty keyboard protocol you can differentiate if you have a real F31 key. F31 would be \x1b[57394u in kitty protocol.

#11 Support Ctrl / Alt / Shift + Arrows a month ago

Comment by ~rockorager on ~rockorager/vaxis

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?

#12 Support function keys after F12 a month ago

Comment by ~rockorager on ~rockorager/vaxis

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, :

Vaxis already supports keys up to F35 in both "xterm" encoding and "kitty" encoding. The encodings I added are VT220 encodings which are only defined up to F20.

  • 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.

In the presence of kitty encoding, this would be possible. Alacritty now supports kitty encoding, however vim has some limited detection support. The reason it doesn't work is that there is no legacy encoding for . Vaxis supports this encoding in kitty.

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!

This should work just the same in vaxis as long as your F31 is encoded properly. F31 is encoded as \E[18;5~ in legacy encodings.

#12 Support function keys after F12 a month ago

on ~rockorager/vaxis

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... :)

#12 Support function keys after F12 a month ago

Comment by ~rockorager on ~rockorager/vaxis

Tim Culverhouse referenced this ticket in commit 5224b90.

REPORTED RESOLVED FIXED

#12 Support function keys after F12 a month ago

Comment by ~rockorager on ~rockorager/vaxis

On Tue Feb 20, 2024 at 11:05 PM CST, ~skejg wrote:

Would be great if vaxis could support function keys like F13 or F31 for instance.

Vaxis does support these keys. Is this the 25~ encoding you mentioned earlier? I currently don't have this encoding supported, but I will add it and the others up to F20 (34~) as documented here