1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
|
<html lang="en">
<head>
<title>Arguments - ne's manual</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="ne's manual">
<meta name="generator" content="makeinfo 4.13">
<link title="Top" rel="start" href="index.html#Top">
<link rel="up" href="Reference.html#Reference" title="Reference">
<link rel="next" href="The-Status-Bar.html#The-Status-Bar" title="The Status Bar">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home" title="Texinfo Homepage">
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
span.sc { font-variant:small-caps }
span.roman { font-family:serif; font-weight:normal; }
span.sansserif { font-family:sans-serif; font-weight:normal; }
--></style>
</head>
<body>
<div class="node">
<a name="Arguments"></a>
<p>
Next: <a rel="next" accesskey="n" href="The-Status-Bar.html#The-Status-Bar">The Status Bar</a>,
Up: <a rel="up" accesskey="u" href="Reference.html#Reference">Reference</a>
<hr>
</div>
<h3 class="section">3.1 Arguments</h3>
<p><a name="index-Arguments-52"></a><a name="index-Global-Directory-53"></a><a name="index-Startup-macro-54"></a><a name="index-Skipping-configuration-files-55"></a><a name="index-Setting-configuration-file-names-56"></a>
The main arguments you can give to <code>ne</code> are the names of files you
want to edit. They will be loaded into separate documents. If you
specify <code>--help</code> anywhere on the command line, a simple help text
describing <code>ne</code>'s arguments will be printed.
<p>The <code>+</code><var>N</var> option causes <code>ne</code> to advance to the <var>N</var>th
line of the first document loaded. This option is fairly common among
editors and text display programs like <code>vi</code> and <code>less</code>. The
<var>N</var> itself is optional. Without it, a bare <code>+</code> on the command
line causes <code>ne</code> to advance to the last line of the first document.
<p>The <code>--no-config</code> option skips the reading of the key
bindings and menu configuration files (see <a href="Configuration.html#Configuration">Configuration</a>). This is
essential if you are experimenting with a new configuration and you make
mistakes in it.
<p>The <code>--macro </code><var>filename</var> option specifies the name of a
macro that will be started just after all documents have been loaded. A
typical macro would move the cursor to a certain line.
<p>The <code>--keys </code><var>filename</var> option and the <code>--menus
</code><var>filename</var> option specify a name different from the default one
(<samp><span class="file">.keys</span></samp> and <samp><span class="file">.menus</span></samp>, respectively) for the key bindings and
the menu configuration files. Note that <code>ne</code> searches for these
files first in the current directory, and then in your <samp><span class="file">~/.ne</span></samp>
directory.
<p>The <code>--ansi</code> and the <code>--no-ansi</code> options manage
<code>ne</code>'s built-in ANSI sequences. Usually <code>ne</code> tries to retrieve
from your system some information that is necessary to handle your
terminal. If for some reason this is impossible, you can ask <code>ne</code>
to use a built-in set of sequences that will work on many terminals
using the <code>--ansi</code> option (to be true, <code>ne</code> can be even
compiled so that it uses directly the built-in set, but you need not
know this). If you want to be sure (usually for debugging purposes) that
<code>ne</code> is not using the built-in set, you can specify
<code>--no-ansi</code>.
<p>The <code>--no-syntax</code> option disables <code>ne</code>'s normal syntax
highlighting capability. For most editing situations, this would be
unnecessary, but for extremely large files it may be helpful. Syntax
highlighting incurs small memory usage and processor overhead penalties
for each line of text. The <code>--no-syntax</code> option eliminates that
overhead.
<p>The <code>--utf8</code> and <code>--no-utf8</code> options can be used to
force or inhibit UTF-8 I/O, overriding the choice imposed by the system
locale. Note, however, that in general it is more advisable to set the
<code>LANG</code> environment variable to a locale supporting UTF-8 (you can
usually see the locale list with <code>locale -a</code>). See <a href="UTF_002d8-Support.html#UTF_002d8-Support">UTF-8 Support</a>.
<p>If you need to open a file whose name starts with ‘<samp><span class="samp">--</span></samp>’, you can put
‘<samp><span class="samp">--</span></samp>’ before the filename, which will skip command recognition for
the next word.
<p>Finally, <code>ne</code> has a <dfn>global directory</dfn> where the system
administrator can store macros, default preferences, and syntax
definitions for all users of the system. The location of this directory
is defined when <code>ne</code> is built, but you can override it by creating
and exporting the <code>NE_GLOBAL_DIR</code> environment variable prior to
invoking <code>ne</code>. If you load no files when you start <code>ne</code>, it
will display a splash screen. The last line on that screen shows the
global directory <code>ne</code> is using, if it exists, or an error message,
otherwise.
</body></html>
|
