Ok, so what you really want is not to change how your program functions, but how your IDE/editor functions. That means what you really want is not a clojure macro, but an emacs macro--you want to extend the functionality of emacs to make your editing easier. The clojure code you write is not going to achieve what you want (though it may help you in learning how to write Emacs macros). I know enough about elisp to customize it so that it throws error messages every time I start it up, so I'll bow out here, but that's where you need to go from here.
Cheers. Mark On Sat, Jun 4, 2011 at 1:15 AM, nil <ache...@gmail.com> wrote: > Mark, it turns out that everything I need is known and static at hack- > time. (Sorry for making it sound otherwise) I know all the names, > values, *and* behaviors that I want to use when I'm writing the code > for my tests. I just want my clojurebox symbol completion to work > after having written a bunch of one-liners to declare families of > functions. I think it forces me to eval certain files before I edit > others. Am I making you all cringe? > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
