>The overwhelming majority of vim/emacs developers use it in a terminal, and are pretty happy with it. When you mentioned open source editors catching up, it is

>The overwhelming majority of vim/emacs developers use it in a terminal, and are pretty happy with it. When you mentioned open source editors catching up, it isn't going to happen because your requirements are not universal. "Only if it looked shiny" is very low on todo list of vim/emacs users/developers. Way to fuck up the discussion in a disingenuous and insulting way by summing down my arguments to "I like shiny things". I specifically talked about native integration. That has myriads of aspects, of which "oh, shiny" is just an insignificant part of. As for the "overwhelming majority of vim/emacs" users using them in the terminal, citation needed. My anecdotal data tell me that they use them in both in both terminal and GUI form (terminal for working on stuff remotely, admin stuff etc, GUI for long term programming sessions). Plus, no matter what the "overwhelming majority of vim/emacs" do, those do not represent the future or cutting edge of programming editor use in any conceivable way. And that is precisely what we are discussing. >bad support for Unicode >>My terminal(terminator) does that fine. Does that answer mean that you don't have the mental capacity to follow the discussion? Maybe you're too tired or something? Isn't it obvious from my comment that I mean Unicode support THROUGHOUT the system? That one or ten terminals has got it doesn't mean a thing if there are 200 other components involved in doing unicode CLI work. For example GNU/BSD unix userland programs supporting full unicode capabilities. Unicode and font-rendering without X-running, etc etc. >Why and how would a terminal support JSON? What are those ad-hoc desktop things? What is this stupid notion that I talk about terminal emulators ONLY? I specifically bloody state that I complain about all terminal-side stuff "from terminal emulators to userland unix commands". In this case, what I ask for (when giving JSON as an example) is a structured way of communication between userland commands, to go beyond '70s style pipes. Microsoft's Powershell AFAIK has some of that built-in. >shell has to support autocomplete in million things, compared to your native app which only does one thing say Java. You'd be surprised. And context-sensitive autocomplete is so solved that it's not even a problem... >You install some utility shit_load. How on earth is shell going to complete "shit_load -<TAB>". See how luck of imagination and blind acceptance of what's there cripples programmers? Off the top of my head: programs could come with definition files for their autocompletion. Adding a program adds those to your shell (in the same way programs come with man-pages). I seriously hope you don't work in R&D. >tmux/screen scroll buffers work fine. You are just making shit up. Only if "switching in copy-mode to scroll, instead of transparently incorporating the terminal scroll buffer" fits your definition of "fine".