> My general rule for where determining where functionality should be placed > when > developing stacks is this: where can I implement this functionality that it > would require the least level of code duplication/reimplementation? I'm pretty > sure that's at the terminal level in this instance. I don't find this patch > unreasonable for any other reason, so I don't understand this rejection.
I agree with you, but the problem I can say with terminal emulators is nobody thought this kind of questions, and we have duplicated this functionality in all the places (terminal, session multiplixer and pagers). The correct place in plan 9 was the terminal, but in unix world we can delete the others two, so it is a bit more difficult for me see where is the correct place. > tmux and the like are useful, but I consider its implementation of a > scrollback > buffer to be a duplication of functionality that the terminal emulator should > already include (although obviously, the usefulness of the terminal's > scrollback buffer in tmux's instance is of limited use due to the way it is > implemented). I don't like use tmux or screen because I find them implementing things that should be in other places, and because they basically impletements a terminal over a terminal, that from my point of view is a non sense (although it's clear that they are useful when you connect to other system through a ssh connection). -- Roberto E. Vargas Caballero _______________________________________________________________________ 'Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface' (Doug McIlroy) In Other Words - Don't design like polkit or systemd _______________________________________________________________________
