So I was playing around with 4coder under Ubuntu 16.04 today, and noticed that it would fail to start if my command line was not set to the directory where I placed 4coder. I made a little fix to this by creating a bash file that I called 4coder.sh:


Hope this helps other people as well as it did for me!

This should be fixed in the next version.

The fixed 4ed will dlopen the 4ed_app.so and 4coder_custom.so from the same directory that 4ed is in (unless you specify a separate 4coder_custom.so path with -d / -D)

That is really great to know!