> > * A.V.Kuznetsov wrote (2008-01-15 11:37): > >> Comment By: Thorsten Haude (yooden) > >> There is no problem with manViewer.nm. Just don't pick a single file from > >> a set of files and expect it to work. The function you are missing is > >> provided in util.nm (which is also autoloaded). The whole idea is to > >> provide a coordinated set, not just a bunch of single files; you can have > >> plenty of those from somewhere else. So of course I put library functions > >> in their own module to advocate reuse. Of course I add menu items because > >> easy access to external macros is what NEdit is lacking. > > > >I am not sure that the main stream is optimal, seems consolidated macros are > >better for the release tarball. User (if he want) can easily look code to > >understand it. Relatively simple macro showing a man page is splitted into > >4 pieces located at 3 files. That looks strange for me. > > I would agree to provide a single-file solution; that's not possible > with NEdit's current setting system however. > > With the current split setup, we demonstrate that NEdit is fully able > to cover the concept of modules, we promote reuse of the library > functions and we demonstrate good coding practices. Putting all > dependencies in one file would break High Cohesion. > > > >> I provided some explanation in the tarball's README. Please let me know > >> how to improve the text. And please, let's work on merging the two man > >> viewers. (And after that, maybe the two spell checker.) > > > >Let us consolidate nMan into single macro and then merge nMan and neman. > > Sorry, we simply cannot do that, NEdit does not allow it. There has > got to be a part of the macro in the menu; I'm not aware of a way to > define macro menu entries from a macro. So why would the macro as a > whole be better, if we change the required menu entry to something > nondescript? > > To put it another way, I could put the GUI part of my version into the > macro file (let's call it nManGUI()) to get something similar to your > version. However, I'd still have to add nManGUI() to the menu by hand. > > Also, I don't think to factor the getManSection() back in would help > anyone. Let's keep different things apart here. > > > Thorsten
Hi Thorsten, manViewer and neman provide similar (practically identical) interface for man page selecting and differ mainly by man output coloring. manViewer via rangesets backlights strictly that the man developer marked. neman via highlighting tries to mark object often used in manuals like command options, paths, urls, strings and so on. There is no strict syntax for man page content so such a highlighting is very imperfect I prefer highlighting to backlighting while somebody prefer a counter. In this context, nMan and neman fill up each other, there is no need to merge them. Let hundred flowers be in blossom, as Mao said. Using manViwer, one can add highlighting patterns from Niki http://nedit.hackvalue.nl/niki/index.php/ManOutputHighlighting This set also provides new "Manual" language mode so user can turn on it and add highlighting to backlighting provided by the manViewer. Alexey -- NEdit Develop mailing list - [email protected] http://www.nedit.org/mailman/listinfo/develop
