Skip to content

Ignore bazel-* directories outside the root directory #4037

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

Merged
merged 1 commit into from
May 2, 2023

Conversation

GregOwen
Copy link
Contributor

@GregOwen GregOwen commented May 1, 2023

Why is this change necessary?

This previous PR added a default to ignore bazel-* directories that were children of the project root. However, the regex used does not ignore bazel-* directories elsewhere in the project repo. This can occur when a git submodule uses bazel.

What does this change do?

Change the default value of lsp-file-watch-ignored-directories to ignore bazel-* directories wherever they are found in the repo, not just the root directory.

How is this change tested?

I tested it locally by adding the new regex using the approach described here and I no longer see LSP warning that the number of file watches has exceeded its limit.

# Why is this change necessary?

[This previous PR](emacs-lsp#3768) added a default to ignore `bazel-*` directories that were children of the project root. However, the regex used does not ignore `bazel-*` directories elsewhere in the project repo. This can occur when a git submodule uses bazel.

# What does this change do?

Change the default value of `lsp-file-watch-ignored-directories` to ignore `bazel-*` directories wherever they are found in the repo, not just the root directory.

# How is this change tested?

I tested it locally by adding the new regex using the approach described [here](https://emacs-lsp.github.io/lsp-mode/page/file-watchers/) and I no longer see LSP warning that the number of file watches has exceeded its limit.
@GregOwen
Copy link
Contributor Author

GregOwen commented May 1, 2023

@jcs090218 I'm not sure how to interpret the error I'm getting in the failing CI/test:

eask clean all
Can't read whole string
mingw32-make: *** [makefile:59: clean] Error 1
Error: Process completed with exit code 1.

I also don't have access to a Windows machine. Any suggestions on how to proceed?

@jcs090218
Copy link
Member

I'm not sure how to interpret the error I'm getting in the failing CI/test:

Don't worry about that! There is an incompatible error in the upstream Emacs' Windows snapshot.

@GregOwen
Copy link
Contributor Author

GregOwen commented May 1, 2023

What's expected from me at this point? Will I need to rebase once the upstream snapshot is fixed?

@jcs090218
Copy link
Member

What's expected from me at this point? Will I need to rebase once the upstream snapshot is fixed?

Nope, you are all set! We regularly wait a day or two for other people to review it. :)

@GregOwen
Copy link
Contributor Author

GregOwen commented May 1, 2023

Awesome, thanks for the fast response!

@jcs090218 jcs090218 added the bug label May 1, 2023
@yyoncho yyoncho merged commit 3c99a2e into emacs-lsp:master May 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants