This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Redux of #762, which I closed after deciding the fix was too trivial to warrant another entry in the Atom team's creaking PR backlog.
Reopened after I lost ~10 minutes thinking a log hadn't been updated (and trying to debug why), only to realise I was being bitten by this bug the whole time. I realised there're probably many more users who're getting false negatives after rerunning a search at startup, which could cost them pointless time too...
/cc @maxbrunsfeld
Steps to reproduce
Expectation: Markers should appear in the buffer
Reality: The program beeps at you as if the field was left blank