This window is opened by TextMate's TODO-command: it collects a list of your TODO-markup of files in the current document's path (see text for details). I hadn't anticipated such behavior, but being a programmer and former Eclipse-user I already have a habit of marking text and code with "TODO:"-comments, so this tool not only allows me to keep an overview over the state of my work, but even gives me a motivation to be consistent in my application of such markup. This list is then presented to you, HTML formatted, with links that allow you to jump to the respective positions in each document. While browsing the list of those preconfigured commands I found an entry called "TODO", and assumed this would open a separate document that I could use to manage my todo-list, but what actually happened was even better: the command searches documents for lines with the string "todo" and collects those lines in a list. (By the way I just checked: these commands are shell scripts! Very cool. It's a somewhat sad statement about the state of application development, but I was impressed by such a seamless integration of customizable functionality into the application. My initial assumption was that this is a categorized list of scripts or macros that can be edited and appended by the user, and so I was surprised that quite a large amount of the individual menu entries had not only shortcut keys assigned to them, but those shortcut keys were even shown in the menu entry of the respective command. My initial assumption was that it is still early in the development process, so I planned to wait for a later release before I would decide if I should register a copy but then I started using it for a couple of days and found several functions that blew me away.Ī tip of the day introduced the "^R" shortcut that executes the current line as shell script and inserts the output into your document this is quite useful to me as I'm starting to use the shell and especially shell scripts for various text management functions and plan to do even more so in the future.Īfter playing around with this for a while I decided to browse the application menu for other useful tools, and found the "Run Command" section in the "Automation" menu. dump Display full database contents after registration.I've just started using TextMate. f force-update registration info even if mod date is unchanged R Recursively register directory contents, including the contents r Recursively register directory contents, do not recurse into lazy n Sleep for n seconds before registering apps if the local cache load Load the LaunchServices service plugin if it's not already loaded. convert Register apps found in older LS database files lint Print information about plist errors while registering bundles kill Reset the global Launch Services database before doing anything else For domain specifications, ask CF for the list of application Search the paths for application bundles and add each found item to the Launch sudo /System/Library/Frameworks/amework/Versions/Current/Frameworks/amework/Support/lsregister -kill -r -domain local -domain system -domain user & killall Finder The issue is caused by a corrupt Launch Services database and can be fixed by running the following command in Terminal and resetting Finder. If a file has inconsistent line endings, Textmate will treat \n as a line ending marker and display as text. Textmate files are set with one of three options.
0 kommentar(er)
