public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tim Lewis" <tim.lewis@insyde.com>
To: <devel@edk2.groups.io>, <afish@apple.com>
Subject: Re: [edk2-devel] Shell feature?
Date: Tue, 11 Feb 2020 12:28:25 -0800	[thread overview]
Message-ID: <003b01d5e119$d2806700$77813500$@insyde.com> (raw)
In-Reply-To: <AC55D41C-B616-4BAD-8057-C8E906D61932@apple.com>

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: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Andrew Fish
via Groups.Io
Sent: Monday, February 10, 2020 12:12 PM
To: devel@edk2.groups.io
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




  reply	other threads:[~2020-02-11 20:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 20:11 Shell feature? Andrew Fish
2020-02-11 20:28 ` Tim Lewis [this message]
2020-02-11 21:30   ` [edk2-devel] " Jim Dailey
2020-02-12  1:30     ` Carsey, Jaben
2020-02-12  2:08       ` Andrew Fish
2020-02-12  6:04         ` Carsey, Jaben
     [not found]     ` <8A8C80EA-FDD7-4AF6-896C-7A7263446D62@apple.com>
2020-02-15  1:30       ` Andrew Fish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='003b01d5e119$d2806700$77813500$@insyde.com' \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox