I may be unusual in this, but I often write several fairly lengthy docstrings in each namespace.
CCW 0.28.1.STABLE001's editor seems to get *very* slow when typing in the latest such docstring if there are many others and the line number is getting up into the upper three digits/lower thousands. It can end up taking nearly a second to display each new character, and easily nearly a minute to catch up to a bunch of typing, once it gets into this state, even when run on a state-of-the-art development box with 8GB RAM and a 3GHz, 64-bit CPU and little else demanding either of these resources. The syntax highlighting is the likely culprit. I think the rendering of the dark red background of incomplete string literals may have something to do with it, as editing the same string later on is *much* faster if the edit is in the middle, but if it's at the end and is done by deleting the closing quotation mark, writing more, and eventually adding a new closing quotation mark, it's slow again. It can be worked around by typing a close quotation mark on a line by itself beneath the docstring and then typing in the docstring, but this is counterintuitive. The user should not be penalized for just writing their function linearly: (defn foo "start typing docstring in... -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
