NEDIT FREQUENTLY ASKED QUESTIONS--------------------------------Version 2001/10/01NEdit is a popular GUI-style text editor for Unix and VMS systems. Theseare answers to the most frequently asked questions to discuss@nedit.org.This information is also available from:    ftp://ftp.nedit.org/pub/<current>/FAQ,and from the NEdit web page at:    http://nedit.org.FAQ Maintainers: Florian Xhumari (Florian.Xhumari@free.fr)ABOUT THE NEDIT FAQ-------------------This FAQ is written in XML and translated to HTML using an XSL stylesheet.The XML source is processed using James Clark's (http://www.jclark.com/)XSLT processor XT (http://www.jclark.com/xml/xt.html) and XML parser XP(http://www.jclark.com/xml/xp).The XSL stylesheet used to generate the HTML version is here (faq.xsl).The text version is generated in three steps: first, an XSL stylesheet(faq-txt.xsl) is used to generate a simple HTML. Then, a second XSLstylesheet (faq-txt-pass2.xsl) transforms the HTML into plain text. An awkscript (faq-txt.awk) then performs the word wrapping.For any questions about or contributions to the FAQ, please send a mail tothe maintainers (mailto:Florian.Xhumari@free.fr).WHERE TO GET INFORMATION------------------------> Where can I get information about NEdit?The NEdit web page is at:    http://nedit.organd it is mirrored in Australia at:    http://www.au.nedit.org/The primary ftp site for NEdit is:    ftp://ftp.nedit.org/pubwhich has a mirror in The Netherlands:    ftp://ftp.nl.nedit.org/pub/mirror/NEditThe NEdit ftp site has executables for most Unix and VMS systems, sources,documentation, and contributed software.The first and easiest place to look for help with NEdit is the NEdit Helpmenu. The bottom item in the menu (Problems/Bugs) has answers to the mostcommonly asked questions about NEdit, which are not duplicated here. Alsocheck the platform specific information in the README file packaged in theNEdit distribution kits.If you have a problem that you really can't figure out, send mail todiscuss@nedit.org, and see if anyone else might be having the same trouble.The nedit developers also subscribe to this list, and hopefully someonewill be able to answer your question. If you are a Silicon Graphics userand NEdit came bundled on your system, you can also contact SGI's technicalsupport.> Are there any mailing lists for NEdit users?There are two separate mailing lists for nedit users, and one fordevelopers. Users may post to the developer mailing list to report bugs andcommunicate with the nedit developers.The lists are:    * discuss@nedit.org: general discussion, questions and answers among    nedit users and developers.    * develop@nedit.org: communication among and with nedit developers.    Developers should also subscribe to the discuss list.    * announce@nedit.org: a low-volume mailing list for announcing new    versions.Please note that only subscribers can send mail to the list.The nedit developers subscribe to both discuss@nedit.org anddevelop@nedit.org, either of which may be used for reporting bugs. Ifyou're not sure, or you think the report might be of interest to thegeneral nedit user community, send the report to discuss@nedit.org. If it'ssomething obvious and boring, like we misspelled "anemometer" in theon-line help, send it to develop@nedit.org.Please do not cross post to both lists!In order to subscribe to a list, send mail to majordomo@nedit.org with oneor more of the following in the body of the message:    subscribe announce    subscribe discuss    subscribe developTo unsubscribe do the same with the keyword unsubscribe.    unsubscribe announce    unsubscribe discuss    unsubscribe developAfter subscribing, you will receive copies of all of the email submitted tothe lists. You may submit mail to the discussion list by sending it to theappropriate list: discuss@nedit.org, develop@nedit.org orannounce@nedit.org.The archives of the old mailing lists (nedit_discuss@fnal_gov andnedit_announce@fnal.gov) can be found on egroups.com:        * http://www.egroups.com/group/nedit_discuss/        * http://www.egroups.com/group/nedit_announce/For more information about the mailing lists, refer to the mailing listssection (http://nedit.org/community/mailing.shtml) in the NEdit site.> Where can I get binaries / executables for machines other than those> available at NEdit site?In past versions, we separated "supported" and "unsupported" executablesand divided them between the binary and contrib directories. With moresupported systems, you're less likely to find executables in the contribdirectory, but it's worth a peek, anyhow. If you can't find anythingappropriate, you can try asking in a usenet news group appropriate to yoursystem. Other places to try are, the discuss@nedit.org mailing list, ornews:comp.windows.x.apps or news:comp.editors.> What can I contribute?If you use and enjoy NEdit, and feel like giving something back to theNEdit user community, contact develop@nedit.org. If you have ported NEditto a new machine, written a useful set of macros, or would like tocontribute to an ongoing development project, we'd love to hear from you.DIAGNOSING AND REPORTING PROBLEMS---------------------------------> How do I report problems I've encountered using NEdit ?If you have a problem which is not covered in the on-line help, in thisFAQ, or in the README file specific to your system, you can report it todiscuss@nedit.org (usage questions) or, develop@nedit.org (error reports).Note that these lists only allow members to post, and if you are not amember, your post will probably de delayed in reaching the list.Alternatively you can use the bug tracker on Sourceforge(http://sourceforge.net/projects/nedit/) to report bugs and make featurerequests. Below are some suggestions for information you can provide tohelp in diagnosing your problem.Because NEdit runs on a large number of different platforms andenvironments, many problems are platform-specific. It's always helpful toknow what kind of system it's being run on. Sometimes, strange behavior canalso be traced to the X server software or window manager, so you may wantto include information on these as well.The origin of the NEdit executable is often important, particularly,whether it came from the NEdit site (http://www.nedit.org), was builtlocally, or came from some other ftp server or freeware distribution CD.Despite the fact that Motif appears on almost all Unix platforms, the Motiflibraries still vary from one machine to another. Be sure to mentionwhether you're using Lesstif or Motif. As of version 5.2 a summary withbuild information is present under 'Version' in the Help menu.If you are having configuration or appearance problems, you should probablylook at the output from the command:   appres NEdit neditThe 'appres' command will show you the resources that NEdit actually seeswhen it runs, including "stray" resources intended for other programs butnot properly qualified by the program name. It will also give you a finalobjective check as to whether resource settings that you have made areactually readable by NEdit.BUILDING--------> When I build NEdit on my SunOS system, I get the fillowing undefined> symbols:> > ld: Undefined symbol>    _memmove>    _atexit>    _strerror> *** Error code 1> make: Fatal error: Command failed for target `nedit'Older versions of the gcc C runtime library were missing these functions.You can either upgrade gcc, or get sources for these functions fromftp://ftp.nedit.org/pub/contrib/misc (which someone else with your verysame problem kindly contributed).> I'd like to build NEdit, but my system seems to be missing the Xm...> include files and libXm.aXm means Motif, which is an important part of NEdit's GUI interface. Motifis standard on commercial Unix workstations, but not on free Unix platformslike Linux and FreeBSD. On these systems, you can now use LessTif, the GPLclone of Motif, or purchase a copy of Motif, which is usually relativelyinexpensive, but not free. You can find a list of companies selling Motiffor Linux at:    http://www.cen.com/mw3/#providersAs of this writing LessTif is very close to being a fully reliable andcomplete replacement for Motif, so it's definitely worth trying beforeshelling out any money for a commercial copy. Also remember that in mostcases, you don't really need Motif libraries to use NEdit. There are plentyof versions available pre-built with the Motif libraries linked instatically. If you can't find one for your system, ask around, and you mayfind that someone else has already built one for you. Motif licensingallows free distribution of statically linked binaries. Executables forNEdit are available fromftp://ftp.nedit.org/pub/<current-version>/executables.> When I build NEdit, I get the yacc error:> >   conflicts: 36 shift/reduceThat's normal. NEdit's macro language has a very conflicted grammar, butthe conflicts all resolve themselves correctly. The conflicts stem fromallowing awk-style no-operator concatenation of strings.> I built NEdit on my Linux system, and it's full of bugs. What a horrible> editor!Several of the Linux distributions began including LessTif (a free versionof the Motif GUI library) before it was really ready for general use(particularly for something which needs to be as reliable as a texteditor). If you have a version of Lesstif prior to 0.92.26, you have toupgrade it, before it will support NEdit reliably. To get the newestversion, go to http://lesstif.org. Alternatively, you can get pre-built,statically linked, executables fromftp://ftp.nedit.org/pub/<current-version>/executables.> While compiling NEdit on Linux, I get the following warning:> >     file.o: In function `PrintString':>     file.o(.text+0x17b7): the use of `tmpnam' is dangerous, better use `mkstemp'> > Is NEdit insecure?Not if you are using the glibc. The algorithm of mkstemp(3) consists of twoparts: the first part is the one used in tmpnam(3) -- this is what NEditaccomplishes by calling tmpnam(3); the second part is done directly inNEdit.> NEdit fails to build on Linux, with messages> >    undefined reference to `XpGetDocumentData'>    undefined reference to `XpGetPageDimensions'>    ...Edit makefiles/Makefile.Linux, and add '-lXp' to the line starting with'LIB', right before '-lXext'. At this time we are not sure whether libXp(the X print library) is installed on all Linux systems.CUSTOMIZATION-------------