Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

Re^2: bcvi - run vi over a 'back-channel'

by grantm (Parson)
on Jan 05, 2008 at 07:53 UTC ( #660518=note: print w/ replies, xml ) Need Help??


in reply to Re: bcvi - run vi over a 'back-channel'
in thread bcvi - run vi over a 'back-channel'

At the risk of feeding a troll ...

There's nothing in the linked page that in any way mimics the functionality of bcvi - namely allowing you to type 'vi filename' in a remote shell window and have a gvim session start on your workstation.

The page seems to describe a plugin for Emacs (called TRAMP) that offers equivalent functionality to Vim's 'netrw' feature.

It would certainly be possible to modify bcvi to work with Emacs+TRAMP rather than gvim+netrw.


Comment on Re^2: bcvi - run vi over a 'back-channel'
Re^3: bcvi - run vi over a 'back-channel'
by Anonymous Monk on Feb 01, 2008 at 14:27 UTC
    Hi, I was wondering : wheter if the netrw plugin for vi was mandatory. Because I can make it work for me. After installation I get a result connection refused. penkoad@sd-10516:~$ bcvi docs.txt Can't connect to 'localhost:10019': Connexion refusée Even though i issued (unsafely) an xhost + command to give client access to anybody. I'm puzzled. Is there a manipulation on the server more than installing bcvi script and adding the alias in the session ? regards

      You certainly don't needto do xhost +. That would only help if gvim was running on the remote server and connecting back to X on your workstation. The whole point of bcvi is to avoid forwarding X (and requiring gvim and X libraries on the server). Instead, bcvi uses a forwarded socket to pass one message back to your workstation which then invokes gvim with an scp-style file path.

      If you type bcvi filename on the server and get Can't connect to 'localhost:10019' then that suggests perhaps the SSH daemon on the server has been configured to refuse TCP forwarding requests. You can find out for sure by running a command like this to connect to the server:

      ssh -v -R 10019:localhost:10019 servername

      The '-v' will mean you get a lot of debugging output which ought to include a line like this:

      debug1: remote forward success for: listen 10019, connect localhost:10 +019

      but in your case there may be an error indicating that the 'remote forward' was not successful. The fix would be to make sure the sshd_config on the server includes:

      AllowTcpForwarding yes

      Even if you can't make bcvi work, you should still be able to edit a remote file like this:

      gvim scp://server//path/to/some/file

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://660518]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (6)
As of 2014-12-20 03:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (95 votes), past polls