faq.xml

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

<title>Building</title>


<qna id="N162">

<q>
When I build NEdit on my SunOS system, I get undefined
symbols: <tt>_memmove</tt>, <tt>_atexit</tt>,
<tt>_strerror</tt>.
</q>

<long-q>

<p>When I build NEdit on my SunOS system, I get the fillowing undefined
symbols:</p>

<pre>
ld: Undefined symbol
   _memmove
   _atexit
   _strerror
*** Error code 1
make: Fatal error: Command failed for target `nedit'
</pre>

</long-q>

<a>

<p>Older versions of the gcc C runtime library were missing these functions.  You
can either upgrade gcc, or get sources for these functions from
<site>ftp://ftp.nedit.org/pub/contrib/misc</site>
(which someone else with your very same problem kindly contributed).</p>

</a>
</qna>

<qna id="N196">
<q>I'd like to build NEdit, but my system seems to be missing the Xm...
include files and libXm.a</q>

<a>

<p>Xm means Motif, which is an important part of NEdit's GUI interface.  Motif
is standard on commercial Unix workstations, but not on free Unix platforms
like Linux and FreeBSD.  On these systems, you can now use LessTif, the
GPL clone of Motif, or purchase a copy of Motif, which is usually relatively
inexpensive, but not free.  You can find a list of companies selling Motif
for Linux at:</p>

<blockquote>
<p>
    <site>http://www.cen.com/mw3/#providers</site>
</p>
</blockquote>

<p>As of this writing LessTif is very close to being a fully reliable and
complete replacement for Motif, so it's definitely worth trying before
shelling out any money for a commercial copy.  Also remember that in most
cases, you don't really need Motif libraries to use NEdit.  There
are plenty of versions available pre-built with the Motif libraries
linked in statically.  If you can't find one for your system, ask around,
and you may find that someone else has already built one for you.  Motif
licensing allows free distribution of statically linked binaries.
Executables for NEdit are available from
<site>ftp://ftp.nedit.org/pub/</site>&lt;current-version&gt;/executables.</p>

</a>
</qna>

<qna id="N221">
<q>When I build NEdit, I get the yacc error: <tt>conflicts: 36 shift/reduce</tt></q>

<long-q>
<p>When I build NEdit, I get the yacc error:</p>
<pre>
  conflicts: 36 shift/reduce
</pre>
</long-q>

<a>

<p>That's normal.  NEdit's macro language has a very conflicted grammar, but the
conflicts all resolve themselves correctly.  The conflicts stem from allowing
awk-style no-operator concatenation of strings.</p>

</a>
</qna>

<qna id="N255">
<q>I built NEdit on my Linux system, and it's full of bugs.  What a horrible
editor!</q>

<a>

<p>Several of the Linux distributions began including LessTif (a free
version of the Motif GUI library) before it was really ready for
general use (particularly for something which needs to be as reliable
as a text editor).  If you have a version of Lesstif prior to 0.92.26,
you have to upgrade it, before it will support NEdit reliably.  To get
the newest version, go to <site>http://lesstif.org</site>.  Alternatively,
you can get pre-built, statically linked, executables from
<site>ftp://ftp.nedit.org/pub/</site>&lt;current-version&gt;/executables.</p>

</a>
</qna>



<qna id='tmpnam'>
<author><name>Thorsten Haude</name></author>

<q> While compiling NEdit on Linux, I get a warning about
<code>tmpnam</code> being dangerous. </q>

<long-q>
<p>While compiling NEdit on Linux, I get the following warning:</p>

<pre>
    file.o: In function `PrintString':
    file.o(.text+0x17b7): the use of `tmpnam' is dangerous, better use `mkstemp'
</pre>

<p>Is NEdit insecure?</p>

</long-q>

<a>

<p>Not if you are using the glibc. The algorithm of mkstemp(3) consists of
two parts: the first part is the one used in tmpnam(3) -- this is what
NEdit accomplishes by calling tmpnam(3); the second part is done directly
in NEdit. </p>
</a>
</qna>



<qna id='Xp'>
<author><name>Joor Loohuis</name></author>

<q>NEdit fails to build on Linux, with messages about `XpGetDocumentData'</q>

<long-q>
<p>NEdit fails to build on Linux, with messages</p>

<pre>
   undefined reference to `XpGetDocumentData'
   undefined reference to `XpGetPageDimensions'
   ...
</pre>

</long-q>

<a>

<p>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.</p>

</a>

</qna>

</section>











<section id="sect_customization">

<title>Customization</title>

<qna id="N277">
<q>I can't get the delete key to remap to a forward delete</q>

<long-q><p>I can't get the delete key to remap to a forward delete. I
have re-bound it in my .Xdefaults file, and that doesn't
help.</p></long-q>

<a>

<p>In your .Xdefaults file, add:</p>

<blockquote>
    <p><tt>nedit.remapDeleteKey: False</tt></p>
</blockquote>

<p>This is now the default, so you likely have an old resource file
sitting around somewhere with this setting.  When <tt>remapDeleteKey</tt> is
<tt>True</tt>), NEdit forcibly maps the delete to
backspace.  This can be used when the X server and the client
machine have different expectations about whether the key in the
backspace position on the keyboard is a backspace key or a delete
key.  It also saves users in very heterogeneous environments
from having to re-map keys on nearly every system they use
just to be able to backspace.</p>

</a>
</qna>

<qna id="N299">
<q>My X resource settings don't work.</q>

<a>

<p>It's harder to explain how to specify X resources than you might
expect, since how they are set is often configured by your local
system manager. They are either automatically attached to the server
(your screen) by an X startup or login script, or they are left
unspecified, and read from the .Xdefaults file whenever you run an X
application.  If they are attached to the server, you should find out
the "normal" method for setting them on your system. If it's not the
.Xdefaults file, then it is usually a file called .Xresources (also
in your home directory). To make a change, you have to either run
xrdb, or re-invoke the startup script that originally attached them,
usually by exiting and re-starting X, or logging out and back in to
your X session.</p>

<p>Since setting resources is tricky, it's usually better to start with
something simple, like:</p>

<blockquote>
<p><tt>nedit*foreground:green</tt></p>
</blockquote>

<p>Then, once you have that working, try the more subtle or difficult ones.
You can also use the appres command to find out what resources nedit
actually sees (<code>appres NEdit nedit</code>).</p>

</a>
</qna>

<qna id="N324">
<q>I am setting some X defaults in my $HOME/.nedit file but some of
them don't work.</q>

<a>

<p>The .nedit file holds the NEdit Preferences menu options and is
automatically overwritten whenever you select "Save Defaults".  You
really shouldn't put X resource settings there.  Also, as you may have
discovered, resources other than Preferences resources don't always
work from there.</p>

<p>How you set X resources depends on local system conventions.  You
usually put them in the .Xdefaults or .Xresources file in your home
directory.  You may also need to run xrdb to install them in the server.
It depends on how your local system has been configured, so it's best
to talk to the person who configured your system.  If you're not sure
whether your resources are set up correctly, the command:</p>

<pre>
    appres NEdit nedit
</pre>

<p>will tell you what settings NEdit will see when it runs.</p>

</a>
</qna>

<qna id="N342">

<q>If I install an "app-defaults" file for NEdit (empty too), all default
shortcuts are reset</q>

<long-q>
<p>If I install an "app-defaults" file for NEdit (empty too), all default
shortcuts are reset (only "Alt+B" and "Alt+Z" works). Without that file
all works fine. Now, how can I customize nedit with this problem ? Or,
how can I get a copy of all default shortcuts to add on my NEdit
"app-defaults" file ?</p>
</long-q>

<a>

<p>NEdit uses the X fallback resources mechanism to provide default values
for user-settable resources.  When you provide a system-wide app-
defaults file, it overrides the entire contents of the fallback
resources, meaning all of the program defaults are lost, except for
those which are also represented in the app-defaults file.  To use an
app-defaults file, therefore, you need to start from a complete one
which provides all of the necessary default values.  There is a complete
app-defaults file in:</p>

<blockquote>
<p><site>ftp://ftp.nedit.org/pub/contrib/misc/nedit.app-defaults</site></p>
</blockquote>

<p>We strongly discourage users from using system-wide app-defaults because
once you install the file, you have to keep it up to date with every new
release of the software.  If you don't update it, users might not even
notice the difference, but things will be increasingly wrong with each
new release.</p>

</a>
</qna>

<qna id="N364">
<q>Where can I get the complete list of nedit resources?</q>

<a>

<p>The way X is designed, there are a LOT of user settable resources in NEdit,
most of them quite useless.  You can see them all using the editres tool,
which is available on most Unix systems.  A more useful subset are the
application default resources, which you can look at either in the source code
(near the beginning of nedit.c, in the variable called fallbackResources) or
in the app-defaults file in:</p>

<blockquote>
<p><site>ftp://ftp.nedit.org/pub/contrib/misc/nedit.app-defaults</site></p>
</blockquote>

</a>
</qna>

<qna id="N386"> <q>Can I use <code>ispell</code> with NEdit instead of the less
capable Unix <code>spell</code> command?</q>

<a>

<p><code>ispell</code> is actually the default spell checker for NEdit on Linux systems where
<code>spell</code> is not available. On other systems, enter the following in the Shell
Commands dialog:</p>

<pre>
  Command Input: Either
  Command Output: Same Window
  Output Replaces Input: ON
  Shell Command: cat&gt;spellTmp; xterm -e ispell -x spellTmp; cat spellTmp; rm spellTmp
</pre>

<p>If you want to get fancy, the following puts the temporary file in the /tmp
directory, and uses $$ (the process ID of the shell) in the file name so you
don't have to worry about clashes between simultaneous ispell sessions:</p>

<pre>
  cat &gt; /tmp/ispell.$$; xterm -title "Spell Check" -e
  ispell -S /tmp/ispell.$$; cat /tmp/ispell.$$; rm /tmp/ispell.$$
</pre>

</a>
</qna>

<qna id="N415">
<q>How can the display of hidden (eg .login) files in dialog boxes be
suppressed</q>

<long-q>
<p>How can the display of hidden (eg .login) files in dialog boxes be
suppressed?  We use nedit with for teaching programming with very naive
and inexperienced students.  The display of these in dialogs such as the
"Save as..." one encourages them to screw up important login stuff, state
files etc.</p>
</long-q>

<a>

<p>It depends on the system you are running how easy this is to do.  Under
Motif 2.0, which I think is still only found on Linux and Free-BSD systems,
it's a simple resource setting:</p>

<blockquote>
<p><tt>nedit*XmFileSelectionBox.fileFilterStyle: FILTER_HIDDEN_FILES</tt></p>
</blockquote>

<p>On other systems, unfortunately, it's a rather difficult source code change,
involving creating a replacement file searching procedure to be spliced in
to the file selection box widget.</p>

</a>
</qna>

<qna id="N437">

<q>Why, in the 'open file' dialog, there is no text field where to
type in the file name?</q>

<long-q>
<p>Most Motif applications allow you to type in the file name in a separate
text field (as in the 'open file' dialog).  Why doesn't NEdit?  Can
I make it do that?</p>
</long-q>

<a>

<p>Set the X resource nedit.stdOpenDialog to True.  The field is disabled by
default to get new users accustomed to typing the file name directly in to
the list widget, which is not standard Motif behavior.</p>

</a>
</qna>

<qna id="N452">
<q>I would like to change NEdit's cursor from a
bar to a block</q>

<long-q>
<p>I would like to change NEdit's cursor from a
bar to a block.  I seem to lose it sometimes in my text.</p>
</long-q>

<a>

<p>The block cursor in NEdit is used to indicate overstrike mode, but
you can turn on a resource to make the cursor thicker:</p>

<blockquote>
  <p><tt>nedit*text.heavyCursor: true</tt></p>
</blockquote>

<p>The only way to get a permanent block cursor, though is to hack the source
code.  This shouldn't be too difficult, since the code for drawing a block