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

feature: Specify config path via environment variable #42

Open
1 task done
musjj opened this issue Oct 2, 2023 · 0 comments
Open
1 task done

feature: Specify config path via environment variable #42

musjj opened this issue Oct 2, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@musjj
Copy link

musjj commented Oct 2, 2023

Did you check the docs?

  • I have read all the neoconf.nvim docs

Is your feature request related to a problem? Please describe.

Sometimes you want to generate project-specific configuration containing data that can't be statically baked.

For example, with Nix you can create a shell environment that automatically pull dependencies for the project. But sometimes, you need to pass these dependencies to the LSP configuration. Since the data is dynamic and can't be known beforehand, you can't just hardcode it in a .neoconf.json

Describe the solution you'd like

Being able to specify the absolute path to the config file via an env var (e.g. NEOCONF_PATH) will allow the user to dynamically generate a config file and pass the path to neoconf via the environment variable.

Describe alternatives you've considered

The only other alternative is to manually create the config file and adjust them regularly.

Additional context

No response

@musjj musjj added the enhancement New feature or request label Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant