Files Tool Window - Path - can the displayed path be relative to project?

[gtrimble]

Hello,
Is there a way to configure the Files Tool Window display to show the path relative to the project directory?

As it is now, it shows the entire path from the root of the drive that I am on, which makes it difficult to find the correct file because the filename(s) are on the left side and I have to scroll, sometimes around 145 characters, to the right to see the path to choose which file I need to open.

If the path were relative, it would reduce the length by 66 characters.

Thanks,

-Glenn

[warnerrs]

This.

[Tim Kemp]

I agree that this would be a nice feature. I think it would be a new feature though. So it probably won't happen soon.

If you would like to have this functionality right now, without SlickEdit changing, you might be able to use your operating to get similar results.

In Windows you can map a drive letter to your project path.

In almost everything everything else (all the UNIX spawn) you can crate a link to make a short version of the project directory.

I'm sure there are different and probably better ways to do this. Anyone else, please feel free to chime in with creative solutions.

[gtrimble]

Tim,

I tried mapping a drive to my folder, and even changed the working directory to that drive letter, closed and restarted SlickEdit, and the old drive and path still show up in the File Tool Window.

I also looked in the .vpw and .vpj file and didn't see the old drive letter.

I will check to see if creating a new project using the newly mapped drive letter works.

Thanks,

-Glenn

[gtrimble]

I created the new project with the new mapped drive letter, but the File Tool Window still shows the old "fully qualified" letter with path. Windows just doesn't want to be without an anchor I guess.

-Glenn

[Dennis]

That is a good idea.  I am filing a feature request for us to add that option to a future release.

Here's a query though, if the relative path is "../../monkey/business/", instead of a path directly under the workspace or project directory, would you still want the relative path or the absolute path for that file? 

I would vote for the absolute path, but I think an argument could be made for allowing a single set of dots, but after that divining the path requires more thinking than it is worth to save the space.

[Tim Kemp]

@gtrimble, I tried it and it seems to work fine.  Here is the original:


And here is after I mapped C:\data\MiniSensor\branches\ULCE\Sensor to w: and created a new project with the same files:


Here is the command I used to do the mapping (if it makes any difference):
subst w: C:\data\MiniSensor\branches\ULCE\Sensor

[jimlangrunner]

Now, see, I would have used "net use" for the mapping. Might even have had to create a share to do it.  Trying that now.

[gtrimble]

Hey Tim,

That works for me.
subst y: w:\bfc_work1\gtrimble\accu\INT_ProdRlsD31Ver600_gcc492\rbb_cm_ecos

Thanks!

[gtrimble]

Hey Dennis,

I would think that a relative path to the working directory would be the way to go. That way, I wouldn't have to "nail-up" lots of drive letters for paths to projects. I have many projects and that would soon exhaust the available free drive letters.

Thanks,

-Glenn

[Tim Kemp]

Hey Glenn,

It's sort of old school, but you could make a batch file for each project to remap the drive letter. That way they could all use the same drive and you wouldn't run out of drive letters. It's, "subst w: /D" to unmap the substed drive.

[gtrimble]

That's a great suggestion, thanks Tim.