User may call wrong Chicken binaries while cenv is active #3
Description
While an environment is active, the user needs to call Chicken binaries with their renamed names. In Arch Linux, this would be chicken-csi, which is probably as expected.
However, if you renamed csi to csi5 to have a parallel Chicken 4 and 5 installation, calling cexec csi might find your Chicken 4 install. That's because cenv simply updates PATH to find your Chicken binaries. Chicken binaries do know which names to use when calling out to other binaries, so internal calls are not a problem.
The only fix for this would be to standardize the naming and either symlink them into bin/ or alias them, similar to Python. And it makes sense to me to have csi instead of csi5 inside a virtual environment. That could cause unexpected behavior in Arch Linux though, as you might not want a csi command at all.