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

solargraph is triggered by changes of log and cache-files #15

Open
dwarfi09 opened this issue May 9, 2019 · 2 comments
Open

solargraph is triggered by changes of log and cache-files #15

dwarfi09 opened this issue May 9, 2019 · 2 comments

Comments

@dwarfi09
Copy link

dwarfi09 commented May 9, 2019

Every change of every file in my project's directory notifies solargraph of a file-change and causes a new indexing-process.

So in my rails-projects every page-reload triggers a lot of reindexing-processes, because a lot of files change while handling the request (multiple changes in log-file, cache-files etc.). This slows atom down to be unusable.

I created a .solargraph.yml in the project's directory, but this seems to be ignored.

I'm using rbenv for managing ruby-versions.

@castwide
Copy link
Owner

castwide commented May 9, 2019

The language server depends on the client to monitor the filesystem and report changes to watched files. In VS Code, the client can minimize server notifications with a filter on the filesystem watcher. I'm not sure if there's a similar mechanism in Atom. I'll have to research it.

@dwarfi09
Copy link
Author

dwarfi09 commented May 9, 2019

I understand, thank you.

Switching the "File System Watcher" from "Native operating system APIs" to "Experimental filesystem watching library" in the core-settings seems to do the trick.

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

No branches or pull requests

2 participants