VILEGET(1) | User Contributed Perl Documentation | VILEGET(1) |
vileget - Pass file edit requests to a Vile editor running Vileserv.
vileget [-n] [-d] [-w] [-s socket-path] [-c command] [-C command] [file ...]
Vileget can be used to load files into an already running instance of Vile or XVile. The editor should have already loaded and started the Vileserv perl module. (See the Vileserv documentation for more detail.)
By default, if vileget cannot connect to a running instance of the editor it tries to start a new one. This will only work correctly if you have configured Vile to start Vileserv automatically. (Vileget will try to find an XVile binary first, then look for a Vile binary.)
Vileget looks for the Vileserv socket in the user's home directory ($HOME/.vilesock) by default. This can be changed by setting the VILESOCK environment variable, or by using the -s option.
If vileget is handed a directory name, it trys to get the target Vile to load the directory.pm module and popup the appropriate directory listing. This only works for the first directory mentioned on the command line, and it only works if the target Vile is configured to accept remote commands (see the -c/-C options).
You can have a lot of mindless fun with these two options. For example, you can popup and close the buffer list by repeatedly executing:
vileget -c '*'
As a nod towards security, command execution is disabled by default in Vileserv. To enable it, you can use
setv %vileserv-accept-commands true
in your .vilerc file. Note that running something like
vileget -c 'setv %vileserv-accept-commands false'
can be used to disable remote commands dynamically. Naturally, this is considered to be both a security violation *and* a feature...
Passing arbitrary commands to Vile may well produce arbitrary results. The author assumes no liability for edit sessions that have collapsed into singularities, or, as a matter of fact, for anything else.
J. Chris Coppick, 1998 (last updated: July 26, 2000)
2018-11-13 | perl v5.28.0 |