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
Right now, I have a patch (wip) to implement XDG_CONFIG_HOME on an opt-in basis. That is, XDG_CONFIG_HOME is used if and only if.jupyter does not exist. This minimizes breakage by ensuring that the change only affects:
New users with XDG_CONFIG_HOME set,
Existing users with XDG_CONFIG_HOME set who explicitly migrate,
Existing users with XDG_CONFIG_HOME set who delete their .jupyter directory for any other reason.
The solution to cases 1/3 is documentation, and I'm willing to update the docs in jupyter/jupyter, and any other locations.
The question is: should the Linux default get set to .config, when it isn't set? This is a more significant change in behavior, but it parallels the existing default of .local/share.
The text was updated successfully, but these errors were encountered:
Addresses #17
- Adds `JUPYTER_CONFIG_DIR` pointing to `XDG_CONFIG_HOME` to `.zshenv`
- Documents situation around IPython
- NOte: out-of-the-box XDG support is still an open issue - see:
jupyter/jupyter_core#185
After reloading the shell (i.e. once `JUPYTER_CONFIG_DIR` is in scope),
one can simply move/rename `~/.jupyter` to `JUPYTER_CONFIG_DIR`.
Right now, I have a patch (wip) to implement
XDG_CONFIG_HOME
on an opt-in basis. That is,XDG_CONFIG_HOME
is used if and only if.jupyter
does not exist. This minimizes breakage by ensuring that the change only affects:XDG_CONFIG_HOME
set,XDG_CONFIG_HOME
set who explicitly migrate,XDG_CONFIG_HOME
set who delete their.jupyter
directory for any other reason.The solution to cases 1/3 is documentation, and I'm willing to update the docs in jupyter/jupyter, and any other locations.
The question is: should the Linux default get set to
.config
, when it isn't set? This is a more significant change in behavior, but it parallels the existing default of.local/share
.The text was updated successfully, but these errors were encountered: