Quoting Thorsten Haude <[EMAIL PROTECTED]>: > This is why I wrote that the RSI might be a bit intimidating. I wrote > this before I even had a closer look at the code (which I still > hadn't), just because it's 7k of manual. For this purpose, eg. a 'Find > All' and a 'Show Changes', each with some bells and whistles seems to > be a much better choice. All it should say is: "Look this is what you > could do with rangesets!"
I tend to agree with this: for rangesets I would supply a "find all", a "mark with rangeset" (add the selection to a rangeset, like a marker pen function), a "goto marked range" (to find one marked area among the many in the rangeset), and the "diff current document against the last stored file". These are essentially the functions I wanted when I first wrote the RS code, and I think they would allow users to learn how to roll their own. Adding the man page rangesets would be a nice-to-have but is not essential. (I like the way Joerg does this BTW!) I wouldn't go overboard in defining a huge number of rangeset function for managing many rangesets (like I have - and use often!) for this: let the new user learn (and provide a purpose to the future nedit resource repository). > (Now while I wrote the above I clicked a bit through the RSI; I think > you could do nice things with externally stored rangesets and a hook > which loads them. Neat.) Hold on there, Thorsten! Don't get carried away! Personally, I write many macros with rangesets, quite often simply to track what my macros are doing at any point in time. As for a "macro development environment", I also use an on-demand macro file loader (it's been around for ages and hasn't changed much since it was added to Marc's list). It means that the number of changes you need to make when you add a new macro from your new macro sourcecode file to your menu are limited to the menu entry itself: you write an extra function call to make sure the file has been loaded. If Joerg's version is ligher-weight than mine, it sounds like a good candidate for inclusion in the macro set (maybe directly coded into autoload.nm). Tony -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
