Re: doc nitpicking

2007-10-14 Fir de Conversatie ap
On Oct 12, 9:31 pm, Bram Moolenaar [EMAIL PROTECTED] wrote: The docs are correct, :silent !true doesn't mess up the display for me. Check your shell init scripts for something that produces output. ... Apparently your termcap settings are causing this. Try this: :set

Re: doc nitpicking

2007-10-11 Fir de Conversatie Yakov Lerner
The screen is not redrawn then, thus you have to use CTRL-L or :redraw! if the command did display something. I do not think this paragraph can be interpreted ambiguously. The first part - The screen is not redrawn then - I see it as information not operational, it does not contradict

Re: doc nitpicking

2007-10-11 Fir de Conversatie Ben Schmidt
vim -u NONE :help helpget some text on screen, and statuslines :silent :true The screen is garbled. Not for me. I think the point made earlier was that the docs actually, in the most strict logical sense, don't say anything about what you need to do if a command

Re: doc nitpicking

2007-10-11 Fir de Conversatie Yakov Lerner
On 10/11/07, Yakov Lerner [EMAIL PROTECTED] wrote: On 10/11/07, ap [EMAIL PROTECTED] wrote: On Oct 10, 10:22 pm, Yakov Lerner [EMAIL PROTECTED] wrote: :help :! says: :silent !{cmd} The screen is not redrawn then, thus you have to use CTRL-L or

Re: doc nitpicking

2007-10-11 Fir de Conversatie Bram Moolenaar
Yakov Lerner wrote: :help :! says: :silent !{cmd} The screen is not redrawn then, thus you have to use CTRL-L or :redraw! if the command did display something. The last part (if the command did display something) is not true. In console vim, screen is always

Re: doc nitpicking

2007-10-11 Fir de Conversatie Yakov Lerner
On 10/11/07, Bram Moolenaar [EMAIL PROTECTED] wrote: Yakov Lerner wrote: :help :! says: :silent !{cmd} The screen is not redrawn then, thus you have to use CTRL-L or :redraw! if the command did display something. The last part (if the command did display