Author Topic: Using a single tag file on windows and unix  (Read 3846 times)

mrothman

  • Senior Community Member
  • Posts: 122
  • Hero Points: 1
Using a single tag file on windows and unix
« on: October 17, 2007, 05:59:31 PM »
I just discovered the Auto-Updated tag files section in the tag files dialog and it's a huge win for me.  We have huge product, and I'm often working on very few files.  By pointing a workspace at the nightly build of the product and tagging that, and then including that tag file in my current working workspace, I can easily navigate around the product into files that aren't in my project.

BUT, now I'm greedy.  I work on both windows and unix (with SlickEdit on each), and I have that tag file on a linux server.  I'd like to add it to the Auto-Upated section on my windows project also.  The problem is getting SlickEdit to re-interpret the paths of the files in the unix tag file.  The original file names in the unix tag file have a fully qualified path, and look like this:

/mycompany/A/devel/somepath/filename.cpp

I'm using the Add Tags Database dialog from the Context Tagging dialog.   If I simply type in the network location of the tag file, like so:

\\mycompany\devel\sandbox\myname\tagfilename.vtg

SlickEdit thinks that each file in the tag file has the windows name of the form:

\\mycompany\devel\mycompany\A\devel\somepath\filename.cpp

In other words, it has pre-pended part of the path to the tag file (\\mycompany\devel) in front of each file name in the tag file.

My first thought was that it might have something to do with the  working directory I assigned in the workspace whose tag file I'm trying to share.  But changing that in a few different ways didn't seem to make a difference.

So, I'm trying to figure out the algorithm.  Maybe there's no way to do this (except to have two tag files), but SlickEdit gets so painfully close, that I'd like to be sure.

Thanks.