PathSnagger is available! (in beta form)

The new release of CopyPath has been renamed to PathSnagger.

This adds several frequently requested features:

  • Quotes are now optional.
  • The separator between multiple files is now configurable.
  • The menu options can reside in either the root menu or within a submenu.

The new features are configured via a Preference Pane in System Preferences.

Try beta 2 and let me know what you think!

Download PathSnagger 1.1b2

9 thoughts on “PathSnagger is available! (in beta form)

  1. Shon Vaughan

    This is a utility that I have needed for years. It will eliminate a great deal of typing on my part. I would give you a hearty handshake if I saw you in person. Thank you.

  2. jon Post author

    Glad to hear it! Please let me know if you find any problems. I am delaying a public release of PathSnagger until I determine it works with Tiger. Feel free to list any problems you might have with beta 2 here.

  3. Christian Zwieb

    Thanks for the recent PathSnagger. Having the option to output the path as ~/file.doc is a great improvement over CopyPath. Even more useful would be to add an option which generates soemthing like file://localhost/file.doc. Then I could go to this file with a single Command-Click and won’t need to copy/paste ~/file.doc into a browser or add file://localhost/ manually.


  4. Laura

    Awesome. This is something so valuable, I still can’t believe it isn’t built into the Mac OS. You rock!! No more screengrabes to describe the convoluted pathway thru directories to a file.

    I want it to work for me in Network display or when using Connect to Server. I think I’m still in my infancy with this valuable little item…
    I found the links work in iChat or Safari, but not much else for me.

    Perhaps a little documentation on exactly the diff b/t HFS, UNIX, and File means to mortals. Even a tips .pdf…anything?

    Thanks again! I’m sharing this like blazes in my web-design group.


  5. Jon

    Laura, I haven’t done much with it in regards to Network drives. I’m sure it could be improved in that area.

    I’ve been saying this for months, but I really do intend on fixing some of the outstanding issues, as well as adding new functionality to PathSnagger. 1.1b5 is in the works. I’ll post something here when it’s available.

    In a nutshell: a “Unix” path (also called POSIX path) uses slashes as delimiters. So a file called “File1.txt” that lives in my home directory would appear like this:


    That file in HFS format (which uses colons as delimiters, as well as referencing the hard drive name) would look like this:


    A “File to” path is a local URI. It would appear like this:


    Hope that helps,

  6. Laura

    Jon, I appreciate the breakdown.
    It might be worth your while to play with Network paths concept.
    Generally, that seems to be a valuable untapped market for this type of tool…Macside, your PathSnagger seems to be without competetion, unless a separate (overblown browsing) app entirely. very simple, easy, communication of path/location is very necessary, in it’s many formats and locations…especially on a local network. One thing maybe you could add to PathSnagger rather than a “location.doc” file, might be a “create .afploc” to the features, and that could be made an easier, clickable attachment. Think about it. Keep up the good work.

  7. John BRIGGS

    Any chance of you revising your PathSnagger to be able to run on an Intel iMac ? After all it is now 2010.

    Your little piece of software is just what I need. I am prepared to give you a donation if necessary.

    Thanking you in anticipation


Comments are closed.