![]() It doesn’t AppleScript snippets in TextExpander expand perfectly on both my Intel and G4 machines. Typeit4me change set name trial#While waiting for a response, I downloaded the trial version of TextExpander to see if it has the same problem. I’m pretty sure the forum is where Ettore wants bugs reported. So far, there’s been no response from Ettore Software, which is a bit annoying. But I can’t use the feature if it keeps spitting out these spurious nulls. I really like the idea of having programmable snippets available system-wide, not just in TextMate. The problem arose when I tried to use the snippets I discussed in this post on my iBook G4. Is this some sort of big-endian/little-endian thing? Can it be fixed? Running the wc utility on these files also shows that the G4 versions have two bytes for every byte in the Intel versions: I got the same result from using the clipping in TextEdit on the Intel iMac: Saving the document to a file called tm-intel.txt and running xxd on it yieldsĠ000000: 6874 7470 3a2f 2f6d 792e 7961 686f 6f2e. On this machine, there are no blanks before the characters when the clipping is inserted in a TextMate document. I don’t get this behavior with the same clipping on my Intel iMac. So the nulls are there, but TextEdit just isn’t showing them. When I run the same clipping from within TextEdit, the spaces don’t appear, but saving it to a file called te-g4.txt and running xxd on it gives me the same thing: At first I thought this was some weird interaction between TypeIt4Me and TextMate, but… I’ve saved this in a file called tm-g4.txt and run the xxd utility on it to see what the characters are. ![]() The “spaces” before each character are not really spaces, they’re unprintable characters. When I run this clipping from within the text editor TextMate, it comes out looking like this Tell application “Safari” to get URL of front document I have a clipping with the following AppleScript: I am having a problem with TypeIt4Me’s AppleScript clipping feature on my iBook G4. Two weeks ago, I posted the following bug report to the the TypeIt4Me technical support forum: Next post Previous post TypeIt4Me problem with AppleScript snippets ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |