Our great sponsors
-
fuzzy_file_finder
A (slightly enhanced) implementation of TextMate's cmd-T lookup functionality, in Ruby, for embedding in other projects
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
c2nim
c2nim is a tool to translate Ansi C code to Nim. The output is human-readable Nim code that is meant to be tweaked by hand before and after the translation process.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
True. I checked and there are such packages already: https://github.com/bling/fzf.el
Notes: The original implementation of the algorithm: https://github.com/jamis/fuzzy_file_finder Original Emacs plugin for it: https://github.com/justinweiss/fuzzy-find-in-project My rewrite of that plugin: https://github.com/piotrklibert/ffip
Yes. Nim compiles to C and has a lot of features for interacting with C code. You can easily call C routines from Nim and Nim functions from C. There's a bit of a ceremony you need to go through, but most of it can be automated with c2nim tool: https://github.com/nim-lang/c2nim
The original template and helpers for writing Emacs modules in Nim is here: https://github.com/yuutayamada/nim-emacs-module but it doesn't work with modern Nim versions, so I had to fix it a bit. That repo seems unmaintained, unfortunately.
Thanks :) Judging by the upvotes there is some interest in the module like this, so I'll keep working on it. It'll take some time before it's usable by others, I think I should be able to clean up the code and write a better Elisp wrapper in a week or two. I used Ivy for displaying candidates because it was by far the easiest integration: literally 1 line of code (https://github.com/piotrklibert/ffipf/blob/master/elisp/ffip.el#L41), but I'm more used to Helm, so integration with it will definitely come next. I don't use Selectrum/Prescient/Embark/etc. personally, but I don't think writing integration with them would be hard. The main selling point of this module is that it's synchronous yet still fast enough, so there's no need for implementing async behavior when integrating it with a framework.