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
All files should be added to the repo as-is, since the initial configuration is not always a known state. If the installation process modifies files, it can get very confusing and hard to recover, even if it's just one line added somewhere.
The text was updated successfully, but these errors were encountered:
I'm not sure how attached to the .bashrc_load idea, but I'd be fine with it disappearing entirely and leaving it up to the user to put dfm on their path (or not), as there are too many variables.
I wouldn't classify this as a bug, but I do think that it'd be a good idea: the dfm docs could ask the user to add ~/bin to $PATH, rather than have dfm modify .bashrc. It'd simplify things and be slightly safer / more conservative.
All files should be added to the repo as-is, since the initial configuration is not always a known state. If the installation process modifies files, it can get very confusing and hard to recover, even if it's just one line added somewhere.
The text was updated successfully, but these errors were encountered: