I'm refactoring. I press cmd-shift-f, type some characters, press enter, click on one of the search

[jbarnette]

I'm refactoring. I press cmd-shift-f, type some characters, press enter, click on one of the search results, and replace the matching line with a new implementation.

I press cmd-shift-f again, press enter again because it's the only way I can see the search results without tabs, and the old version line I just changed is still in the search results.

Occasionally the results will mix it up by giving me duplicate results for the same match: One with a path relative to the current project root and one with an absolute path.

I've reported this and related issues a few times now without getting much insight. I'd really like to know what I'm doing that makes search usless for me and OK for everybody else. What am I doing wrong?

Atom Version: 0.49.0
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Atom/0.49.0 Atom-Shell/0.8.7 Safari/537.36

[izuzak]

@jbarnette Wondering if you're still seeing these two issues you reported:

I press cmd-shift-f again, press enter again because it's the only way I can see the search results without tabs, and the old version line I just changed is still in the search results.

I think this might have been fixed in atom/find-and-replace@27c9b51 (I can't reproduce it locally).

Occasionally the results will mix it up by giving me duplicate results for the same match: One with a path relative to the current project root and one with an absolute path.

Are you perhaps seeing this for symlinked directories, as described in atom/find-and-replace#129?

[jbarnette]

@izuzak I don't think I've seen stale results recently, but I haven't been doing a ton of coding. I'll keep 👀 out. I am seeing the duplicates in a directory that's symlinked, interesting.

Closing this because stuff's either fixed or tracked elsewhere. 🔨

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!