James Vega wrote:
> The print_line function in src/ex_cmds.c (which is used by :print,
> :list, :number, :z, :s with the 'p' flag) sets the info_message variable
> to TRUE and only sets it back to FALSE if save_silent is set. This then
> causes msg_puts_attr_len (via wait_return) to call msg_puts_printf
> instead of msg_puts_display -- displaying the "Press ENTER or type
> command to continue" inline with the output of the shell instead of in
> Vim.
>
> An easy example to reproduce from Vim's top-level source directory:
>
> vim -u NONE -N Makefile
> :number
> :!ls
> :!ls
>
> Notice that after the first ":!ls", the "Press ENTER" message isn't
> displayed. In the output of the second ":!ls", you see the first "Press
> ENTER" message and the ls output is skewed to the right.
Thanks.
Is there something against moving "info_message = FALSE" to after the
if {}? Matters for silent mode.
--
hundred-and-one symptoms of being an internet addict:
31. You code your homework in HTML and give your instructor the URL.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
