Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A autojump
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 158
    • Issues 158
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • William Ting
  • autojump
  • Issues
  • #294
Closed
Open
Issue created Jun 25, 2014 by Administrator@rootContributor

`jc` does not limit results to subdirectories (via `match_fuzzy`)

Created by: blueyed

With jc foo in /home/daniel/.autojump, /tmp/t/C:\Users/foo was returned.

This appears to be caused by match_fuzzy, which uses only the last needle for fuzzy matching.

I see two problems here:

  1. jc should trigger a mode, where entries are filtered based on the path prefix (pwd) explicitly, i.e. find results and apply a path based filter.
  2. match_fuzzy should not work on the last needle only.

I could imagine looping over all needles in match_fuzzy.

This would change the documented behavior though, since Entry(path="/moo/foo/baz", weight=10), would not get matched anymore for needles=['foo', 'bar'].

I have started writing some tests for it, but would like to get some feedback before carrying on.

Assignee
Assign to
Time tracking