I just added a new feature to the "Show Actions" commands. The html windows generated now contain a checkbox, using which you can toggle whether the corresponding action is marked as completed or not. Each time you click the checkbox it writes on the corresponding file. It hasn't been checked much, so, you know, make backups and all that. Any errors encountered will show up in Console.app. You will need to switch away and back to textmate to see the changes in the gtd files.
Haris
I just checked out the latest bundles and I get the following errors when using any of the new "show action" commands:
/Library/Application Support/TextMate/Bundles/GTDAlt.tmbundle/Support/ bin/GTD.rb:41:in `parse': Parse error on line: @email (RuntimeError) . This is not a line I recognize. from /Library/ Application Support/TextMate/Bundles/GTDAlt.tmbundle/Support/bin/ GTD.rb:229:in `initialize' from /Library/Application Support/TextMate/ Bundles/GTDAlt.tmbundle/Support/bin/GTD.rb:100:in `new' from /Library/ Application Support/TextMate/Bundles/GTDAlt.tmbundle/Support/bin/ GTD.rb:100:in `process_directory' from /Library/Application Support/ TextMate/Bundles/GTDAlt.tmbundle/Support/bin/GTD.rb:99:in `each' from /Library/Application Support/TextMate/Bundles/GTDAlt.tmbundle/ Support/bin/GTD.rb:99:in `process_directory' from /tmp/ temp_textmate.dJjzV2:4
Additionally, I found another bug: If I use the "Clean up current file" command, all the tabs before the actions get converted into spaces resulting in the "EOL + Action" command not inputting the same indent as in the line before (only with "soft tabs" set to *off*).
Oliver
On 07.07.2006, at 17:02, Charilaos Skiadas wrote:
I just added a new feature to the "Show Actions" commands. The html windows generated now contain a checkbox, using which you can toggle whether the corresponding action is marked as completed or not. Each time you click the checkbox it writes on the corresponding file. It hasn't been checked much, so, you know, make backups and all that. Any errors encountered will show up in Console.app. You will need to switch away and back to textmate to see the changes in the gtd files.
Haris
On Jul 8, 2006, at 9:39 AM, Oliver Hagmann wrote:
I just checked out the latest bundles and I get the following errors when using any of the new "show action" commands:
/Library/Application Support/TextMate/Bundles/GTDAlt.tmbundle/ Support/bin/GTD.rb:41:in `parse': Parse error on line: @email (RuntimeError) . This is not a line I recognize. from
As the error says, you have a line that just says "@email", and so the parsing system doesn't know what to do about it, since it lacks an action. I should probably have the parsing system should just ignore any lines it can't deal with, instead of raising an exception. Right now it basically stops processing whenever it finds a line it doesn't know about. What do you guys think is the best way?
Additionally, I found another bug: If I use the "Clean up current file" command, all the tabs before the actions get converted into spaces resulting in the "EOL + Action" command not inputting the same indent as in the line before (only with "soft tabs" set to *off*).
Should be fixed now. I was not checking for soft tabs at all, nor for the length of the tab spaces. I had hard-coded two spaces because that's what I am using.
Oliver
Haris
On Jul 8, 2006, at 11:05 AM, Charilaos Skiadas wrote:
On Jul 8, 2006, at 9:39 AM, Oliver Hagmann wrote:
I just checked out the latest bundles and I get the following errors when using any of the new "show action" commands:
/Library/Application Support/TextMate/Bundles/GTDAlt.tmbundle/ Support/bin/GTD.rb:41:in `parse': Parse error on line: @email (RuntimeError) . This is not a line I recognize. from
As the error says, you have a line that just says "@email", and so the parsing system doesn't know what to do about it, since it lacks an action. I should probably have the parsing system should just ignore any lines it can't deal with, instead of raising an exception. Right now it basically stops processing whenever it finds a line it doesn't know about. What do you guys think is the best way?
I like it throwing an error. It gives us information when our syntax is incorrect or that something in the code is amiss. So far every error I have had has either been one of those two and the developers have been great with fixes when I send them error reports when something does not work.
-Ron -- Ron Rosson oneinsanedotnet@gmail.com http://www.oneinsane.net
-
Charilaos Skiadas -
Oliver Hagmann -
Ron Rosson