Working directorySome macros have to know the directory in which they must be executed (for compilation by example). It means that you must use nc (or ncl, or nedit-nc, depending on your OS) instead of NEdit. Install get the tarball and copy it on your home directory so that you can see the file ~/.nedit/nedit.rc you need set the NEDIT_HOME environment variable to $HOME/.nedit General issueNEdit serverThis Nedit Macro-Kit fully work with the nedit-server binary. a powerful search and replace tool using the "grep" command.
This is my favorite! IDE features like compilation and jump to error line. Here is the feature list: completion (which can use dictionary, or tags file). Personally, I use them to write C++, python and LaTeX, but you can use them to code in any programming langages (Java, Perl, Html.). These macros are dedicated to all software developpers. Any comment/feedback/bug: use the Wiki or send me (Frank Perbet) an email at Brieflyold web page To use those macros you'll need NEdit version 5.4 or higher (to obtain the version number, use: nedit -V). Note for Windows user: NEdit requires Cygwin. Multi-language, Multi platform, easy to configure, featuring functionalities like the "expander", completion, ctags dialog, comment/uncomment, build and jump to error, multiple files search&replace. NEdit Macro for programmers, basically turning the NEdit text editor into a full-featured IDE.
0 kommentar(er)
