Monday, June 23, 2014

Re: way to force vim to do a read (already in 'autoread')

On Saturday, June 21, 2014 4:01:32 AM UTC+12, Linda A. Walsh wrote:
> As far as 'which' vim to send it to, It'd be nice to be able to send
> to it by 'name' of the file it is editing -- as the 'monitor vim'
> always displays "/tmp/out" (/tmp is a normal "xfs" file system as well).

Why not?

gvim --servername /tmp/out /tmp/out

(Note that case is not significant in vim server names, and when they're listed
they show in uppercase.)

> When the vim's are minimized, I go by the filename displayed on the task
> bar to know which one to use if I need to open one. Sometimes will have
> 'greater than' 10 vim's open on various files in the project.

Some people like to work with vim that way, I do. Some don't, and go to lengths to have lots of tabs and lots of windows and buffers in each tab; I've never understood that.

> I am using a monitoring script (perl) to trigger the make ...

So, maybe get the script to run

vim --servername /tmp/out --remote-send ":checkt<cr>"

when it thinks there might be more output to see.

Regards, John Little

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment