<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#ffffff"> Rodolfo Carvalho wrote at 12/25/2011 09:33 PM:<br> <blockquote cite="mid:CANkx08i0Fg+ZgY0k9fjUOEgS5RbR1G8do-JTE+fqwyRk0j2UrQ@mail.gmail.com" type="cite"> <div class="gmail_quote">On Sun, Dec 25, 2011 at 01:03, Neil Van Dyke <span dir="ltr"><<a moz-do-not-send="true" href="mailto:neil@neilvandyke.org" target="_blank">neil@neilvandyke.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Matthew Flatt wrote at 12/24/2011 09:47 PM:<br> <div><br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> I'd also advocate short names --- `update' instead of `update-dev-links', say.<br>   <br> </blockquote> <br> </div> There will probably be a few different commands that start "raco mcfly update-".<span><font color="#888888"><br> <br> </font></span></blockquote> <div><br> <br> If there would be fuzzy-matching instead of unambiguous preffix matching, you could write "raco mcf u-d", and "raco mcf u-x"...<br> I'm thinking of something like Emacs' ido.el, but well, just for parsing raco commands now.<br> </div> </div> </blockquote> <br> I will try to have names that aren't too hard to type, and perhaps eventually rig up some Bash command completion.<br> <br> I think that a better place for "ido.el"-like completion might be in Bash (or whatever shell) itself.  It already has the necessary information.<br> <br> -- <br> <a class="moz-txt-link-freetext" href="http://www.neilvandyke.org/">http://www.neilvandyke.org/</a><br> <br> </body> </html>