atom / fuzzy-finder

Find and open files quickly
MIT License
276 stars 138 forks source link

Doesn't update when new files are added #30

Open robahl opened 10 years ago

robahl commented 10 years ago

I really don't know when this is happening. But it seems that sometimes when I add files with touch file.txt the fuzzy-finder does not list it, and you have to close the window and reopen it to show it (reload window also works). Worth noting is that it appears as it should in the tree-view.

mtodd commented 10 years ago

Hitting this as well as of Atom (0.100.0).

mtodd commented 10 years ago

Err, correction, it finally found it after trying ~6 times and it just sitting there saying no matches found; it never looked like it was trying to refresh while I waited. I switched away from the app and when I switched back it seemed to perform the refresh and find the file.

hsuttong commented 9 years ago

I'm hitting this as well: Atom (1.0.2), fuzzy-finder (0.87.0). Once I opened the file from the tree view fuzzy-finder can find the file, but not before that.

shayfrendt commented 9 years ago

I've run into this frequently as well and noticed that if you wait about ~2 seconds, the fuzzy finder eventually completes reindexing and finds the new file:

On initial search: screen shot 2015-09-04 at 12 15 16 pm

Then after about 2 seconds: screen shot 2015-09-04 at 12 15 20 pm

I'm running Atom 1.0.11 and fuzzy-finder 0.88.0.

It looks like reindexing is lazily performed when the fuzzy-finder window is invoked. I wonder if it could be tweaked to reindex every time a new file is added to the filesystem?

gibsjose commented 9 years ago

+1

joowh85 commented 9 years ago

+1

nektro commented 8 years ago

+1

sirianni commented 8 years ago

atom-bug

+1.

In my case, simply waiting does not fix the problem. Newly created files are never found until the window is reloaded.

dwelle commented 8 years ago

Happens to me when checking out between branches.

gustavomanolo commented 8 years ago

I have the same problem, just like @sirianni

catsky commented 8 years ago

+1 on v1.7.4

surajreddy commented 8 years ago

This is happening to me as well. My fuzzy search does not update with newly added files, even if they are added and saved with Atom. Version: 1.8.0

Quitting Atom and Reopening it makes the file show up.

morhook commented 8 years ago

You can press CTRL-ALT-R (On PC), or for MacOSX it might be CTRL-ALT-CMD-I

askehansen commented 8 years ago

+1

adamstegman commented 8 years ago

In my case, this started happening after I upgraded to Atom 1.8.0 (on OS X 10.11). The file finder indicates that reindexing is occurring, but it never finishes and no new files are added until I quit and re-open the project.

EDIT: A week later, I was able to update to 1.9.6 and this plugin seems to work with new files again.

guidorice commented 8 years ago

I have noticed this problem with Atom 1.9.2 on OSX. I am using the advanced-open-file package to create files. Although I think I have noticed a similar problem with create new by Cmd-N then Cmd-S to save. It seems that the fuzzy-finder is not rebuilding it's index, or if it is, unpredictably.

rumpelsepp commented 7 years ago

Running into this every time I add new files with the tree view using alt + \ + a. I also, ran into the issue that renamed files are not recognized; instead fuzzy finders opens the no more existing files.

stwr667 commented 7 years ago

Yep, it happens to me too all the time when changing branches. +1 for a fix.

Gkupce commented 7 years ago

Atom 1.18.0 Fuzzy finder 1.5.8 currently has the problem.

Could we get a Force index refresh option so that at least we don't need to reload the editor?

nicnilov commented 6 years ago

An externally created file shows up in the treeview but is not available in the fuzzy finder window.

Atom 1.22.1 fuzzy-finder 1.6.1

theworkerant commented 6 years ago

+1

Any updates on this bug? It's been around for nearly 4 years???

winstliu commented 6 years ago

@theworkerant commenting on the age of the bug won't help - if there's been any updates regarding the status of this bug we'll announce them here. If you'd like to see this fixed sooner rather than later we would definitely appreciate a well-written PR!