3 ms·
I'd argue that the aerc approach is also bit of hack[1], but ultimately it mostly boils down to the limitations of terminals; to have "sub-windows", you need to
by zokier 7y ago
I'd argue that the aerc approach is also bit of hack[1], but ultimately it mostly boils down to the limitations of terminals; to have "sub-windows", you need to implement basically a whole windowing system and terminal emulation layer.
Makes me think what would email client designed for and integrated with tmux look like, i.e. the client would open new tmux panes for editors etc.
[1] don't take that as a hard criticism, I happen to think lot of things, especially around terminals, being hacks.
- Sir_Cmpwn 7y agoWell, it's not as hacky as you portray it to be. The windowing system already needed to be there for other aerc features (and the embedded terminal is used in more integrated contexts than just windows, too). The terminal emulation is delegated to libvterm, the same library vim uses for this purpose. The actual aerc code is pretty simple: https://git.sr.ht/~sircmpwn/aerc/tree/master/widgets/terminal.go https://git.sr.ht/~sircmpwn/aerc/tree/master/widgets/termina... <500 lines.