The intent is to have a shell to use command line applications that are installed inside the container, like git or gcc and have access to my documents with these tools and have access to any results produced by these tools from the regular touch system.
E.g., consider the following:
libertine-launch -i vivid bash
cd Documents
git clone user@server:project ./project
now open Libre office and open that document that's in ~/Documents/project/foo.odt
work on it
export it as a pdf
now switch to dekko and write that email where you attach foo.pdf
I thought that libertine-launch IS the proposed way how a regular user would get command-line access, because
a) the exec command is hidden and
b) it doesn't mount things like ~/Documents
The intent is to have a shell to use command line applications that are installed inside the container, like git or gcc and have access to my documents with these tools and have access to any results produced by these tools from the regular touch system.
E.g., consider the following:
libertine-launch -i vivid bash
cd Documents
git clone user@server:project ./project
now open Libre office and open that document that's in ~/Documents/ project/ foo.odt
work on it
export it as a pdf
now switch to dekko and write that email where you attach foo.pdf
I thought that libertine-launch IS the proposed way how a regular user would get command-line access, because
a) the exec command is hidden and
b) it doesn't mount things like ~/Documents