/usr/share/doc/jed-common/html/jed010.html is in jed-common 1:0.99.19-7.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
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 103 104 105 106 107 108 | <!DOCTYPE html>
<html >
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
<meta name="generator" content="hevea 2.28">
<link rel="stylesheet" type="text/css" href="jed.css">
<title>Mini-Buffer</title>
</head>
<body >
<a href="jed009.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="index.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="jed011.html"><img src="next_motif.gif" alt="Next"></a>
<hr>
<h2 id="sec13" class="section">9  Mini-Buffer</h2>
<p>The Mini-Buffer consists of a single line located at the bottom of the
screen. Much of the dialog between the user and <span style="font-weight:bold">jed</span> takes place in this
buffer. For example, when you search for a string, <span style="font-weight:bold">jed</span> will prompt you
for the string in the Mini-Buffer.</p><p>The Mini-Buffer also provides a direct link to the <span style="font-weight:bold">S-Lang</span> interpreter. To
access the interpreter, press <span style="font-variant:small-caps">Ctrl-X</span> <span style="font-variant:small-caps">Esc</span> and the <span style="font-family:monospace">S-Lang></span>
prompt will appear in the Mini-Buffer. Enter any valid <span style="font-weight:bold">S-Lang</span> expression
for evaluation by the interpreter.</p><p>It is possible to recall data previously entered into the Mini-Buffer by
using the up and down arrow keys. This makes it possible to use and edit
previous expressions in a convenient and efficient manner.</p>
<h3 id="sec14" class="subsection">9.1  Command Line Completion</h3>
<p>The <span style="font-weight:bold">jed</span> editor has several hundred built–in functions as well as many
more written in the <span style="font-weight:bold">S-Lang</span> extension language. Many of these functions
are bound to keys and many are not. It is simply unreasonable to require
the user to remember if a function is bound to a key or not and, if it is,
to remember the key to which it is bound. This is especially true of those
functions that are bound but rarely used. More often than not, one simply
forgets the exact name or spelling of a function and requires a little
help. For this reason, <span style="font-weight:bold">jed</span> supports command line completion in the
mini-buffer. This function, called <code>emacs_escape_x</code>, is bound to the
key <span style="font-variant:small-caps">Esc X</span>. This is one binding that must be remembered!</p><p>As an example, suppose that you are editing several buffers and you wish
to insert the contents of one buffer into the current buffer. The
function that does this is called <code>insert_buffer</code> and has no default
key-binding. Pressing <span style="font-variant:small-caps">Esc X</span> produces the prompt <span style="font-family:monospace">M-x</span>. This
prompt, borrowed from the Emacs editor, simply means that <span style="font-variant:small-caps">Esc X</span>
was pressed. Now type <span style="font-family:monospace">in</span> and hit the space bar or the <span style="font-variant:small-caps">Tab</span>
key. In this context (completion context) the space bar and the <span style="font-variant:small-caps">Tab</span>
will expand the string in the Mini-Buffer up until it is no longer unique.
In this case, <code>insert_file</code> and <code>insert_buffer</code> are only the two
functions that start with <span style="font-family:monospace">in</span>. Hence, <span style="font-family:monospace">in</span> will expand to
<code>insert_</code> at which point it becomes necessary to enter more
information to uniquely specify the desired function. However, in a
completion context, the space bar also has a special property that enables
the user to cycle among the possible completions. For this example,
hitting the space bar twice consecutively will produce the string
<code>insert_file</code> and hitting it again produces the desired string
<code>insert_buffer</code>.</p><p>The role of the space bar in completion is a point where Emacs and <span style="font-weight:bold">jed</span>
differ. Emacs will pop up a buffer of possible completions but <span style="font-weight:bold">jed</span> expects
the user to press the space bar to cycle among them. Both have there pros
and cons. Frequently, one sees messages on the Usenet newsgroup
<code>gnu.emacs.help</code> from Emacs users asking for the kind of completion
<span style="font-weight:bold">jed</span> employs.</p>
<h3 id="sec15" class="subsection">9.2  File Names</h3>
<p><span style="font-weight:bold">jed</span> takes every file name and “expands it” according to a set of rules
which vary according to the Operating System. For concreteness, consider
<span style="font-weight:bold">jed</span> running under MS-DOS. Suppose the user reads a new file into the
editor via the <code>find_file</code> command which emacs binds to <span style="font-variant:small-caps">Ctrl-X</span>
<span style="font-variant:small-caps">Ctrl-F</span>. Then the following might be displayed in the mini-buffer:</p><pre class="verbatim"> Find File: C:\JED\SLANG\
</pre><p>Here <span style="font-weight:bold">jed</span> is prompting for a file name in the directory <code>\JED\SLANG</code>
on disk <span style="font-family:monospace">C:</span>. However, suppose the user wants to get the file
<code>C:\JED\SRC\VIDEO.C</code>. Then the following responses produce equivalent
filenames when <span style="font-weight:bold">jed</span> expands them internally:
</p><pre class="verbatim"> Find File: C:\JED\src\video.c
Find File: C:\JED\SLANG\..\src\video.c
Find File: C:\JED\SLANG\../src/video.c
</pre><p>Note that the on MS-DOS systems, <span style="font-weight:bold">jed</span> replaces the <span style="font-family:monospace">/</span> with a <code>\</code>
and that case is not important. Now suppose you wish to get the file
<span style="font-family:monospace">VIDEO.C</span> from disk <span style="font-family:monospace">A:</span>. The following are also valid:</p><pre class="verbatim"> Find File: A:\video.c
Find File: A:video.c
Find File: C:\JED\SLANG\a:\video.c
</pre><p>In the last case, <span style="font-weight:bold">jed</span> is smart enough to figure out what is really meant.
Although the above examples are for MS-DOS systems, the rules also apply to
Unix and VMS systems as well. The only change is the file name syntax.
For example, on VMS
</p><pre class="verbatim"> sys$manager:[misc]dev$user:[davis.jed]vms.c
dev$user:[davis.jed]vms.c
</pre><p>become equivalent filenames upon expansion. For unix, the following are
equivalent:</p><pre class="verbatim"> /user1/users/davis/jed/unix.c
/usr/local/src//user1/users/davis/jed/unix.c
/usr/local/src/~/jed/unix.c
</pre><p>Note the last example: the tilde character <code>~</code> always expands into
the users <code>HOME</code> directory, in this case to <code>/user1/users/davis</code>.</p><p>When <span style="font-weight:bold">jed</span> writes a buffer out to a file, it usually prompts for a file name
in the minibuffer displaying the directory associated with the current
buffer. At this point a name can be appended to the directory string to
form a valid file name or the user may simply hit the <span style="font-variant:small-caps">RET</span> key. If
the latter alternative is chosen, <span style="font-weight:bold">jed</span> simply writes the buffer to the file
already associated with the buffer. Once the buffer is written to a file,
the buffer becomes attached to that file.</p>
<h3 id="sec16" class="subsection">9.3  Buffer Name and File Name Completion</h3>
<p>When <span style="font-weight:bold">jed</span> prompts for a file name or a buffer name, the space bar and
the <span style="font-variant:small-caps">Tab</span> keys are special. Hitting the <span style="font-variant:small-caps">Tab</span> key will complete
the name that is currently in the minibuffer up until it is no longer
unique. At that point, you can either enter more characters to complete
the name or hit the space bar to cycle among the possible completions.
The spacebar must be pressed at least twice to cycle among the
completions.</p><p>On MSDOS and VMS, it is possible to use wildcard characters in the file
name for completion purposes. For example, entering <span style="font-variant:small-caps">*.c</span> and hitting
the space bar will cycle among file names matching <span style="font-variant:small-caps">*.c</span>.
Unfortunately, this feature is not available on unix systems.</p>
<hr>
<a href="jed009.html"><img src="previous_motif.gif" alt="Previous"></a>
<a href="index.html"><img src="contents_motif.gif" alt="Up"></a>
<a href="jed011.html"><img src="next_motif.gif" alt="Next"></a>
</body>
</html>
|