You can still do this in LaunchBar, but it takes more keystrokes. I liked to be able to type "ctrl + option + cmd + l" and go to the login window. It has "abbreviations", but it's not the same. You could assign a keyboard shortcut to any "subject, verb" action. This was one of my favorite things about Quicksilver. While it has been an overall positive experience, there are still some things LaunchBar could learn from Quicksilver. LaunchBar doesn't randomly forget its settings like Quicksilver would with the actions sometimes LaunchBar is really fast compared to Quicksilver This makes things like WordService useful again! Using the OS X services menu items in LaunchBar actually works. You can merge multiple clippings into one by using the ClipMerge functionality The clipboard menu tells you where the item was copied, and how many characters and lines it contains You can access each line of a copied item from a sub menu It doesn't assume that everything with a dot in it is a URL The clipboard in LaunchBar is really nice The default setup of LaunchBar makes much more sense, which is helpful for n00bs If you've ever set up the clipboard and shelf in Quicksilver then you know what I'm talking about. Setup of LaunchBar is orders of magnitude easier than Quicksilver. Web searches are quoted properly, you can search for "Bob Marley & the Wailers" and get the proper results Here is a rundown of some of the features that make it one of the best I've used. There are a lot of really nice features in LaunchBar. In the week and a half that I've been using it, the program has really exceeded all my expectations. Most of them are bearable, but sometimes it can be really annoying when you are trying to get something done fast. Quicksilver has been plagued with some really strange issues for quite some time. That has turned out to be an excellent choice. I recently overheard Andi Zeidler talking about LaunchBar on Twitter, so I decided to give it a try. While there are still some folks working on the open source version, it has been a slow process. This was pretty much the beginning of the end for QS. Quicksilver was recently open sourced, since the lead developer now works for Google and their launcher product called Google Quick Search Box. Quicksilver has been my "launcher" of choice for quite some time now and before that I was using Butler, which I originally tried out because of its clipboard implementation. I guess "launcher" is a really bad term for it, in reality it's a "do a bunch of awesome stuff thingamajig", but that's not easy to say. I need to be able to manipulate the item from the launcher, not just open it. On OS X there is always the Spotlight functionality, but that has never satisfied my needs. It is really painful when there isn't one available, "How the hell do I open an application?!?!". Whether I ran your the solution with GUI scripting, or with the above workflow, the input text file printed exactly as it appeared in TextEdit.A good app launcher makes all the difference in the world to me. Tell application "System Events" to keystroke "p" using withoutprint dialogĪnd used in the context of your original workflow: If you intent is to just pass the Playground.txt document into TextEdit, have it print the file, and then remain open, then you will need this AppleScript in place of your current effort: It won't print until you have selected a file. Your Run AppleScript content as it is currently written will ignore your specified Finder item file, launch TextEdit, and present the File Chooser. I have to use plain text for other reasons - that part is non-negotiable. Please does anybody know how I might write an applescript to print the document instead (that I could insert into my automator workflow which also contains other actions after the printing) so that I could control the printing settings and the words would not break? The margins don't matter so much but broken words are very hard to read. (If I print the same document from Textedit it comes out fine with margins and no broken words.) Is very quick but I get strange results: the text goes right from one side of the paper to the other and words are broken across lines (no hyphens just broken). (this is to be used in a live performance where I need to deliver printed scripts to performers just before they speak, so every second I can shave off the time taken to send the data to the printer is crucial) I'm trying to set up automator workflow to print a plain text document created in TextEdit as quickly as possible.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |