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

bug: State not cleared when changing cwd/workspaces #61

Open
3 tasks done
Ajaymamtora opened this issue Jun 12, 2024 · 10 comments · May be fixed by #86
Open
3 tasks done

bug: State not cleared when changing cwd/workspaces #61

Ajaymamtora opened this issue Jun 12, 2024 · 10 comments · May be fixed by #86
Labels
bug Something isn't working

Comments

@Ajaymamtora
Copy link

Did you check docs and existing issues?

  • I have read all the neoconf.nvim docs
  • I have searched the existing issues of neoconf.nvim
  • I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)

0.10 stable

Operating system/version

Macos 14.5

Describe the bug

When I change sessions with nvim persisted, the previous project config is left in memory.

I don't know how to remove the values from the previous project after switching projects

image

Steps To Reproduce

Go to project a with config file, switch to project B with no local config file, project A state retained

Expected Behavior

Api to clear state / recheck project local config

Repro

No response

@Ajaymamtora Ajaymamtora added the bug Something isn't working label Jun 12, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Jul 13, 2024
@Ajaymamtora
Copy link
Author

It also looks upwards outside the CWD and loads local config from the parent directory of the cwd.

@github-actions github-actions bot removed the stale label Jul 26, 2024
@Ajaymamtora Ajaymamtora linked a pull request Aug 24, 2024 that will close this issue
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Aug 26, 2024
@Ajaymamtora
Copy link
Author

Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Sep 26, 2024
@Ajaymamtora
Copy link
Author

.

@github-actions github-actions bot removed the stale label Sep 27, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Oct 27, 2024
@Ajaymamtora
Copy link
Author

.

@github-actions github-actions bot removed the stale label Oct 29, 2024
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label Nov 28, 2024
@Ajaymamtora
Copy link
Author

.

@github-actions github-actions bot removed the stale label Nov 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant