help.etx

nedit 是一款linux下的开发源码的功能强大的编辑器

-----------------

  Programmers who use structured languages usually require some form of
  automatic indent, so that they don't have to continually re-type the
  sequences of tabs and/or spaces needed to maintain lengthy running indents. 
  NEdit therefore offers "smart" indent, in addition to the traditional
  automatic indent which simply lines up the cursor position with the previous
  line.

3>Smart Indent

  Smart indent macros are only available by default for C and C++, and while
  these can easily be configured for different default indentation distances,
  they may not conform to everyone's exact C programming style.  Smart indent
  is programmed in terms of macros in the NEdit macro language which can be
  entered in: Preferences -> Default Settings -> Indent -> Program Smart
  Indent.  Hooks are provided for intervening at the point that a newline is
  entered, either via the user pressing the Enter key, or through
  auto-wrapping; and for arbitrary type-in to act on specific characters typed.

  To type a newline character without invoking smart-indent when operating in
  smart-indent mode, hold the Shift key while pressing the Return or Enter key.

3>Auto-Indent

  With Indent set to Auto (the default), NEdit keeps a running indent.  When
  you press the Return or Enter key, spaces and tabs are inserted to line up
  the insert point under the start of the previous line.

  Regardless of indent-mode, Ctrl+Return always does the automatic indent;
  Shift+Return always does a return without indent.

3>Block Indentation Adjustment

  The Shift Left and Shift Right commands as well as rectangular dragging can
  be used to adjust the indentation for several lines at once.  To shift a
  block of text one character to the right, select the text, then choose Shift
  Right from the Edit menu.  Note that the accelerator keys for these menu
  items are Ctrl+9 and Ctrl+0, which correspond to  the right and left
  parenthesis on most keyboards.  Remember them as adjusting the text in the
  direction pointed to by the parenthesis character.  Holding the Shift key
  while selecting either Shift Left or Shift Right will shift the text by one
  tab stop (or by one emulated tab stop if tab emulation is turned on).  The
  help section "Shifting and Filling" under "Basic Operation" has details.
   ----------------------------------------------------------------------

Syntax Highlighting
-------------------

  Syntax Highlighting means using colors and fonts to help distinguish language
  elements in programming languages and other types of structured files. 
  Programmers use syntax highlighting to understand code faster and better, and
  to spot many kinds of syntax errors more quickly.

  To use syntax highlighting in NEdit, select Highlight Syntax in the
  Preferences menu.  If NEdit recognizes the computer language that you are
  using, and highlighting rules (patterns) are available for that language, it
  will highlight your text, and maintain the highlighting, automatically, as
  you type.

  If NEdit doesn't correctly recognize the type of the file you are editing,
  you can manually select a language mode from Language Modes in the
  Preferences menu.  You can also program the method that NEdit uses to
  recognize language modes in Preferences -> Default Settings -> Language
  Modes....

  If no highlighting patterns are available for the language that you want to
  use, you can create new patterns relatively quickly.  The Help section
  "Highlighting_Patterns_" under "Customizing", has details.

  If you are satisfied with what NEdit is highlighting, but would like it to
  use different colors or fonts, you can change these by selecting Preferences
  -> Default Settings -> Syntax Highlighting -> Text Drawing Styles. 
  Highlighting patterns are connected with font and color information through a
  common set of styles so that colorings defined for one language will be
  similar across others, and patterns within the same language which are meant
  to appear identical can be changed in the same place.  To understand which
  styles are used to highlight the language you are interested in, you may need
  to look at "Highlighting_Patterns_" section, as well.

  Syntax highlighting is CPU intensive, and under some circumstances can affect
  NEdit's responsiveness.  If you have a particularly slow system, or work with
  very large files, you may not want to use it all of the time.  Syntax
  highlighting introduces two kinds of delays.  The first is an initial parsing
  delay, proportional to the size of the file.  This delay is also incurred
  when pasting large sections of text, filtering text through shell commands,
  and other circumstances involving changes to large amounts of text.  The
  second kind of delay happens when text which has not previously been visible
  is scrolled in to view.  Depending on your system, and the highlight patterns
  you are using, this may or may not be noticeable.  A typing delay is also
  possible, but unlikely if you are only using the built-in patterns.
   ----------------------------------------------------------------------

Finding Declarations (ctags)
----------------------------

  NEdit can process tags files generated using the Unix _ctags command or the
  Exuberant Ctags program.  Ctags creates index files correlating names of
  functions and declarations with their locations in C, Fortran, or Pascal source
  code files. (See the ctags manual page for more information).  Ctags produces a
  file called "tags" which can be loaded by NEdit.  NEdit can manage any number
  of tags files simultaneously.  Tag collisions are handled with a popup menu to
  let the user decide which tag to use.  In 'Smart' mode NEdit will automatically
  choose the desired tag based on the scope of the file or module. Once loaded,
  the information in the tags file enables NEdit to go directly to the
  declaration of a highlighted function or data structure name with a single
  command.  To load a tags file, select "Load Tags File" from the File menu and
  choose a tags file to load, or specify the name of the tags file on the NEdit
  command line:

      nedit -tags tags

  NEdit can also be set to load a tags file automatically when it starts up. 
  Setting the X resource nedit.tagFile to the name of a tag file tells NEdit to
  look for that file at startup time (see "Customizing_NEdit_").  The file name
  can be either a complete path name, in which case NEdit will always load the
  same tags file, or a file name without a path or with a relative path, in
  which case NEdit will load it starting from the current directory.  The
  second option allows you to have different tags files for different projects,
  each automatically loaded depending on the directory you're in when you start
  NEdit.  Setting the name to "tags" is an obvious choice since this is the
  name that ctags uses. NEdit normally evaluates relative path tag file
  specifications every time a file is opened. All accessible tag files are
  loaded at this time. To disable the automatic loading of tag files specified
  as relative paths, set the X resource nedit.alwaysCheckRelativeTagsSpecs to
  False.

  To unload a tags file, select "Un-load Tags File" from the File menu and
  choose from the list of tags files.  NEdit will keep track of tags file updates
  by checking the timestamp on the files, and automatically update the tags
  cache. 

  To find the definition of a function or data structure once a tags file is
  loaded, select the name anywhere it appears in your program (see 
  "Selecting_Text_") and choose "Find Definition" from the Search menu.
   ----------------------------------------------------------------------

Calltips
--------
  
  Calltips are little yellow boxes that pop up to remind you what the arguments
  and return type of a function are.  More generally, they're a UI mechanism to
  present a small amount of crucial information in a prominent location.  To 
  display a calltip, select some text and choose "Show Calltip" from the Search
  menu.  To kill a displayed calltip, hit Esc.
  
  Calltips get their information from one of two places -- either a tags file (see
  "Finding_Declarations_(ctags)_") or a calltips file.  First, any loaded calltips 
  files are searched for a definition, and if nothing is found then the tags 
  database is searched.  If a tag is found that matches the hilighted text then
  a calltip is displayed with the first few lines of the definition -- usually 
  enough to show you what the arguments of a function are.
  
  You can load a calltips file by using choosing "Load Calltips File" from the
  File menu.  You can unload a calltips file by selecting it from the 
  "Unload Calltips File" submenu of the File menu.  You can also choose one or
  more default calltips files to be loaded for each language mode using the 
  "Default calltips file(s)" field of the Language Modes dialog.
  
  The calltips file format is very simple.  calltips files are organized in blocks
  separated by blank lines.  The first line of the block is the key, which is the
  word that is matched when a calltip is requested.  The rest of the block is
  displayed as the calltip.  
  
  Almost any text at all can appear in a calltip key or a calltip.  There are no
  special characters that need to be escaped.  The only issues to note are that
  trailing whitespace is ignored, and you cannot have a blank line inside a
  calltip.  (Use a single period instead --  it'll be nearly invisible.)  You should
  also avoid calltip keys that begin and end with '@*' characters, since those are
  used to mark special blocks.

  There are five special block types--comment, include, language, alias, and 
  version--which are distinguished by their first lines, "@* comment @*", 
  "@* include @*", "@* language @*", "@* alias @*", and "@* version @*" respectively 
  (without quotes).

  Comment blocks are ignored when reading calltips files.

  Include blocks specify additional calltips files to load, one per line.  The ~
  character can be used for your $HOME directory, but other shell shortcuts like
  @* and ? can't be used. Include blocks allow you to make a calltips file for your
  project that includes, say, the calltips files for C, Motif, and Xt.

  Language blocks specify which language mode the calltips should be used with. 
  When a calltip is requested it won't match tips from languages other than the
  current language mode.  Language blocks only affect the tips listed after the
  block.

  Alias blocks allow a calltip to have multiple keys.  The first line of the block
  is the key for the calltip to be displayed, and the rest of the lines are
  additional keys, one per line, that should also show the calltip.

  Version blocks are ignored for the time being.

  You can use calltips in your own macros using the calltip() and kill_calltip()
  macro subroutines and the $calltip_ID macro variable.  See the 
  Macro_Subroutines_ section for details.
   ----------------------------------------------------------------------
  
Regular Expressions
===================

Basic Regular Expression Syntax
-------------------------------

  Regular expressions (regex's) are useful as a way to match inexact sequences
  of characters.  They can be used in the `Find...' and `Replace...' search
  dialogs and are at the core of Color Syntax Highlighting patterns.  To specify
  a regular expression in a search dialog, simply click on the `Regular
  Expression' radio button in the dialog.

  A regex is a specification of a pattern to be matched in the searched text. 
  This pattern consists of a sequence of tokens, each being able to match a
  single character or a sequence of characters in the text, or assert that a
  specific position within the text has been reached (the latter is called an
  anchor.)  Tokens (also called atoms) can be modified by adding one of a number
  of special quantifier tokens immediately after the token.  A quantifier token
  specifies how many times the previous token must be matched (see below.)

  Tokens can be grouped together using one of a number of grouping constructs,
  the most common being plain parentheses.  Tokens that are grouped in this way
  are also collectively considered to be a regex atom, since this new larger
  atom may also be modified by a quantifier.

  A regex can also be organized into a list of alternatives by separating each
  alternative with pipe characters, `|'.  This is called alternation.  A match
  will be attempted for each alternative listed, in the order specified, until a
  match results or the list of alternatives is exhausted (see Alternation_
  section below.)

3>The 'Any' Character

  If a dot (`.') appears in a regex, it means to match any character exactly
  once.  By default, dot will not match a newline character, but this behavior
  can be changed (see help topic Parenthetical_Constructs_, under the
  heading, Matching Newlines).

3>Character Classes

  A character class, or range, matches exactly one character of text, but the
  candidates for matching are limited to those specified by the class.  Classes
  come in two flavors as described below:

     [...]   Regular class, match only characters listed.
     [^...]  Negated class, match only characters NOT listed.

  As with the dot token, by default negated character classes do not match
  newline, but can be made to do so.

  The characters that are considered special within a class specification are
  different than the rest of regex syntax as follows. If the first character in
  a class is the `]' character (second character if the first character is `^')
  it is a literal character and part of the class character set.  This also
  applies if the first or last character is `-'.  Outside of these rules, two
  characters separated by `-' form a character range which includes all the
  characters between the two characters as well.  For example, `[^f-j]' is the
  same as `[^fghij]' and means to match any character that is not `f', `g',
  `h', `i', or `j'.

3>Anchors

  Anchors are assertions that you are at a very specific position within the
  search text.  NEdit regular expressions support the following anchor tokens:

     ^    Beginning of line
     $    End of line
     <    Left word boundary
     >    Right word boundary
     \B   Not a word boundary

  Note that the \B token ensures that the left and right characters are both
  delimiter characters, o