I love this script, but I’m running into one problem… it doesn’t seem to take just a start date. I’ve tried using the sample, it works fine (once you remove the “20” from the year), then I remove the due date and the “-” and it doesn’t actually fail, it just doesn’t put in a start date.

Yup, looks like there’s a bug in the code there. Thanks for the catch! Just added a new task to my KGTD file to get this fixed.

For the time being, the syntax of task#startdate- does work, so you should be able to do that.

Either of two things happen when I use this script via QS:

1) it crashes QS 2) it forces me to switch to QS to use it, and won’t let me input anything in the field

Any suggestions? I’m using the latest QS and followed the ReadMe instructions.

Thanks

Thanks for the great script. But I cannot input Korean with this script. When I write in Korean, it just shows question marks instead of Korean. Can you fix it?

thanks

Sorry, Kumbal. The Satimage scripting library (which is necessary to parse the special syntax) doesn’t support Unicode, so all you can really pass to it is Roman characters. Any characters outside of that character set will be lost.

I’ve asked Satimage to update their scripting library to support Unicode, but it seems as though they aren’t too interested in doing that, since they also sell a Unicode-supporting scripting environment which can do everything their scripting addition can.

You aren’t the first to ask about this, and I wish I could make it work for you.

I’m having a slight issue with the script when setting it within a trigger in QS.

I have set “control-option-command-k” as a trigger to run the script but it doesn’t bring the input window to the top so that I can begin entering the command string immediately. This sort of defeats the purpose of it as I then have to select the input window using the mouse.

I’ve installed the latest version, three times, checked the locations of the scripts and re-launched QS but to no avail. It is highly likely that I’m missing something obvious but thought I’d drop you a line to see if you knew of anything.

It did work before the new version but used the QS interface as the input window. Not sure why it is different now. I actually preferred it this way as the text input window was larger and allowed you to see the complete command string at once.

I would just go back to the kinkless version but i really dig your syntax and the forcing of new projects/contexts.

cheers

nic

Well, if Quicksilver is in the background and runs the script, then yeah, that’s what’ll happen. I don’t know triggers from shinola (I’m a LaunchBar user, myself), but that’s what I’d expect to see.

I might recommend that you instead install FastScripts Lite and attach your keyboard command to the script there. FastScripts will ensure that all scripts’ dialogs come to the foreground.

thanks for the tip. I’ll let you know how it goes.

cheers,

nic

I’m currently using multiple kGTD documents (mostly for the sake of being able to set recursive actions) - and I can’t seem to get the QS script to send things to the right one.

1. How does the script determine “this document”? I’ve tried having the correct doc the only one open, the last one synced or saved - it still seems that the script has its own ideas.

2. Is there a way I can modify the script to only send to one document I specify? I have no programming experience, but I suppose that should be be too difficult.

Thanks!

Nic,
You CAN set the QS trigger so that it opens with the Input Window selected and active. Set your trigger with:

1. Nik’s Advanced script selected in the first pane,
2. Process Text… in the second pane, and
3. then the third pane will open for text input.

This might use a plug-in to work, probably Text Maniputlation Actions or Process Manipulation Actions.

Thanks for the tip Paul. All is now hunky-dory.

nic

What a wonderful script! It’s so efficient to use, I find myself using it even when already in kGTD.

I noticed that the adding of details was broken (perhaps during the rewrite of the parser?)

Anyway here’s a suggested one-line patch (tested): ” — Assign the details as a note, if details exist << if first item of detail of kArray is “new” then — Details are always new, never “match”

if first item of detail of kArray is not none then “

Debugging it showed that detail does have “match” as the first element, never “new”. It’s really nice code so was easy to find!

Cheers, Matt

Ugh, that came out formatted pretty badly. Meant to say:

if first item of detail of kArray is “new” then — Details are always new, never “match”

could be replaced with

if first item of detail of kArray is not none then

Thanks for the catch!

I moved the whole string parsing to a series of methods, whereas it used to be a one-off piece of code that always returned “new.” Looks like I forgot to update there. I’ll get a fix posted ASAP.

Hi, when I use “>NewProj” as the action fed to the script, I get the NewProj project created - but it shows up as greyed-out. Then when I try to create a new task for that NewProj, by using the full project name or trying to use matching (i.e. use “get something done>NewP”) it actually creates another new project named “NewP” with the task assigned to it.

So, how do I prevent the new project from being greyed out upon creation (without an associated new task)?

(I’m using 3.1)

Thanks.

Sync after creating the project then add the task. Alternately, do it all as one step (i.e. “new task > new project” rather than “> new project” followed by “new task > new proj”.

This script has been a wonderful tool for me. Thanks so much Nik for putting it together.

I am not an applescripter by any means, but it seems there should be a way for the script to automatically run the kGTD sync’ing after sending the info to kGTD. Any idea of how to do this? I imagine it’s a simpe as saying “run [location]sync.scpt” at the end, but I’m cluesless.

Thanks again.

Evan

Another user requested that and put it all together. You can find it somewhere in the Kinkless forums. I am not planning on adding that feature to the release version of the script — sync’ing takes way too long.

Hi - I’m getting the error above and The variable result is not defined via growl when trying to use the script. Any clues on how to fix?

Try sync’ing your KGTD file before running the script. It probably just can’t find the file.

Thanks Nik!

I can seem to figure out how to get this script to work similar to the default send to kGTD script. I want to follow the same work flow as the original — I would like to enter text first and then send it to the Sent to kGTD Advanced script.

From the readme: “(You can also start by entering text and then select this script in the second pane of Quicksilver, if you prefer.)”

When I invoke QS, I hit period to enter text, then tab. I am presented with the original Sent To script, but not the Advanced one.

I am able to invoke the script in QS, by choosing the script, enter text, process, etc.

Any ideas on how I can make this work per the readme above?

Thanks!

Sorry… One last question. For some reason OOP will not close when using the QS script.

OOP is closed to begin with. I invoke the script. It open OOP/kGTD and adds the item. But OOP doesn close.

Any idea how come.

Thanks, again.

Setting things up with Quicksilver can be a little funny. Be sure you put the script in the right directory (somewhere in Application Support — it’s in the docs), and you may need to manually refresh your catalog of commands. You may also need to swing a rubber chicken around while standing on one foot. QS is a little, well, persnickety in this regard.

Talk to your fellow QS’ers on the Blacktree forums or wherever for help. I’m a LaunchBar man, myself, so my knowledge is a little weak down QS way.

As for OOP not closing, that’s by design. I prefer to keep it open.

I managed to get QS to work (kinda). I’m not sure exactly what I did. Thanks.

In the last post your mentioned “As for OOP not closing, that’s by design. I prefer to keep it open.”

I guess I was confused b/c I saw this statement in the Readme…

“If it was closed to begin with, it will close itself again (thus pleasing the world’s neatness freaks).”

That’s why I thought it would close.

Thanks so much for the useful script.

The “it” in that sentence refers to your KGTD file, not to OmniOutliner. So I guess it just pleases some of the world’s neatness freaks. :)

OK. Got it. Thanks again, Nik. I appreciate your time and the script.

I use applescript (not QS) from the drop down menu to launch the Send to kGTD A (3.1 script. I understand that the syntax is task @ context, but how do I add the due date and the project name?

There is detailed documentation included with the script. It makes a handy reference.

But then that requires OmniOutliner Pro running in the foreground, doesn’t it? Or is there a way of avoiding that?

” Well, if Quicksilver is in the background and runs the script, then yeah, that’s what’ll happen. I don’t know triggers from shinola (I’m a LaunchBar user, myself), but that’s what I’d expect to see.

I might recommend that you instead install FastScripts Lite and attach your keyboard command to the script there. FastScripts will ensure that all scripts’ dialogs come to the foreground. “

But then that requires OmniOutliner Pro running in the foreground, doesn’t it? Or is there a way of avoiding that?

You can set up Nik’s script to process like the default Send to KGTD script. The only difference is that the text window is in the third pane, instead of the first. Set your trigger with:

1. Nik’s Advanced script selected in the first pane,
2. Process Text… in the second pane, and
3. then the third pane will open for text input.

When you invoke the trigger, the text entry pane will be active and ready for input.

This might require that a plug-in be installed, probably Text Maniputlation Actions or Process Manipulation Actions.

Johan,

If you set up the QS trigger the way I described to Jpepp above, the script and OOP will run in the background.

wholesale jewelry jewelry wholesale fashion jewelry handmade jewelry wholesale fashion jewelry wholesale costume jewelry costume jewelry wholesale pearl wholesale crystal

Interesting article! I read about this before. Thanks to author. Design is also pleased. Well, there are more things to read in the internet. Thank you. Plot Movie Mp3 Music Download Imdb Film Mp3 music downloads

Another user requested that and put it all together. You can find it somewhere in the Kinkless forums. I am not planning on adding that feature to the release version of the script sync’ing takes way too long. club penguin

burun estetiği and estetik burun ameliyatı: http://www.burunestetigi.tv/

I think I could use that script for some of my tasks. By the way, do you have any update on that script? Another thing, you mentioned about international characters. Did you mean it can support languages like Chinese, Japanese. dofollow bookmark

I think I could use that script for some of my tasks. By the way, do you have any update on that script? Another thing, you mentioned about international characters. Europe Cruise Deals

Thanks for sharing.I think i need to install Growl notification manager first to get this script work on my computer.

I just installed it, great work mate, i’ll let you know if i find bugs. Como hacer dinero rapido

I don’t know triggers from shinola (I’m a LaunchBar user, myself), but that’s what I’d expect to see.

since they also sell a Unicode-supporting scripting environment which can do everything their scripting addition can

if first item of detail of kArray is “new” then

Welcome to fotografia ślubna śląsk

Well, if Quicksilver is in the background and runs the script, then yeah, that’s what’ll happen. I don’t know triggers from shinola (I’m a LaunchBar user, myself), but that’s what I’d expect to see.

I don’t know triggers from shinola (I’m a LaunchBar user, myself), but that’s what I’d expect to see.

interesting article, totally agree with everything mentioned above.

I’m not an AppleScript by any means, but it seems that there must be a way for the script to run automatically after sync’ing kGTD send the information to kGTD. Any idea how to do this? I guess it’s a fairly simple as saying “run [place] sync.scpt” at the end, but I’m cluesless.