Conversation
264608c to
645e973
Compare
|
that's interesting. it seems the shorten parts can be highlighted correctly
Tested it work with term ansi hl, I see the code conceal the part not coverted by |
53dac58 to
e4b5075
Compare
I also tested with ANSI hl and it worked, also worked with
I'll let the AI fix it's own work let's see what it comes up with :-) |
cffe957 to
58013e9
Compare
|
insane!!! so cool (and scary) to see. cool feature nonetheless |
It’s a new era, we’re soon gonna be redundant, this was done with Opus 4.5, since then we had Opus 4.6, Codex 5.3, Kimi 2.5, MiniMax 2.5, Qwen 3.5 and more I can’t recall ATM, all can handle complex tasks even better than this, didn’t think I’d say this one day but soon (if not already) they’ll be coding better than me :) |
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces a winopts.path_shorten feature to visually shorten paths in the fzf window using extmarks, which is a great enhancement. The implementation is well-contained within a new PathShortener class and is correctly integrated into the FzfWin lifecycle. The logic for identifying and shortening path components is thorough, handling various line formats and edge cases like Windows paths. I have one suggestion to improve code quality by refactoring duplicated logic for UTF-8 character counting. Overall, this is a solid contribution.
|
lmao 💀 the immediate follow-up with gemini review |
What’s better than a model reviewing a model lol |
|
hm... maybe you reviewing my pr 🤔 |
Just write |
|
Acknowledged. I am now performing a code review for this pull request. |
7be8ff2 to
67901ac
Compare
|
/gemini review |
There was a problem hiding this comment.
Code Review
This pull request introduces a new feature for path shortening using Neovim's extmarks, implemented within a PathShortener class and integrated with the fzf window's lifecycle. However, a potential Denial of Service vulnerability was identified in the PathShortener._apply_line function in lua/fzf-lua/win.lua, where maliciously crafted long lines could cause the Neovim UI to hang. Additionally, there's an issue with the use of certain Neovim API functions for string manipulation that appears incorrect and could cause issues, for which a specific code suggestion has been provided.
67901ac to
3d019a2
Compare
Use `winopts.path_shorten` (instead of `path_shorten`) Fix #2517
3d019a2 to
2643d21
Compare
Ty for reporting #2607 |
|
(sorry for not opening a separate issue btw, I just didn't have enough time/spoons to fill in the form and try to come up with a reproducer using mini.sh; seemed that if I just post a screenshot it'll be obvious what's going on and it seemed unlikely this is my config messing stuff up) |
All good this is very obviously a bug and easily reproducible as the terminal text shifts due to the extmarks, may or may not be fixable, I’ll explore :) |
If it helps prioritise, I don't think I'll actually be using this myself. 🙂 |



I'm quite mind blown, this PR was one shot from a single prompt in opencode using subagents, the prompt:
I haven't reviewed the code yet, but my agents (3 different models) did and this is what they found:

Note it chose to use a different option as it affects the main fzf window only within neovim and can't be used in fzf-tmux so to use this you need to use
winopts.path_shorten:Honestly, this is quite shocking, the level of understanding of a very intricate problem and solution from a two-liner prompt...
The review seems to be on-point too (which I'll soon push it's changes too).