Download Latest Version
v0.4 -- New flags, help, new tcell.zip (161.7 kB)
Get an email when there's a new version of up
| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| up-openbsd | 2018-10-26 | 4.4 MB | |
| up | 2018-10-26 | 4.3 MB | |
| up-darwin | 2018-10-26 | 4.3 MB | |
| up-dragonfly | 2018-10-26 | 4.3 MB | |
| up-freebsd | 2018-10-26 | 4.3 MB | |
| up-netbsd | 2018-10-26 | 4.3 MB | |
| README.md | 2018-10-26 | 949 Bytes | |
| v0.3 -- Allow custom_non-bash shells (_engines_).tar.gz | 2018-10-26 | 156.2 kB | |
| v0.3 -- Allow custom_non-bash shells (_engines_).zip | 2018-10-26 | 156.7 kB | |
| Totals: 9 Items | 26.2 MB | 1 | |
This release by default loads user's login shell, as specified in the SHELL environment variable (instead of always using bash, as was done previously). This feature can also be used to change the shell/engine used by up, by changing the contents of the SHELL variable. To be compatible with up, a shell must support two ways of being called:
$SHELL -c "$COMMAND"— this is used by up when evaluating the command entered by user,$SHELL $FILENAME— this is used in upN.sh scripts saved after exiting up.
If a shell/engine you want to use with up doesn't support such ways of being called, you can create a wrapper script to translate those into options appropriate for your shell. This can be used to make up work with engines such as lua or ghci.
To change a shell used by up, change the value of the SHELL environment variable. For example, in bash, you could try:
lshw |& SHELL=python up
