PathSnagger 1.1b4 Available

New in 1.1b4:

  • Unix Paths” and “Use Quotes” are now enabled by default. Fixes an issue where it appeared PathSnagger wasn’t enabled because it wouldn’t show up in the contextual menu. This was because nothing was enabled by default.
  • Default separator is “;”
  • Recompiled with 10.2.8 SDK. Should provide compatibility with 10.2, and hopefully with 10.1.

Download.

8 thoughts on “PathSnagger 1.1b4 Available”

  1. jay

    PathSnagg 1.1b4 converts space character into “”\ ” (without quotes)
    “~/Desktop/Menu\ Master\ Read\ Me.rtfd”

    Here are 3 variations:
    file://
    file://localhost/Users/jaychow/Desktop/Menu%20Master%20Read%20Me.rtfd/

    Unix:
    “~/Desktop/Menu\ Master\ Read\ Me.rtfd”

    HFS:
    Macintosh HD:Users:jaychow:Desktop:Menu Master Read Me.rtfd:

  3. jon Post author

    WordPress strikes again. Since it seems to be impossible to use the backslash character on this blog, I’ll just use (bs) to indicate a blackslash.

    Are you saying that when you snag the Unix path with quotes you’re getting escaped spaces? Or is this happening when you snag the Unix path wihtout quotes?

    In other words, this:

    “~/Desktop/Menu(bs) Master(bs) Read(bs) Me.rtfd�

    or

    ~/Desktop/Menu(bs) Master(bs) Read(bs) Me.rtfd

    ?

    If it’s the second one, that’s by design. If it’s the first example, then that’s a bug.

  4. jon Post author

    Actually, as a test I’m wondering if typing two blackslashes will render one backslash on the page: \\

  6. jay

    With quotes:
    “/Applications/Address(bs) Book.app”

    Without quotes:
    /Applications/Address(bs) Book.app

    Same problem.

  7. monoclast

    PathSnagger should not add escape characters (\) for spaces in quoted paths.

    Actually, I can think of times when even UNquoted paths should have escape characters in them. So it might be best to make this a user-configurable setting.

    Any idea when this will be fixed?

  8. monoclast

    (oops – correcting some typos in my post)

    PathSnagger should not add escape characters (backslash) for spaces in quoted paths.

    Actually, I can think of times when even UNquoted paths should not have escape characters in them. So it might be best to make this a user-configurable setting.

    Any idea when this will be fixed?

Comments are closed.