My usual workflow involves starting SlickEdit from a bash shell prompt inside a macOS terminal.
When I use /Applications/SlickEditPro2017.app/Contents/MacOS/vs
to do this and SlickEdit is not already running, the bash shell is stuck in a waiting state until I quit SlickEdit because it is launched as a foreground process.
When I use open -a SlickEditPro2017.app
to do this, I get the desired behavior. SlickEdit is launched and control returns to the bash shell. Unfortunately, using this method does not allow me start SlickEdit with a new file that does not exist.
I would like to see /Applications/SlickEditPro2017.app/Contents/MacOS/vs
changed so that it launches SlickEdit as a background process and returns control to the bash prompt. Other editors like Visual Studio Code offer a command line launch command that do exactly this.