On Wednesday 05 March 2008 09:31 pm, Aaron Hsu wrote: ---< good stuff snipped >--- > Which brings up another thing to beware of. When creating these code > folding routines, it should not break existing macros which scan through > and check for pieces. That is, you should be able to scan through the > folded code even though it's not shown, if so desired. You should also > be able to skip over it. > > To give a practical example, I might rebind the delete or ( and ) keys > on my keyboard to do pseudo-structured editing based on the context. If, > that macro needs to track the depth of its parentheses, it can either > assume that all parentheses are balanced inside a fold (which is okay) > or it may need to go into that fold to make sure that things are alright.
Understood (I think ;-) I think that's sort of analogous to my thinking about things like search and/or replace, and/or the ability for editing operations to operate on the visible portions of the text only or on the entire document. A point to not forget. Randy Kramer -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
