2da4cc4634
This makes 'toolbox enter' similar to 'toolbox run $SHELL'. The 'run' command is meant to spawn arbitrary binaries present inside the toolbox container. Therefore it doesn't make sense for it to fall back to /bin/bash, like it does for 'enter' if $SHELL is absent. It's expected that users might use 'run' to create ad-hoc *.desktop files. That's why it neither offers to create nor falls back to an existing container like 'enter' does, because such interactions can't happen when used in a *.desktop file. It's also a more advanced command that new users are less likely to be interested in. Hence, this shouldn't affect usability. Some changes by Debarshi Ray. https://github.com/debarshiray/toolbox/pull/76 |
||
|---|---|---|
| .. | ||
| meson.build | ||
| toolbox-create.1.md | ||
| toolbox-enter.1.md | ||
| toolbox-list.1.md | ||
| toolbox-rm.1.md | ||
| toolbox-rmi.1.md | ||
| toolbox-run.1.md | ||
| toolbox.1.md | ||