Also, it's worth noting that my trick to highlight def-initions probably isn't going to work if we have hierarchical parsing of S- expressions. I'm not entirely sure how jEdit is going to handle certain cases if we try to merge the two. It might be possible to make it work, but I suspect that jEdit's greedy matching will get in the way.
Daniel On Dec 16, 1:22 am, Daniel Spiewak <djspie...@gmail.com> wrote: > > I been thinking about this during the weekend, and I think I prefer the mode > > to be aware of nesting (unless you can cause it to blow the stack on a large > > Well, this would be my question: why? :-) Auto-indent needs to be > aware of nesting, but that's already handled in a separate pass from > the highlighting. Besides that, there really isn't anything that > requires this sort of complexity. Also, as you say, it does tend > toward far less efficient highlighting in more deeply-nested S- > expressions. > > > Will let you know when done (sometime later this week or so) so that you can > > have a look. I'm also thinking that regexps should have some highlighting... > > I may even push that into the Perl mode as it pisses me off greatly that > > regexps don't even know about variable substitution. > > Proper regexp highlighting would be nice, but as I mentioned, I'm not > sure what the "correct" way to handle this may be. Are regular > expressions actually handled specially in the reader? If not, then we > should probably just reuse the string highlighting semantics. > > Daniel --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
