File path in deeply nested folders is truncated from the wrong side in quick open

[LangLangBart]

Info

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.69.2 (latest)
• OS Version: macOS 10.15

Steps to Reproduce:

1. Create a very nested file structure with some long filenames and similar sounding directories.
2. Open Quick Open (cmd+P) in vscode and search for this filename.
3. The file path is cut off before I can see which folder the file I was trying to open is in. In macOS Spotlight the file path is cut from the left (much better).
4. See image below for more clarity.

related ticket(s)

• Better represent long file names in quick open #58040

possible solution

1. Cut the file path from the left (favourite) or
2. allow the Quick Open field to be wider.

[LangLangBart]

Started experimenting after building from source, see diff and image below. I couldn't figure out how to truncate the entire path from the left (like in macOS Spotlight), did the next best thing and just limited the number of folders being displayed.

Diff

--- a/src/vs/workbench/services/label/common/labelService.ts
+++ b/src/vs/workbench/services/label/common/labelService.ts
@@ -251,7 +251,7 @@ export class LabelService extends Disposable implements ILabelService {
 				}
 
 				if (!relativeLabel[overlap] || relativeLabel[overlap] === formatting.separator) {
-					relativeLabel = relativeLabel.substring(1 + overlap);
+					relativeLabel = relativeLabel.substring(1 + overlap).split('/').slice(-3).join('/');
 				} else if (overlap === folderLabel.length && folder.uri.path === posix.sep) {
 					relativeLabel = relativeLabel.substring(overlap);
 				}

Putting this behind an option would be useful. e.g.
workbench.quickOpen.filePathTrim: 'noTrim' | 'headTrim'

• noTrim: Display of the entire path, provided it is not hindered by the size of the Quick Open panel itself (default).
• headTrim: Limiting the file path to up to three folders.

[TylerLeonhardt]

/duplicate #143956

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!