~rockorager

St. Paul, MN

https://timculverhouse.com/

Trackers

~rockorager/tcell-term

Last active 21 hours ago

~rockorager/go-jmap

Last active 4 months ago

#2 Support Tc codes (38:2::r:g:bm) 4 hours ago

Comment by ~rockorager on ~rockorager/tcell-term

REPORTED RESOLVED FIXED

#3 Create a terminfo file for better terminal support 21 hours ago

Ticket created by ~rockorager on ~rockorager/tcell-term

#2 Support Tc codes (38:2::r:g:bm) 21 hours ago

Ticket created by ~rockorager on ~rockorager/tcell-term

#116 Split stuck on last message and can't be closed in empty folder a day ago

~ferdinandyb assigned ~rockorager to #116 on ~rjarry/aerc

#46 mouse in aerc's terminal doesn't work? 4 days ago

Comment by ~rockorager on ~rjarry/aerc

~john1doe, can you also try :set ttymouse=sgr and see if it fixes it?

EDIT: also what terminal are you using?

#46 mouse in aerc's terminal doesn't work? a month ago

on ~rjarry/aerc

~rockorager, I confirm that opening :term and run /usr/bin/vim -u NONE +'set mouse=a' +'set showcmd' with mouse-enabled=true results in erratic behaviour. With mouse-enabled=false, mouse events seem not forwarded to vim.

#95 Issues with pgp-opportunistic-encrypt=true a month ago

Comment by ~rockorager on ~rjarry/aerc

This boils down to how to tell the user what's going on with the encryption status. I agree we shouldn't display encryption status until the review message screen for opportunistic encryption.

There are a few options at that point:

Case A: we can encrypt

  1. Push a Success message that we can encrypt
  2. Push a Normal message that we can encrypt
  3. Do nothing, the encryption status is shown with the headers anyways
  4. Create a config option for what should happen

Case B: we can't encrypt

  1. Push an Error message that we can't encrypt, and why (ie whose keys are missing?)
  2. Push a Normal message that we can't encrypt, and why
  3. Do nothing, the headers won't have an encryption status so the user can infer it's not encrypted
  4. Create a statusline Warning style, and push a Warning message that we can't encrypt, and why
  5. Create a config option for what should happen

I like A.1 and B.2 personally, but I also like A.3 and B.4. Open to input here, it's a pretty simple change so I can put it in once we have consensus.

#10 support OSC-8 multiline URLs a month ago

Comment by ~rockorager on ~rjarry/aerc

REPORTED RESOLVED IMPLEMENTED

#80 imap: crash while switching tabs a month ago

Comment by ~rockorager on ~rjarry/aerc

This should be solved with the new event loop handling

REPORTED RESOLVED FIXED

#67 Variable $ex handling in compose::editor 2 months ago

Comment by ~rockorager on ~rjarry/aerc

: is indeed an undocumented default.