On Sat, Oct 24, 2009 at 5:26 AM, Hari Krishna Dara <[email protected]>wrote:

>
> On Fri, Oct 23, 2009 at 2:55 AM, anna <[email protected]> wrote:
> >
> > Hi all,
> >
> > After finishing the execution of a command, is there a way to hide the
> > command-line editor? The one that is at the bottom of vim. I am not
> > too sure whether my terminology is correct.
> > I am sending a command from other process through OLE. The command is
> > shown at the very bottom line of vim window. For example, the process
> > send command ":call foo()". Then ":call foo()" is shown at the very
> > bottom line of vim window. One alternative to remove it, I could use
> > <C-L>. However, it is quite costly. I simply want the command not
> > shown. Is there a way to set it hidden or not shown?
>
> <C-L> or :redraw shouldn't be that expensive, unless you are talking
> about slow terminals (which you probably don't use, as you are using
> OLE), so you could try using the ":call foo() | redraw".
>
>
There is a side effect if I call redraw. When I send too many commands in a
short time, the screen will be blinking, which I don't like it.


> Also, if you are using |clientserver| features, then you could use
> remote_expr('foo()') instead of remote_send(":call foo()\<CR>"). The
> other alternative is to do a NOP right after the command, something
> like: remote_send(":call foo()\<CR>:\<BS>").
>

Yes, I can use remote_expr() (or eval() in my case) without having the
effect of showing the command in command-line editor. However, as the
command that is sent is modifying the buffer, I have to force 'redraw' the
screen to see the updated buffer. Again, I will have the above side effect,
blinking screen.

Sending NOP command is good idea. It can remove the command shown in the
command line editor.
However, now I have a blinking command-line editor. :)
Any further advice?



> --
> HTH,
> Hari
> >
> > Cheers,
> > Anna
> > >
> >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to