Andrew -- I think this is a good idea, but I think this is probably a shell spec issue because I don't want competing, incompatible implementations.
A few other issues: I think there is a persistence issue (similar to shell variables) so that the change could be installed and survive a reboot. I also think there can be a simple shell command that manages extensions (so that they can be installed by a script) Tim -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Andrew Fish via Groups.Io Sent: Monday, February 10, 2020 12:12 PM To: [email protected] Subject: [edk2-devel] Shell feature? I wanted to start a conversation on the mailing list prior to writing up a BZ, to make sure I'm not missing anything, or in case there is a better way to implement this. I was thinking it would be good to have a Shell API that lets you associate a file type with an internal or external shell command. The Idea would be to pre-pend the internal/external shell command to the file name and also pass the arguments. So this: fs0:>dump.py 1 2 3 Becomes: fs0:>python3.efi dump.py 1 2 3 Basically you just need an API like: ShellAddScriptingLanguage (L".py", L"python3.efi"); Seems like this could just plug into the Shell via a ShellExecute(). So for example you could make Python a UEFI Shell command via a library and that library constructor could also teach the shell that a .py file could be an executable? Thanks, Andrew Fish -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#54231): https://edk2.groups.io/g/devel/message/54231 Mute This Topic: https://groups.io/mt/71147932/21656 Group Owner: [email protected] Unsubscribe: https://edk2.groups.io/g/devel/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
