Add option to set search scope as the first parent dir containing a VCS settings directory about dumb-jump HOT 3 CLOSED

This is possible using the new ".dumbjumpignore" files. have a look at 12c315f for more information.

from dumb-jump.

Sorry, let me clarify with another example:

code/                     # `dumb-jump-default-project`
├── Client A              
│   └── project-1/        # active project dir
│       ├── .git/         # VCS dir identifying *expected* project dir
│       ├── active.py     # current buffer location
│       └── defs.py       # location of target definition 'foobar'
└── Client B
    └── project-2/        # second project dir
        ├── .git/         # VS dir identifying project dir
        └── more-defs.py  # contains a second definition of 'foobar'

It would seem from your description that this is already the behaviour, that when jumping to foobar in defs.py from active.py one should stay within code/Client A/project-1, but I'm occasionally jumping to project-2/more-defs.py.

I'll keep an eye on the behaviour and raise a separate bug if I can provide replication steps.

from dumb-jump.

Thanks for the message. Just to confirm I understand what you're saying. This proposed setting, when enabled, would use the shallowest VCS directory instead of the deepest? So right now as it walks up the tree, it stops and uses the first VCS directory it finds. In other words, you're saying it should keep going up until it finds dump-jump-default-project and use the last VCS directory it found?

from dumb-jump.