Git Product home page Git Product logo

Comments (3)

tomrijndorp avatar tomrijndorp commented on August 14, 2024

Hi @juzerzarif, thanks for reporting! This was a tricky one. I only managed to reproduce this for the case where "some-ignored-dir" is a relative path. When the path is absolute, I don't have problems. Is this the same for you?

I'm wondering if the right "fix" for this, is to warn users that additionalSearchLocations should be an absolute path. FiF works slightly differently when there are multiple roots in the workspace, and this is roughly similar.

Honestly I'm having a hard time remembering why I even added to option to search additional locations, as opposed to just expecting users to add another folder to their workspace, so I'm also considering just ripping that option out at this point... Perhaps you could tell me for your case why using this option is preferable over adding a folder to the workspace? Thank you!

(And in the meantime, your problem can hopefully be solved by specifying the full path but I understand this is not as nice)

from vscode-finditfaster.

juzerzarif avatar juzerzarif commented on August 14, 2024

My use case (might not be that common) is that I have a directory that a build tool will output that's gitignored but sometimes when I need to troubleshoot failures for that build tool I need to look through files in that directory so I've added it as an additional search location for FIF

from vscode-finditfaster.

juzerzarif avatar juzerzarif commented on August 14, 2024

One suggestion that I had was maybe registering a key binding with fzf to toggle including ignored files in the search results but I'm not sure how FIF determines which files to include/exclude as search options or if FIF even has a concept of ignored files via stuff like .gitignore internally

Edit: Just saw the useGitIgnoreExcludes and useWorkspaceSearchExcludes settings so FIF definitely knows what files are being ignored. For my use case I can just switch these off/on depending on whether I'm troubleshooting a failure or not. Though a key bind in fzf might be nice still if you think it makes sense.

Edit 2: Nvm, setting useGitIgnoreExcludes and useWorkspaceSearchExcludes to false seems to result in no search options...?

from vscode-finditfaster.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.