Quote:
Originally Posted by nikev
I eventually got the program to work by authorizing it in the security preference pane, but the executable is still not found and one has to direct the terminal to it manually via ./kepubify.
Is this the expected behaviour?
|
Unlike Windows, the current folder that you're in is intentionally not in the path that is searched for executables (You can see the search path with
echo $PATH) in Unix derived OSes (including MacOS) because that is a potential security risk, so typing
./ before a local executable is perfectly normal and expected.