Bryan Goldstein

That sounds good. I would definitely be up for building a tokenizer, as long as it scales well I think it could be great. I think being able to have...

``` ruby class Copy < Token argument source: FileInstance argument destination: DirectoryInstance, question: 'Where would you like to copy it to?' statement 'copy', :source, 'to', :destination statement 'copy', :source, ask:...

:+1: Okay, I will start implementing this refactor at some point this week and throw it on a branch.

How would you feel about doing something like this?: ``` ruby argument copy: WordExpansion statement :copy, :source, 'to', :destination ``` Meanwhile, in `WordExpansion` land... ``` ruby class WordExpansion < Token...

Never mind on the above for now. I started implementing it and realized that we probably want to start by just making all the arguments a `SimpleMatcher` type to get...

Right now I am moving the `find` command over to the style we talked about above. I will submit a pull when I have it in some working order that...

I didn't forget about this... After my experiment with the pull request above I decided it might be easier to go with semr after all. Check out mdeiters/semr#1

I think that having super cool configuration to read would be awesome, but I think the simplest approach at first would be allowing the user to edit the existing code...

I think the regexes are a great start. I think that as people start adding new commands and wanting to change the existing ones, a parser with some shared capabilities...

That could be really useful, she could keep a log of user preferences. It would also be cool if you could tell betty you want to do something, but not...