When filtering the results of helm-buffers-list or helm-for-files, as soon as I type a forward slash, Helm seems to switch from filtering results as expected to showing all buffers:

It seems to highlight some letters in the buffers list, but I don't see any logic or pattern behind this behavior.

I'm not sure why this happens. Is it a bug? Is it some special syntax I'm not aware of? Fuzzy matching is off as far as I can tell.

  • While helm matches buffers, / is used to match directory name, you can find some info on this with C-h m (which is already displayed in helm's mode-line). And you also need a blank space before and after /, otherwise helm doesn't filter any buffer, for example, as you can see dmd/src is matching all buffers.
    – xuchunyang
    Apr 6, 2016 at 20:33
  • That's only if you start the search with /. According to the documentation, at least. Apr 6, 2016 at 23:45
  • If I add blank spaces around /, then locate no longer works. Having to type different patterns to search within subsets of results makes no sense. Apr 6, 2016 at 23:46
  • Different sources have different ways to interpret your search pattern and they may and may not work well at the same time.
    – xuchunyang
    Apr 7, 2016 at 4:34

1 Answer 1


Turns out it was a bug, now fixed.

  • Could you please accept this answer so we can mark this question as resolved?
    – Dan
    Sep 4, 2016 at 17:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.