To integrate with your file manager...

To run a command, the directory containing it needs to be listed in an environment variable called PATH - this is how the system finds commands. E.g. if you install a Python package with 'pip install --user', the commands will go into /home/username/.local/bin/ , which isn't on PATH by default.

To get around this, you can use a file in their home directory to change PATH, with a line like this:

export PATH=$HOME/.local/bin:$PATH

For nbopen, you need to make sure that this is in the file '/home/username/.profile' . People often put it in a file like '/home/username/.bashrc' , which works for commands in the terminal, but doesn't work for running commands when you launch applications graphically, like by double clicking on a file.

I should really improve nbopen so that this isn't necessary.

On 23 November 2017 at 09:20, Mattia Podio notifications@github.com wrote:

Hi all I'm new in Linux, and a beginner i Python, so I'm not confident with installing programs via command line.. I followed your instructions in the README, but I can't undertand the last statement:

Ensure that nbopen is on the profile path (not just terminal, e.g. .profile not .bashrc)

I mean: where should I check it, and, just in case, what should I do? Thank you

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/takluyver/nbopen/issues/48, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUA9SPwLW4EjkhGEOe9vwgrxjJ_rQr3ks5s5TjTgaJpZM4QodC6 .

takluyver / nbopen

To integrate with your file manager... #48