> What I am trying to convey is NNN_OPENER env var can be set to open(1) and it will override everything. NNN_OPENER IS the first preference. But as you can see, there are people like me who wants some level of customization which is done in nlay (second preference).
My point is that since one can't really do better than `open(1)` on macOS, in general at least, one should just use it instead of some quirky custom thing that's most likely inferior. Those who are determined enough could of course hack away, but for 99% of people, trying to launch Mac apps with anything other than `open` will be an inferior experience.
> If you set NNN_OPENER to open(1), does it work for you?
Yes, it works. Use `/usr/bin/open` to avoid any ambiguity.
> I am thinking of setting open(1) on OS X and xdg-open on Linux.
My thoughts as well.
I'm not kidding, you really can't do better than `open(1)`. Even for the text editor. Many people use windowed Emacs, MacVim, Sublime, Atom, VS Code, TextMate, etc. as their primary text editor, all of which are GUI. Sure they can be launched from the terminal, but why bother when users have set up the bindings.
Outside text editor realm, it makes even less sense to not use `open(1)`. You either use `open(1)` which takes care of everything (you can specify an application, but again, why override user bindings?), or use the scripting bridge, which means calling `osascript` with AppleScript code (you'll enjoy quoting for AppleScript, apparently), which basically does the same job, except it can run into all sorts of weird issues.
> is vlock available on OS X?
No. And I don't know what it is, nor its category. If I need to lock my session, I just put my screen to sleep, hence locking my console (GUI) session as well as tty sessions shown on the console session. Same for remote sessions.
> you can suggest the suitable OS X apps for the categories in nlay.
Just use `open(1)` for everything. You can't do better than that.