-
Notifications
You must be signed in to change notification settings - Fork 27
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
Path name is truncated (and inconsistently) #11
Comments
I think this is consistent in the sense that it's truncating directory names longer than 16 chars. Yeah...it's an odd default that's not called out anywhere, It's using the This is definitely a weakness we have when using terminal-based applications, since we can't use a variable width typeface that would allow us to use so much less space for these. Ideally there wouldn't need to be any options here because we'd just be able to do the most reasonable thing always. If anybody has any thoughts or examples of some project doing this well, I'd love to know about it. I don't care for the way telescope shortens directories. I'd much prefer if it only shortens as much as it would need to make the directory fit, but for that, the |
* Use a different highlighting group instead of parentheses for differentiating the directory vs. the filename * Use the width of the results window to decide how aggressively to shorten path names * Create tests for formatting functions Fixes #11
This change is available on the If there's anyone who can provide feedback on this, it would be a big help. |
It looks great! I just tried it and I think it works for whatever I have right now. Not sure if there is any edge case but at least it's working for me. Thanks for working on this! It's a daily plugin for me :) |
Implemented on 0.2.x branch. |
It seems sometimes the filepath is truncated, for example, I have a file in
tools/foobar_query_benchmark/main.go
And when I type in
bench/main
I can find the file but the path was truncated. At the same time, other file with longer path doesn't get truncated.I wonder if there is a way to configure so that either:
Again, thanks for the plugin I'm already enjoying the quickness when working on a large codebase.
The text was updated successfully, but these errors were encountered: