Normally when I run
helm-find-files I'm immediately shown a list of files in the current directory. Sometimes, however, helm just gives me an empty window. I can start navigating my filesystem in that window like normal, but I have to start navigation from the root of my filesystem. It's as if helm didn't/couldn't figure out the directory of the file I'm editing.
For example, I see this problem if my cursor is at the very beginning of a typical HTLM file:
<!doctype html> ^ point is here
or at the end of a line with a meta tag:
<meta charset="utf-8"> ^ point is here
If the point is anywhere else in those lines,
helm-find-files works as expected. In those positions, though, it seems like helm gets confused.
So my question: Is this expected behavior? I know that helm is complex (heck, it's probably self-aware), and it may well be that this is the "correct" behavior somehow. If this is expected, can someone explain why? I just need a better mental model of what's going on.
If this is not expected behavior, I'll likely file an issue with helm. I just wanted to do some due diligence before that, though.