Re: Further to the perl/vileget/vileserv saga

[Chris Green]

On Mon, Feb 08, 2021 at 01:46:11PM -0600, J. Chris Coppick wrote:
>    On Mon, Feb 8, 2021 at 1:25 PM Chris Green <[1]cl@isbd.net> wrote:
[snip my ramble]
> 
>    All I can tell you for sure at this point is that my memory is no doubt
>    worse than yours.  :)
>    Do not think the "use Vileserv" replaces those other lines.  It does
>    ring a bell.  I'd have to dig up the docs and code to check what was
>    required for what.
>    The register commands just set it up so you can stop/start the vileserv
>    process from the vilerc or the Vile command prompt, e.g. ':startserv'
>    or ':stopserv'.   The startserv cmd is then used to start the vileserv
>    process.  And of course the exit hook setup is meant to not leave the
>    vileserv process running without an active vile.   This was all
>    intended primary for use with Xvile of course.   In theory you would
>    login, which would launch your X window environment, which would launch
>    Xvile, and then you would use vileget to load files into the running
>    xvile either from the command line or even from a file manager.
>    (Remember X windows?   I can't seem to find it on my mac.   There's an
>    Xcode but it doesn't appear to be the same thing... ha ha.)
>    Regarding your unexpected vileget, have you checked your shell
>    aliases?   Perhaps you have an old 'alias vi=vileget' or similar
>    lurking somewhere?
>    Do not recall for sure but very possible that vileget might hang for a
>    bit if there is no vileserv process running.  Might explain the vileget
>    taking a while to die.
>    Hope this helps in some small, vague way.  :)

Yes, thanks Chris, it tells me why the snippet of perl in my .vilerc
is the way it is.  It is all quite a while ago that this was really
important! :-)

-- 
Chris Green