You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# ~/.profile: executed by the command interpreter for login shells.# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login# exists.# see /usr/share/doc/bash/examples/startup-files for examples.# the files are located in the bash-doc package.# the default umask is set in /etc/profile; for setting the umask# for ssh logins, install and configure the libpam-umask package.#umask 022# if running bashif [ -n"$BASH_VERSION" ];then# include .bashrc if it existsif [ -f"$HOME/.bashrc" ];then."$HOME/.bashrc"fifi# set PATH so it includes user's private bin if it existsif [ -d"$HOME/bin" ] ;then
PATH="$HOME/bin:$PATH"fi# set PATH so it includes user's private bin if it existsif [ -d"$HOME/.local/bin" ] ;then
PATH="$HOME/.local/bin:$PATH"fi
meaning that if .bash_profile exist then the bins are not correctly instanciated (and the coloring and other prettifying stuff)
The text was updated successfully, but these errors were encountered:
In https://sepal-ui.readthedocs.io/en/latest/start/contribute.html#env-for-planet-components we suggest to create a .bash_profile file to the developers of the lib. It should work on local computers but will break SEPAL instances initialization.
Looking at the
.profile
in my account I found:meaning that if
.bash_profile
exist then the bins are not correctly instanciated (and the coloring and other prettifying stuff)The text was updated successfully, but these errors were encountered: