Universal Binary Test Build Available

I’m really sorry PathSnagger isn’t working on Intel Macs. I’m trying to get it done soon. For various reasons, the computer has been offline and I haven’t had much time to do any work on it.

For those of you who absolutely can’t wait, there is a Universal binary version available, although I can’t guarantee its stability. I’ve had a couple of people test it on their Intel Macs, and it worked, but that’s about the best I can do (unless someone wants to donate a MacBook to the cause .. ) It has a number of new features that haven’t really been turned on (ie, the UI is there, but the functionality is not.) So yes, it says something about automatically updating and Windows paths and some other goodies, but it won’t work! There, I warned you.

That said, all the old functionality should be there. So if you’re feeling brave, download the Universal Binary build and let me know how it works for you.

66 thoughts on “Universal Binary Test Build Available

  1. podi

    I think a best one among various path copy softwares. But there is a big problem. I am using Mac OS X on Korean system. So I have many korean files and directories. When I copy a path include korean file or directory name, it don’t copy a path to clipboard. I think that this problem is a software bug. I expect this problem will be fixed.


  2. jon Post author

    podi, do you see anything in the Console when you attempt to copy the path? Are you doing this with Unix or HFS paths?

  3. podi

    I’m sorry that exaplained the problem in detail.

    Copy HFS path: the path is not copied and Console says ‘Got a null string’ on Korean language logined.
    In English language logined, the path is copied but korean character is broken.

    Copy Unix path: Console says ‘Could not copy path of selection.’

    This problem is only appeared in paths include korean characters.

  4. jon Post author

    podi, what happens if you drag a Korean file to an open Terminal window? That should print the file path right in the Terminal window.

  5. jiri

    I test it on Intel iMac 17” and 10.4.6.

    Does not work for me at all:
    HFS returns in console – 1212PathSnagger: Got a null string.
    Unix returns in console – 12PathSnagger: Could not copy path of selection.

    I installed it for all users.
    Something not so much standard – I have Czech set as the first language in System preferences -> International -> Languages

    I hope it helps you some how.

    Than you trying to develop it also for Intel … love it on my ppc iBook G4


  6. Spencer

    Works like a charm for me! Thanks much. I appreciate it. (I really missed it)

    (MBP 15′ 2 gigs of memory. OS completely up to date).

  7. Brian Topping

    Echoing Spencer’s sentiments (and system configuration). You rock. I really missed it too. I owe you a beer or three when we cross paths.

  8. Michael

    I’m very happy to see this fine product available in univeral form!
    Works as expected and hasn’t done anything strange (yet 😉
    I just installed it and will make much use of it again.
    Thank you!

  9. Pat

    Worked for me as well without any issues. Machine is a MacPro 17″ 10.4.7 (English Language). Adding my echoes to the chorus of Thank You…greatly missed and appreciated! Paypal my next posting 🙂

  10. Scott Cooper

    No dice. I double-click PathSnagger.prefPane, & get:

    “Could not load PathSnagger preference pane”

    The error message in Console is:

    System Preferences[1077] [NSPrefPaneBundle instantiatePrefPaneObject] (/Library/PreferencePanes/PathSnagger.prefPane): principalClass is nil.

  11. Brett

    The contextual menu works great, but the pref pane returns “Could not load PathSnagger preference pane.”

    15″ MacBook Pro 1.83 GHz Intel Core Duo
    Mac OS X 10.4.7

  12. jon Post author

    @Scott Cooper and Brett: This is the first time I’ve seen these reports. Are you guys sure you replaced the existing preference pane with the UB one? If you do a Get Info on the prefpane, does it say it’s a Univeral build?

  13. Matthieu


    works fine for me (only the UNIX path option tested) on my new macbook with the last Tiger version.

    MANY thanks, that’s very useful !

  14. Dave

    Working great, just tested on my new macbook as well. Just one thing, I unchecked the quotes option but it still keeps them, not a big deal really. Thanks very much for this.

  15. jon Post author

    @Dave: Did you relaunch the Finder? Changes to the preferences won’t take affect until you either do that or log out and back in again.

  16. Peter da Silva

    You shouldn’t have both “escape spaces” and “use quotes” concurrently enabled. Most shells will accept this double-quoted format, but a number of other applications will behave remarkably strangely.

    I would also like to have these options as submenus, because sometimes you need them and sometimes you don’t:

    Copy Path
    * UNIX format
    * * Quote
    * * Escape
    * Classic format (Not HFS, it’s got nothing to do with the file system, you can use Classic style paths on any file system)

    Also, you need to escape more than just quotes, and you need to escape some characters even when you’re quoting: quotes and backslashes at a minimum!

  17. jon Post author

    If someone can point me to a reference that indicates ALL of the characters that should be escaped in a UNIX shell, I’d be very very happy. I can’t seem to find anything like that.

  18. Eytan

    Love the System Pref. Works great for me. A recommendation for the Windows part is a way to place a drive letter there. The issue is when you are passing around URLs for a connected server at work – while the Mac works fine with volume names, windows still often needs drive names or server name (server name in addition to volume name) and a quick way to pre-pend a drive letter would be sweet.
    Thank you for a great tool!

  19. John Cradock

    I’ve got a MacBook Pro 2.0GHz Core Duo running 10.4.8, and this is working great for me. Thanks for releasing an Intel-compatible version.

  20. Hackbert

    @matx: Agree. None of them should be in a filename, but all of them (except ‘/’) can we and will often be.

  21. James

    I’ve been using the universal Intel ver since it was first available, and it has never caused me any problems.
    Thanks for a very useful utility.


  22. Bob Wallace

    Version 1.1UB (universal binary) works fine on an Intel iMac with OS X version 10.4.10. Tried all the options and they work. Some, but not all, require relaunching the Finder for an option change to take effect.

    One suggestion: change the assertion at the top of this page that PathSnagger doesn’t work on Intel Macs; it does!

    Thanks to Jon Baumgartner for a very useful and appropriately designed tool.

  23. jon Post author

    Thanks, everyone. I’m still trying to finish up work on the next release. It’s taking way longer than I expected, mostly because I just don’t have enough free time these days. Given the success of the test build, I think I might just point everyone to that as the default build, even though it’s not a release build. Stay tuned …

  24. cait

    I just installed PathSnagger on my intel mac 10.4.10, installation went fine, it appears in my system preferences, but control click drop down list does not give me PathSnagger options… I restarted my computer, still no new menu items on control click. I’ve tried checking and unchecking various options and relaunching finder too without any effect. Any ideas?

  25. François

    Thank’s a lot for this usefull tool !

    Just work fine on MacBook Pro 17′ Release 1 and Leopard 10.5 😉

  26. jon Post author

    @cait: Did you enable at least one of “Enable Unix Paths,” “Enable HFS Paths,” or “Use file:// paths” and restart the Finder?

  27. jon Post author

    @Dave Douglas: Sorry, no. Hopefully soon (I know I’ve been saying that for quite some time now.)

  28. cwittenb

    thanks very much, works great for me!

    just one thing:
    on Tiger 10.04.10 I can double click the preference file and it will install into my system preferences. Still I had to copy the plugin manually to the Context Menue folder.

    Anyway, neat stuff!

  29. Erik Cayré

    Works for me too!

    I use the bleeding edge (2006!) 1.1 Universal version with Mac OS X 10.5.1 on a MBP 2.33

    I can confirm it doesn’t work with odd characters. In my case it was a volume name “Fælles” which prevented it from ‘snagging’. After mounting the same volume via SMB instead of AFP I could snag the path (via SMB it is named ‘Faelles’).

    I wish to cast a vote on upgrading the foreign character support in pathnames. As a danish writing user, I would very much like support for Æ Ø Ã… É. I’m sure others need support for other characters…

    Thanks for a nice little tool (which Apple should have built into Mac OS X long ago)


  30. jon Post author

    @Erik Cayré: I’m very sorry it hasn’t been updated in so long, but I am glad to hear it works on Leopard. If you drag the file to a Terminal window, does it correctly display the characters?

  31. Erik Cayré

    I just dragged a folder on an AFP server to a Terminal window and got this:

    eac:~ eac$ /Volumes/Prepress\ HD/\ Igangværende

    So yes, foreign characters (in this case ‘æ’) do appear correctly in Terminal
    (tested on 10.5.1, the AFP server is Xinet FullPress 14)
    ((the backslahes appear in front of [space] characters, quite normal and as expected)


  32. jon Post author

    Awesome. Thanks, Erik. I actually finally figured out a way to do a better mass find/replace on the path strings, so I should be able to escape all of those characters in one shot.

  33. Don Montalvo

    Just a note…would love to see “final” version released. Although we’ve deployed this to 1000+ Macs without a hitch. 🙂

    Don Montalvo, NYC

Comments are closed.