Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

On a fresh install, the link step for ~/.config clobbers all of the config #22

Closed
sinewalker opened this issue May 30, 2017 · 3 comments
Closed

On a fresh install, the link step for ~/.config clobbers all of the config #22

sinewalker opened this issue May 30, 2017 · 3 comments
Labels
bug
Milestone
1.1-SUSE

Comments

@sinewalker
Copy link
Owner

I need to rethink how this works, because when I did a fresh install of SUSE and then dotfiles, it broke all the things.

Workaround: recover the original ~/.config from the backup that dotfiles makes, and then manually link in the midnight commander stuff.
@sinewalker sinewalker added the bug label May 30, 2017
@sinewalker sinewalker added this to the 1.1 SUSE milestone May 30, 2017
@sinewalker
Copy link
Owner Author

some of this could be addressed by Issue #16 also

@sinewalker sinewalker mentioned this issue Oct 17, 2017
Closed
@sinewalker
Copy link
Owner Author

sinewalker commented Oct 17, 2017 •
edited
Loading

See Cowboys' commit plus his fixup

@sinewalker sinewalker mentioned this issue Oct 30, 2017
Closed
sinewalker added a commit that referenced this issue Oct 30, 2017
@sinewalker
link config files (from Cowboy)
52e3d58 
I've also renamed the conf directory to misc to avoid confusion between config
and conf.

Issue #22
@sinewalker
Copy link
Owner Author

fixed with commit 52e3d58

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.1-SUSE
Development

No branches or pull requests
1 participant
@sinewalker