are not very usefully displayed.
More useful (where path_len > available_len) would be perhaps
first 70%*available_len ... last 30%*available_len
so maybe
/System/Library/StagedFrameworks/Safari/WebKit.fra....acOS/com.apple.WebKit.WebContent
there is a similar problem. The priority of path vs params is beyond me to hope to guess, in general across all systems & useages, but maybe 50% of available_len for each and then apply the ellipsis ideas as in the path only case? Perhaps I'd prefer more params as the path can usually be found via locate, find and other tools.
Does this recalculate and change when scrolling? ideally, if the performance impact is not too large, at least when scroll has stopped for a suitable amount of time!
Thanks for your consideration....
If full paths are being shown, as I usually do, then the very long paths in some OSen (e.g. macOS)
are not very usefully displayed. More useful (where path_len > available_len) would be perhaps
first 70%*available_len ... last 30%*available_lenso maybe/System/Library/StagedFrameworks/Safari/WebKit.fra....acOS/com.apple.WebKit.WebContentWhere there are many long parameter strings, e.g.
there is a similar problem. The priority of path vs params is beyond me to hope to guess, in general across all systems & useages, but maybe 50% of available_len for each and then apply the ellipsis ideas as in the path only case? Perhaps I'd prefer more params as the path can usually be found via locate, find and other tools.
Does this recalculate and change when scrolling? ideally, if the performance impact is not too large, at least when scroll has stopped for a suitable amount of time! Thanks for your consideration....