2017-03-18 6:51 GMT+09:00 Bram Moolenaar <[email protected]>:

>
> Kazunobu Kuriyama wrote:
>
> > The tests are done with the help of one or more command-line utilities
> > handling the system clipboard.  More specifically, xsel(1) for X11, or
> > pbcopy(1) and pbpaste(1) for macOS.
> >
> > The idea is very similar to the +-register tests I proposed recently;
> > exchanging a piece of text between vim and the utility, and comparing the
> > result with the expected value in order to check if the *-register works
> as
> > a faithful mediator between them.
> >
> > pbcopy and pbpaste are installed on macOS by default, but I'm not sure if
> > so is xsel.  Hence, please make sure whether or not xsel  is installed on
> > the host system before running the tests against the X11 clipboard (the
> > PRIMARY selection, actually).  When xsel is not found, the tests are
> > skipped leaving a message indicating that.
> >
> > I chose xsel simply because its source code was easily available to me
> and
> > was easily built and installed successfully on my macOS.
> >
> > So, in case xsel is not available to you, please consider replacing it
> with
> > another utility having the same functionality, or adding a test path
> using
> > that replacement, as the tests themselves are quite simple.
> >
> > Hopefully,  the X11 of Travis CI tests has xsel.
>
> On my system I don't have xsel.  I'm afraid that this probably means
> that most people don't have it.
>
> How about using another Vim to communicate with?  It's possible to
> control it with the client-server feature.
>

Oh my...  That reminds us of that file of the worst coverage.


>
> For Mac your solution is probably OK.  I don't think client-server works
> on Mac.
>

Well, by default, you're right.  But after XQuartz is installed,

./configure --disable-darwin --disable-gui && make

detects the X11 there automatically, and builds a vim having +clientserver
(The --disable-gui option is not essential, actually).

With the vim which was built like that way, do

./vim --servername FOOBAR

on a terminal.  Then, on another terminal,

./vim --servername FOOBAR --remote if_xcmdsrv.c

makes the first vim instance open the file given to it.

So...looks like you have had me open up a can of worms twice this week,
haven't you?...wait...It's me who triggered them.  How stupid I was! :)

Kazunobu


> --
> hundred-and-one symptoms of being an internet addict:
> 141. You'd rather go to http://www.weather.com/ than look out your window.
>
>  /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net
>  \\\
> ///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/
> \\\
> \\\  an exciting new programming language -- http://www.Zimbu.org
> ///
>  \\\            help me help AIDS victims -- http://ICCF-Holland.org
> ///
>

-- 
-- 
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.

Raspunde prin e-mail lui