Autocomplete package names

[jacques-]

At startup you could scan all installed packages and then autocomplete package names, bit of a pain re-typing them all the time.

Perhaps provide a way to create aliases for package names so I could do:

p = com.mwr.mercury.agent
app.activity.info -a p

would save loads of time...

[metall0id]

Maybe we can have an implementation where you can set your own "environmental variables" e.g.

mercury> set p="com.mwr.droidhg.agent"
mercury> run app.activity.info -a $p

This will also be useful to make a cleaner implementation of the dirty replace() used for $BB in shell.py

I was also looking to provide a helper module for SQLITE3 that allows you to type $sqlite in a shell and have that binary referenced like busybox. Implementing this functionality would allow it to be cleanly integrated without adding another dirty replace() for it

[metall0id]

Or something that conforms more to the rest of the Mercury UI like:

mercury> set p com.mwr.droidhg.agent

and then have the following command to remove it:

mercury> unset p

[ghost]

I think this is two separate features. I like the idea of being able to set and unset variables (maybe with an alias to export to keep the linux folks happy), but auto-completing package names would also be very handy.

[metall0id]

Agreed, two separate features. Maybe we can keep these variables in the .mercury_config and when running the setup modules like busybox then it registers the appropriate variable automatically

[metall0id]

The use of these variables may not be the best idea. Having uploaded binaries like busybox directly on the path for each Mercury shell as described in #81 seems like a better way to go.