But that doesn't seem to do the trick. I seem to have a lot of other .exe programs that I run on a regular basis that take parameters. How can I do this? Been looking around in the forum and on the docs, but I must be blind.

Thanks a ton. Awesome tool! Hopefully will be giving some scripts back to the community soon.

Second, that alias you specified should work fine -- i think it's important for you/me/us to figure out why its not working properly if it isnt. Can you tell me any more symptoms, like is it launching the program but without arguments, or not launching it at all.

Third, people have been requesting an easier way to pass parameters to a tool for a while now, and i think it's time for me to add it. The idea that i think we settled on for how to do this is to allow some way to express on the search line that you want to pass extra paramaters to the launched program, like: "search terms :: param1 param2" that would tell far that whatever you type after the :: should be passed as commandline parameters. Thoughts?

Well, seems like the machine needed a restart I haven't changed anything and the alias does work as expected, as in, it does bring up the Remote desktop tool with the appropriate machine.

I like your idea of having some sort of string that can be used to specify arguments. Personally, I have a lot of these programs that I need to pass parameters to, and making an alias for each of them has been a bit annoying. I have managed to make it work though. I'm wondering if making the string be "$$" instead of "::" would make it more obvious, as "$$" is already used as a prefix to the parameters.

Well, it seems like I wasn't crazy in the head after all. The remote desktop alias that I described in the original post is a real issue. It is intermitent, and I have not been able to pin down the environment under which it fails and the one under which it works. As of this writing it has gone back to "not working", and nothing in the config has changed that would seem to make this happen. Any tips on how I can provide more data to aid debbugin?

Works fine iff you change %SystemRoot% to C:\Windows\ or equivalent for your system. Clearly it should work with the environment variable but as a temporary solution I guess you should just use the absolute path, or is it not possible?

Third, people have been requesting an easier way to pass parameters to a tool for a while now, and i think it's time for me to add it. The idea that i think we settled on for how to do this is to allow some way to express on the search line that you want to pass extra paramaters to the launched program, like: "search terms :: param1 param2" that would tell far that whatever you type after the :: should be passed as commandline parameters. Thoughts?

Some way of passing commandline parameters is really needed. Perhaps launchy's method is the most intuitive one. Pressing Tab would add a special visual separator (a triangle if I recall correctly) behind the text in the searchbox and you could write any parameters needed. Now, since Tab is used to autocomplete there should be a check to see if currently selected item in the result list is executable or not before deciding what would be done (autocomplete or take commandline parameters).