VILEGET(1)

okay so bestie, you opened up vileget(1) and honestly? iconic choice. let's get into it 💅

---

✨ NAME ✨

vileget — passes file edit requests to a Vile editor that's running Vileserv. that's the whole job, and she does it slayfully 🦋

---

🌸 SYNOPSIS 🌸

vileget [-n] [-d] [-w] [-s socket-path] [-c command] [-C command] [file ...]

---

💖 DESCRIPTION 💖

okay so here's the tea: vileget lets you load files into an already-running instance of Vile or XVile. the editor needs to have already loaded and started the Vileserv perl module — check the Vileserv documentation if you want the full deets on that part.

by default (like, if you don't tell her otherwise), if vileget can't connect to a running instance of the editor, she will try to start a new one. lowkey important: that only works correctly if you've configured Vile to start Vileserv automatically. and when she goes hunting for a binary, vileget tries to find an XVile binary first, then looks for a Vile binary. priorities, honestly 👑

now, where is the socket at? vileget looks for the Vileserv socket in your home directory — $HOME/.vilesock — by default. you can change that by setting the VILESOCK environment variable, or by using the -s option. your call, your vibe.

directory moment: if vileget is handed a directory name, she tries to get the target Vile to load the directory.pm module and popup the appropriate directory listing. caveat time though, because there's always a caveat: 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 (peep the -c/-C options for that).

---

🎀 COMMAND-LINE OPTIONS 🎀

• -d — with this option, vileget will change the current working directory of the running Vile to be the directory in which vileget is being run, in addition to loading any requested files. two things at once, she's multitasking 💅
• -n — this tells vileget NOT to try starting a new instance of Vile if necessary. so if she can't connect to a running Vile, she just dies with a connection error instead. no backup plan, no rescue mission, periodt 😭
• -w — vileget waits for the given file(s) to be written by Vile before exiting. patient queen behavior fr fr.
• -s socket-path — tells vileget to use the socket given by socket-path. this overrides the default and the environment variable VILESOCK. she said "i make the rules now."
• -c command
• -C command — the -c and -C options can be used to pass arbitrary Vile commands to a running instance of Vile. these can be used at the same time that file edits are being requested, or without giving any files at all. when file arguments are used, the -c option can be used to execute a Vile command before the requested files are loaded. the -C option is used to execute a Vile command after the requested files are loaded. if no file arguments are given, then -c and -C are basically the same, except that -c has precedence. these options are non-repeatable, so you can only execute two Vile commands per invocation of vileget. of course, there are always procedures... ✨

🦋 the -c / -C extended lore 🦋

you can have a lot of mindless fun with these two options, ngl. 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... 💀✨ the duality.

⚠️ 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. fr fr, she said what she said 🙈

---

🌈 SEE ALSO 🌈

• vileserv(3)
• vile(1)

---

👑 AUTHOR 👑

J. Chris Coppick, 1998 (last updated: July 26, 2000)

---

and that's the whole page bestie!! this one shipped with perl v5.40.0, dated 2025-02-01 — go forth and load those files into your editor, you absolute main character 🫶💜