Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I use a software library whom I often refer to the documentation pages.
Those are html pages, therefore I created several bookmarks to quickly access to them.
However, when the library version changes, my bookmarks become deprecated.
I have a Windows environment variable that holds the library path. Is there a method to use it in order to create bookmarks I would not need to update every time the library version changes ?

share|improve this question
What OS environment please! – mdpc Jan 10 '13 at 6:54
Windows 7. I edited my questions to refer to it. – wil Jan 10 '13 at 8:09
up vote 3 down vote accepted

I don't know about environment variables, but I have a better solution. Why not create directory symbolic links instead?

For example, suppose you have a bookmark to C:\Software Library\Version 1\Documentation\index.htm, that broke because now you have C:\Software Library\Version 2\Documentation\index.htm.

Open an elevated Command Prompt, navigate to wherever you want to create the link (could even be on a different drive altogether), and issue the following command:

mklink /d Docs "C:\Software Library\Version 1\Documentation"

Now suppose you did this on D:\, you'd see D:\Docs (with a shortcut arrow overlay), which is actually a directory symbolic link to the original directory. Open D:\Docs\index.htm in your browser and add a bookmark to it (and any other sub-pages as well if you want).

After the version change, simply delete D:\Docs from Windows Explorer and issue the following command:

mklink /d Docs "C:\Software Library\Version 2\Documentation"

Now when you open the bookmark to D:\Docs\index.htm, it will automatically open Version 2 instead of Version 1.

share|improve this answer
Thanks for the suggestion, I will try this and get back to you. – wil Jan 11 '13 at 1:42
I accepted your answer as there are no other suggestions. The thing that bothers me is that I might forget to update the symbolic link after a library version update, and I would not notice it since when using this method the version number is not displayed in the file path anymore in Chrome. However, it works fine. – wil Jan 15 '13 at 10:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .