Bert, Thanks! (Some comments below.)
On Monday 17 March 2008 03:18 pm, Bert Wesarg wrote: > On Mon, Mar 17, 2008 at 2:55 PM, Randy Kramer <[EMAIL PROTECTED]> wrote: > > * modified_rangeset_hook: which would be called after a rangeset is > > modified (and it should report what has changed) > the current hooks I use take no arguments, its only the 'event' that > bothered me, not exactly what happened (like in the modified or > cursor_moved events) > > Thats exactly what is needed to be done: identify hooks/events and the > information what these should carry. Starting a small list: * modified_hook--modify it to report what has changed in the textBuf * modified_rangeset_hook--should report the change(s) (additions, deletions, locations) * cursor_moved event--should report the change (i.e., the new location) * selection_change hook--should report the new selections * scroll_change hook--should report the new scroll position (is that the top line (or the first character) in the display?) I suspect I'll think of more. On the other hand, if we (someone) writes the backend changes necessary for folding in C, then, presumably, these won't be required. Randy Kramer PS: A few minutes ago I checked the GSoC website to see if the list of mentoring organizations has been posted yet--not so far (was supposed to happen at noon, PDT (1900 UTC)). -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
