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

suggest: step-by-step processing #35

Closed
zhenyangze opened this issue Jan 12, 2017 · 5 comments
Closed

suggest: step-by-step processing #35

zhenyangze opened this issue Jan 12, 2017 · 5 comments

Comments

@zhenyangze
Copy link

hi. bother you again.

when i open a large project,then i open leaderF,it will take a long time to search files.and i have to wait it until finish finding all.

can it do some changes?

  1. search the recent changed dirs first(not all) and then show result.
  2. background process.
  3. listen for directory changes.

thx!

@Yggdroot
Copy link
Owner

For 1, I think it's difficult to implement.
For 2, I will add async support later on.
For 3, watchdog?

@zhenyangze
Copy link
Author

thx.
look forward to your work. m( _ _ )m
For 3, it aim to auto refresh.
And for 1, i will try to implemente it in one way, although not very familiar.
[]( ̄▽ ̄)*

@roxma
Copy link

roxma commented Jun 27, 2017

listen for directory changes.

Just curious, why you need this feature?

As a regular use case, you trigger LeaderF, type and find the file you want as soon as possible, then open the file and close LeaderF. I don't see it being useful in this use case.

Yggdroot added a commit that referenced this issue Jul 4, 2017
@Yggdroot
Copy link
Owner

Yggdroot commented Jul 5, 2017

@zhenyangze Now you can use LeaderF to search a file asynchronously, and you don't have to wait for its finishing the index.
I think this issue can be closed.

@Yggdroot Yggdroot closed this as completed Jul 9, 2017
@zhenyangze
Copy link
Author

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants