Sunday, February 25. 2007> cd to ... version 2.1.1 (just a little update)So 2.1.1 fixes a bug when you have an apostrophe in the path for Terminal.app and iTerm plugins. Just a little shell script whoops. Therfore I recommend updating. Also, for 2.1.1, a big thanks to Brian Koponen who contributed a plugin that enables support for PathFinder. So now “>cd to …” can work exactly like “Reveal in PathFinder”,which is an applescript that is bundled with pathfinder but obvoiusly “>cd to” is a TON faster. update: Little bug in the build, the info plist didn’t have the excutable name macro replaced, which made launch services upset, and wasn’t noticeable from the Xcode since it would launch from the actual executable rather than the bundle. There is a new build out now. Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
2007-02-24 20:46:19.212 open19882 LSOpenFromURLSpec() returned -10827 for application (null) urls file://localhost/Applications/%3Ecd%20to%20….app/ (Intel MacBook Pro.) 2.1 works fine, 2.1.1 doesn’t. ~L 2.1.1 also fails on a G4 PowerBook. I get the dialog box: ‘You cannot open the application "> cd to …" because it may be damaged or incomplete.’ Thanks! This was due to a broken info.plist file, I added a script to the build process that robert wrote for niceplayer, this makes the bundle version == svn build number, however I had forgotten that it doesn’t work with the default macros in an info plist, so i just had to hardcode them in. I have a new package available at http://code.google.com/p/cdto Good work! Putting bugs in the isssue tracker at http://code.google.com/p/cdto/issues/list is the best way to make sure they stay on my radar for the next release Thanks for the cool app Jay. Check out my latest hack: http://osx.iusethis.com/app/gmailapp What are you up to these days anyway? ~L Claudio So for applications that support UTF-8 and UTF-16 such as Termal.app and PathFinder, cd to works fine with accented characters such as the ones you listed in your comment, and I also tested japanese (UTF-16). iTerm & xterm do not support these characters (iterm just does nothing, and xterm will cd, but displays the wrong chars, and blows up with double byte utf-16 characters too). So It’s not really my bug as it does works with programs that support them and would work with the others if they had support. just wanted to let you know that you write some really high quality mac apps. keep up the great work! Please update for Leopard. Please Please Please! : ) Talk to you soon— |
QuicksearchStatic PagesCalendar
ArchivesSyndicate This BlogShow tagged entries |
|||||||||||||||||||||||||||||||||||||||||||||||||
