Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting hotfuzz-module to play nicely with consult #12

Closed
sjrmanning opened this issue May 2, 2023 · 2 comments
Closed

Getting hotfuzz-module to play nicely with consult #12

sjrmanning opened this issue May 2, 2023 · 2 comments

Comments

@sjrmanning
Copy link

I've been playing around with the hotfuzz-module and it's so fast — just ran into one issue with consult which uses these 'tofu' characters in candidates which breaks with this error:

Debugger entered--Lisp error: (wrong-type-argument unicode-string-p #(".gitignore�" 0 10 (face consult-file multi-category (file . ".gitignore")) 10 11 (invisible t consult-strip t)))
  hotfuzz--filter-c("m" (#(".gitignore�" 0 10 (face consult-file multi-category (file . ".gitignore")) 10 11 (invisible t consult-strip t)) #("README.md�" 0 9 (face consult-file multi-category (file . "README.md")) 9 10 (invisible t consult-strip t))
...

Any ideas how I can work around this? I've tried stripping out those characters but to no avail so far. Oddly enough it works fine without the compiled module (albeit much slower), so it might actually be an issue with my system/compiled module.

@sjrmanning
Copy link
Author

BTW, I've been able to get the module compiling and loading on macOS. I need to clean up how it works as I had to change some settings in the CMake file and it wasn't finding my emacs module header, but after working around that it has been working flawlessly, apart from this consult tofu character issue. This could be related, but also after cleaning it up I'm hoping to open a PR here :)

@minad
Copy link

minad commented Jul 1, 2023

If the non-Unicode Tofus create problems you can set consult--tofu-char and consult--tofu-range such that characters from the private Unicode plane B are used instead. The range will be smaller but encoding issues are avoided.

@axelf4 axelf4 closed this as completed in 6223294 Apr 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants