{% extends "base.html" %} {% block title %}X Resources (30){% endblock %} {% block content %}
NEdit has additional options to those provided in the Preferences menu which are set using X resources. Like most other X programs, NEdit can be customized to vastly unnecessary proportions, from initial window positions down to the font and shadow colors of each individual button (A complete discussion of how to do this is left to books on the X Window System). Key binding (see "Key Binding" is one of the most useful of these resource settable options.
X resources are usually specified in a file called .Xdefaults or .Xresources in your home directory (on VMS this is sys$login:decw$xdefaults.dat). On some systems, this file is read and its information attached to the X server (your screen) when you start X. On other systems, the .Xdefaults file is read each time you run an X program. When X resource values are attached to the X server, changes to the resource file are not available to application programs until you either run the xrdb program with the appropriate file as input, or re-start the X server.
The following are selected NEdit resource names and default values for NEdit options not settable via the Preferences menu (for preference resource names, see your NEdit preference file):
nedit.tagFile
: (not defined)nedit.alwaysCheckRelativeTagsSpecs
: True
nedit.wordDelimiters
: .,/\\`'!@#%^&*()-=+{}[]":;<>?
The set of characters which mark the boundaries between words. In addition to these, spaces, tabs, and newlines are always word boundaries.
These boundaries take effect for the move-by-word (Ctrl+Arrow) and select-word (double click) commands, and for doing regex searches using the \B, < and > tokens.
Note that this default value may be overridden by the setting in Preferences → Default Settings → Language Modes....
nedit.remapDeleteKey
: False
nedit.typingHidesPointer
: False
nedit.overrideDefaultVirtualKeyBindings
: Auto
Motif uses a virtual key binding mechanism that shares the bindings between different Motif applications. When a first Motif application is started, it installs some default virtual key bindings and any other Motif application that runs afterwards, simply reuses them. Obviously, if the first application installs an invalid set, all others applications may have problems.
In the past, NEdit has been the victim of invalid bindings installed by other applications several times. Through this resource, NEdit can be instructed to ignore the bindings installed by other applications, and use its own private bindings. By default, NEdit tries to detect invalid bindings and ignore them automatically (Auto). Optionally, NEdit can be told to always keep the installed bindings (Never), or to always override them (Always).
nedit.stdOpenDialog
: False
nedit.bgMenuButton
: ~Shift~Ctrl~Meta~Alt<Btn3Down>
nedit.maxPrevOpenFiles
: 30
nedit.printCommand
: (system specific)nedit.printCopiesOption
: (system specific)nedit.printQueueOption
: (system specific)nedit.printNameOption
: (system specific)nedit.printHostOption
: (system specific)nedit.printDefaultQueue
: (system specific)nedit.printDefaultHost
: (system specific)nedit.visualID
: Best
If your screen supports multiple visuals (color mapping models), this resource allows you to manually choose among them. The default value of "Best" chooses the deepest (most colors) visual available. Since NEdit does not depend on the specific characteristics of any given color model, Best probably IS the best choice for everyone, and the only reason for setting this resource would be to patch around some kind of X server problem. The resource may also be set to "Default", which chooses the screen's default visual (often a color-mapped, PseudoColor, visual for compatibility with older X applications). It may also be set to a numeric visual-id value (use xdpyinfo to see the list of visuals supported by your display), or a visual class name: PseudoColor, DirectColor, TrueColor, etc..
If you are running under a themed environment (like KDE or CDE) that places its colors in a shallow visual, and you'd rather have that color scheme instead of more colors available, then you may need set the visual to "Default" so that NEdit doesn't choose one with more colors. (The reason for this is: if the "best" visual is not the server's default, then NEdit cannot use the colors provided by your environment. NEdit will fall back to its own default color scheme.)
nedit.installColormap
: False
nedit.findReplaceUsesSelection
: False
nedit.stickyCaseSenseButton
: True
nedit.multiClickTime
: (system specific)nedit.undoModifiesSelection
: True
nedit*scrollBarPlacement
: BOTTOM_RIGHT
nedit*text.autoWrapPastedText
: False
nedit*text.heavyCursor
: False
nedit.autoScrollVPadding
: 4
nedit*text.blinkRate
: 500
nedit*foreground
: black
nedit*background
: #b3b3b3
nedit*calltipForeground
: black
nedit*calltipBackground
: LemonChiffon1
nedit*XmLFolder.inactiveForeground
: #666
nedit*fontList
: helvetica medium 12 points
nedit.helpFont
: helvetica medium 12 points
nedit.boldHelpFont
: helvetica bold 12 points
nedit.italicHelpFont
: helvetica italic 12 points
nedit.fixedHelpFont
: courier medium 12 points
nedit.boldFixedHelpFont
: courier bold 12 points
nedit.italicFixedHelpFont
: courier italic 12 points
nedit.h1HelpFont
: helvetica bold 14 points
nedit.h2HelpFont
: helvetica bold italic 12 points
nedit.h3HelpFont
: courier bold 12 points
nedit.helpLinkFont
: helvetica medium 12 points
nedit.helpLinkColor
: #009900
nedit.backlightCharTypes
: 0-8,10-31,127:red;9:#dedede;32,160-255:#f0f0f0;128-159:orange
NOTE: backlighting is experimental (see "Programming with NEdit").
A string specifying character classes as ranges of ASCII values followed by the color to be used as their background colors. The format is:
low[-high]{,low[-high]}:color{;low-high{,low[-high]}:color}
where low and high are ASCII values.
For example: 32-255:#f0f0f0;1-31,127:red;128-159:orange;9-13:#e5e5e5
nedit.focusOnRaise
: False
nedit.forceOSConversion
: True
By default, NEdit converts texts in DOS or Mac format to an internal format using simple newlines as line dividers. This is sometimes not wanted by the user and can be prevented by setting this resource to False.
Note: Setting this to False would supress newlines in Mac files entirely, leaving the control character <cr> where every line feed would be. Mac OS X uses Unix files and is not affected.
Note: Setting this to False while the option 'Terminate with Line Break on Save' is active could lead to file corruption.
nedit.truncSubstitution
: Fail
NEdit has a fixed limit on substitution result string length. This resource modifies the behaviour if this limit is exceeded. Possible values are Silent (will silently fail the operation), Fail (will fail the operation and pop up a dialog informing the user), Warn (pops up a dialog warning the user, offering to cancel the operation) and Ignore (will silently conclude the operation).
WARNING: Setting this to 'Ignore' will destroy data without warning!
nedit.honorSymlinks
: True
nc.autoStart
: True
nc.serverCommand
: nedit -server
nc.timeOut
: 10
Basic time-out period used in communication with an NEdit server (seconds).
The following are Selected widget names (to which you may append .background, .foreground, .fontList, etc., to change colors, fonts and other characteristics):
nedit*statsAreaForm
nedit*statsAreaForm*foreground
instead of: nedit*statsAreaForm.foreground
nedit*menuBar
nedit*textHorScrollBar
nedit*textVertScrollBar