Show part of the path if several open file names are the same

[Dainius14]

Feature

Currently when I open several logs from production, test, dev servers with the same file name, I see 3 tabs with identical names - app.log, app.log, app.log. It'd be great to see parth of the path if the current shown tab name is identical to some other tab. That is, tabs could be /prod/app/app.log, /qa/app/app.log, /temp/app/app.log. This way I could distinguish between witch tab is for which log.

I got this idea from VS Code. (don't mind the arrows, copied from the internet)

[Hirogen]

There are a few Questions that need to be answered:

• 1. How many Characters for the pathname is to many characters?
• 2. How many is not enough?
• 3. Should the full path be displayed or only half of it?
• 4. What is enough information to distinguish between the files?
• 5. What happens if a path is 256 characters long? and you open 3-4 Files from this path, then you will be unable to switch easily between tabs

Would it not be easier to just rename the logfiles to "prod" "test" "dev"? For instance, at my company every logfile that is generated has the hostname in its filename

hostname.server.log
hostname.client.log
hostname.protocol.log
hostname.whatEverNeedsToBeInALog.log

With this, it's easily distinguished were the file came from and what logfile I'm currently reading.

[Dainius14]

1. Could be determined via trial and error.
2. When file names are still identical.
3. Just enough path to have different names.
4. ^^^
5. As much path as possible is shown. If it's still not enough, well, then it's not enough, there's nothing much that could be done.

That's a nice idea. But looking at just the log files, it makes little sense to have host name in the file. From the perspective of the log file that information is redundant.

VS Code behavior could be investigated first, to see how the big boys did it.

[Hirogen]

That's a nice idea. But looking at just the log files, it makes little sense to have host name in the file. From the perspective of the log file that information is redundant.

but from the perspective of the user its not redundant, the user has the problem that he can not distinguish the files on from the other, so if the hostname is in the filename, the user would easily distinguish the logfiles.

1 Could be determined via trial and error.
2 When file names are still identical.
3 Just enough path to have different names.
4 As much path as possible is shown. If it's still not enough, well, then it's not enough, there's nothing much that could be done.

1 => bad practice
2 => how do you determine if file names are identical? is "Logfile1.log" the same as "logfile1.log", on windows systems, this is the same file, on unix systems those are 2 different files!
3 => see 2
5 => bad practice