2018-03-19 5:25 GMT+09:00 Manuel Ortega <[email protected]>: > On Sun, Mar 18, 2018 at 4:10 PM, Kazunobu Kuriyama < > [email protected]> wrote: > >> 2018-03-19 4:26 GMT+09:00 Bram Moolenaar <[email protected]>: >> >>> >>> Until recently, the GUI used a "dumb" terminal for external commands. >>> With patch 8.0.1616 it is now possible to run an external command inside >>> the GUI window. Try it out with: >>> :set go+=! >>> :!cat testdir/color_ramp.txt >>> >> >> Seems like we need to run :so testdir/color_ramp.vim before running the >> cat command; there seems to be no color_ramp.txt in the repo... >> >> And the result is...very impressive! Not only colors are displayed >> correctly, but also its drawing is noticeably faster than that of the >> "dumb" terminal. >> > > On the contrary, the drawing is much, much slower than with the dumb > terminal, when using the MacVim gui. I don't know if this is a MacVim > specific problem or not, but it makes using the non-dumb terminal into what > I would call a regression (it's that slow and laggy). >
Are you sure that MacVim has already included Patch 8.0.1616? How can you conclude that using the new non-dumb terminal would result in "regression"? > > Also, when using the dumb terminal to show `!ls`, I see: > > ``` > :!ls > one two three > four five six > [blank line] > Press ENTER or type command to continue > ``` > But when using "!" in &cpo on MacVim, the blank line is in a different > place. It's right below `:!ls`, and before the output of the `ls` > command. Then the "Press ENTER" part has no blank line above it to > separate it from the `ls` output. > I can't reproduce. BTW, you are talking about 'cpo' (cpoptions) here and below, but it should be 'go' (guioptions). Are they typos? > > Finally, another reason to not put "!" in &cpo by default just yet is that > the colors are hard to read if your colorscheme has a black or nearly black > background. This is *not* a MacVim specific problem. There is an open > thread about this on GitHub, I think. Maybe that should be solved before > making "!cmd" result in nigh-invisible output. > That is rather a well-known, classic issue that blue is hardly visible on a dark background color, as is written in the comment of app-defaults/XTerm-color. That has happened with color consoles as well. Perhaps we could "correct" the pixel values of blue (color4) and light blue (color12) just like the XTerm-color comment suggests, but there seems to be pros and cons as to what values are better than the current ones. Anyway, it is the fact that xterm has been shipped with them and that nobody has never stopped it. > -Manny > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
