Rendered at 19:36:21 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
modinfo 1 hours ago [-]
I use atuin is like yours fzf+ml but for ctrl+r, also with fuzzy search, but somehow i like your project, as i started first time (tui) it just take small amount of time to index, even detected my zoxide already! then just works but somehow i don't like if time 'x seconds ago' is updated live, maybe add some config for static time for tui? But great work!
articulatepang 37 minutes ago [-]
(author here)
Thanks!
> maybe add some config for static time for tui
I thought about it and decided you're right: there's no reason for that time to update every second. I changed it to only update once a minute. That way, if someone leaves the TUI open for a while, the times will still be accurate, but it won't be needlessly attention-grabby.
Pushed to github and started releases on crates and homebrew.
_doctor_love 40 minutes ago [-]
Is atuin worth it? I keep seeing it highlighted but have yet to make the plunge.
eterps 2 hours ago [-]
I use fzf for a lot more than selecting files, this seems mostly focused on files and directories?
articulatepang 46 minutes ago [-]
(author here)
Yes! For now this is just for files and directories. In principle the same idea can be extended to other things people use fzf for, like selecting processes or containers. But one of the reasons I found this works so well is that we can use filesystem metadata as input to the ML model. LightGBM works great on that kind of numerical/tabular data.
For more general text input, I don't currently have any great ideas for how to make that fast and really good. Transformer models can do prediction on that kind of data, but they're a bit too slow for now.
Thanks!
> maybe add some config for static time for tui
I thought about it and decided you're right: there's no reason for that time to update every second. I changed it to only update once a minute. That way, if someone leaves the TUI open for a while, the times will still be accurate, but it won't be needlessly attention-grabby.
Pushed to github and started releases on crates and homebrew.
Yes! For now this is just for files and directories. In principle the same idea can be extended to other things people use fzf for, like selecting processes or containers. But one of the reasons I found this works so well is that we can use filesystem metadata as input to the ML model. LightGBM works great on that kind of numerical/tabular data.
For more general text input, I don't currently have any great ideas for how to make that fast and really good. Transformer models can do prediction on that kind of data, but they're a bit too slow for now.
I'd love to hear suggestions!