how does ondemand for command line utilities work?

[christophed]

I may not represent the typical use case (OnDemand extensions in mostly CLI TinyCore) and it's a small effort for me to edit the wrapper scripts if I know I can't depend on them working automagically in my context.

If creating the icons (which I can imagine is quite hard for a lot of tools) is part of the problem maybe part of the solution could be to make one 'generic' icon for all (non specific) CLI tools?

I hope I don't offend anyone by making these remarks since I'm very new to TinyCore and how it works. It's been a superb distro so far!

[roberts]

They could and will work automagically. The infastructure is provided and or will be adjusted. FWIW so too is a generic icon. See /usr/share/pixmaps/core.png. However if an extension maker deems not to use such or only upon request, e.g. mc, then so be it. It will not be for lack of base support.

Your question has brought to light valuable insight from a user's perspective. I hold no hard feelings towards anyone. It is an interesting topic discussion which will make Tiny Core only more capable going forward.

[curaga]

I recall that previously when creating ondemand entries one was asked for the binary name, if desired. Perhaps that functionality could be brought back for clí extensions in some form.

[roberts]

That too, like the "run in xterm" would require that the end user know in advance such details. Whereas the extension maker would obviously know. Many CLI extensions would benefit from having at least a menu item with cliorx. Of course there would still be some CLI extensions where it would not make sense, specifcally those that require dynamic run time command line arguments.