Radon Rosborough

> right next to the match I'm assuming you mean this functionality of CTRLF, which displays the match count and index within the buffer, rather than only the minibuffer: 

What are the issues you're facing with your current implementation? Maybe I can help advise.

> there's an issue with tabs vs spaces Yeah, that's just because `indent-tabs-mode` foolishly defaults to non-nil. We can disable it in file-local variables, no need to pull in anything...

I feel bad for letting this sit so long, let me see if I can fix up any remaining CI failures and merge this in.

Hmmm. But, if your code is in CRLF format, then you'd _except_ `^M` to be everywhere, right (`^M` is just a CR)? You just expect for it to be invisible....

Yep, that sounds totally reasonable. And I think the implementation will not be too hard as some of the relevant primitives already exist; for example, the `:bound 'wraparound` argument passed...

I think that's a fine idea as well, thanks for the suggestion!

Makes sense, thanks for the pointer. Yes, indeed, CTRLF is slow for large files. That's because it's actually doing an eager search of the entire buffer every single time you...

These all seem like reasonable proposals. My thoughts: * I am not sure why `initial-contents` is not supported in `ctrlf-backward`; that feature was added in https://github.com/raxod502/ctrlf/pull/48. I suspect it would...

Perhaps, if it can be implemented in a clean way. Most likely by modifying the existing lazy highlight code to also collect a list of lines from the buffer, and...