Readability when working on files residing in a very deep directory structure
Opened this issue · 2 comments
Liquid displays the filename (with the complete absolute path) of the buffer in the lower left corner. At the right side of the filename information like row and column numbers as well as the current mode (INSERT, VISUAL, etc.) gets displayed. This is basically all fine, but if you work on a larger project which has a really (I mean really) deep directory structure and your monitor is only something like Full-HD and/or you want the liquid window displayed alongside something else, you will neither be able to see the complete filename, nor any of the other information described above anymore.
When switching buffers, it can also happen quickly that two lines will be used for one buffer entry.
All of this is not much of a show-stopper and might be a rare case, but maybe there is a way to improve the readability of really long paths/filenames? Something like only displaying the top and last directory together with the filename, so e.g. instead of
displaying
"/home/daisybytes/my/very/very/deeply/structured/terrible-project/sucks.txt"
maybe
"/home/.../terrible-project/sucks.txt"
"my/.../terrible-project/sucks.txt"
or something completely different could be displayed to shorten this down.
A very quick and dirty "solution" could also be to just switch around the information in the status line and show the file/path information on the right and the other things on the left. Then you might still run into the situation that the filename is too long, but at least the other things are still readable 😉
I have made a commit to handle this. There is now a general function for trying out different strategies to shorten a path below some given max. It is used in the status-bar and buffer-chooser.
I now also show how many percent into the file the cursor is. # # #
Sorry for the late reply 😓 That works nicely, it might make sense to shorten the paths for the files added to the typeahead too?