-
Notifications
You must be signed in to change notification settings - Fork 196
Displaying deleted files #634
Comments
It may have to do with the file still being open in a tab (see atom/tabs#160)
The first tab is the reference to the delete file. The second tab is what opened up after searching and clicking on the result. |
@anderoonies can you test if this is (as well) due to |
gladly, i'll update as soon as i get back to my machine and have a chance update: looks like |
atom/node-pathwatcher#106 has been merged, which may solve this problem. @adambuczynski can you ensure this is working properly with the latest version of |
@acontreras89 so this is partially fixed, I guess it depends on how find and replace should work. When I follow the above steps now, the tab of the deleted file is properly removed, and when I close the find and replace panel and open it again to search, the deleted file does not show up. However, when you leave the panel open and try searching for the same term again, it does not perform a new search, and your previous result (including the deleted file) still shows up. This may or may not be the intended behaviour of find and replace, so I can't classify it as an outright bug. But when you click on the deleted file in the search results, the same happens, e.g. an empty tab is opened with the same file name, but pointing to a non existing file. After you do that, the result disappears from the find and replace search results. |
Personally, I think it would be best if the corresponding entries could be removed from the find-in-project view. |
I created a pull request to address this. Will wait for feedback before working any longer on it, though. |
I assume find & replace uses some kind of caching system for all files when searching in project files, but when I delete a file through Atom, it should probably trigger an event to remove that file from the cache.
Currently, after having deleted a file, it will still show up in the search results, which is confusing at best.
Possibly related, but the fuzzy finder module is also plagued by this issue, see atom/fuzzy-finder#168
The text was updated successfully, but these errors were encountered: