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.

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

Reorganize how clink settings are loaded #794

Merged
merged 2 commits into from
Feb 1, 2016

Conversation

jankatins
Copy link
Contributor

4bfdf04 moved all clink config files
to vendor/ and therefore the files in config/ were not used and .history
was also moved to vendor/.

The new arrangement uses --script to load our own clink.lua file which in
turn as the first thing loads the original clink.lua file. The user defined
files are again in config/. As clink regenerates these files, if they are not
present, this also means that we don't need to include the settings file
in the git repo and therefore don't overwrite it on updates.

Closes: #793

@jankatins
Copy link
Contributor Author

Just a note: the current setup is broken as it places the clink files (mainly history and settings) in vendor\ and not in config\ since 4bfdf04. IMO cmder should not be release with that, either that should be reverted or this PR (or something similar) should be used.

4bfdf04 moved all clink config files
to vendor/ and therefore the files in config/ were not used and .history
was also moved to vendor/.

The new arrangement uses `--script` to load our own clink.lua file which in
turn as the first thing loads the original clink.lua file. The user defined
files are again in config/. As clink regenerates these files, if they are not
present, this also means that we don't need to include the settings file
in the git repo and therefore don't overwrite it on updates.
Introduce a header like in the rest of the scripts that this file
is overwritten on updates and should not be modified.
@jankatins
Copy link
Contributor Author

ping?

@MartiUK
Copy link
Member

MartiUK commented Jan 26, 2016

I need to figure this out, a lot of contradicting PRs and changes.

@Stanzilla
Copy link
Member

@MartiUK why not just merge this? Other PRs have to be rebased on that but this at least fixes the problem, no?

@MartiUK
Copy link
Member

MartiUK commented Feb 1, 2016

Fair enough

MartiUK added a commit that referenced this pull request Feb 1, 2016
Reorganize how clink settings are loaded
@MartiUK MartiUK merged commit 261b8bf into cmderdev:development Feb 1, 2016
@jankatins jankatins mentioned this pull request Feb 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants