When calling enlightenment_filemanager /usr/bin the filemanager gets opened and shows me the content of /usr/bin.
When calling enlightenment_filemanager /usr/bin/xterm I would expect that it does the same, but selects the file xterm in that directory.
However what it does is executing the executable xterm. If a specify a non-executable file, e.g. /etc/fstab then (in my case) a terminology window with vim gets opened for the the specified file.
This is a very annoying and unexpected behaviour.
I assume that the same call is used internally in enlightenment_filemanager when opening a file (or directory), but I think there should obviously be a difference when double clicking on a file or directory inside efm and when calling efm with a file as argument.
I have tried other filemanagers and found that some have the same strange behaviour (pcmanfm, thunar), but some others behave like I expect (nautilus, double commander, worker). I found the behaviour of dolphin even more strange. It opens the filemanager in the given files directory and _additionally_ calls xdg-open on the given file.
But I think selecting the given file (if a file, not a directory) is the sanes behaviour. Especially when the given file is an executable!