home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Fresh Fish 8
/
FreshFishVol8-CD1.bin
/
new
/
util
/
edit
/
jade
/
man
/
jade.info-3
(
.txt
)
< prev
next >
Wrap
GNU Info File
|
1994-10-16
|
50KB
|
1,067 lines
This is Info file jade.info, produced by Makeinfo-1.55 from the input
file jade.texi.
START-INFO-DIR-ENTRY
* Jade: (jade). An editor for X11 and AmigaDOS
END-INFO-DIR-ENTRY
This is Edition 1.3, last updated 7 October 1994, of `The Jade
Manual', for Jade, Version 3.2.
Jade is a text editor for X11 (on Unix) and the Amiga.
Copyright 1993, 1994 John Harper.
Permission is granted to make and distribute verbatim copies of this
manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of
this manual under the conditions for verbatim copying, provided that
the entire resulting derived work is distributed under the terms of a
permission notice identical to this one.
File: jade.info, Node: Using Marks, Next: Interrupting Jade, Prev: Using the Prompt, Up: Using Jade
Using Marks
===========
Marks are used to record a position in a file, as the file's buffer
is modified so does the position that the mark points to -- a mark will
keep pointing at the same character no matter what happens (unless the
character is deleted!).
The other good thing about marks is that they point to files *not*
buffers. This means that you can set a mark in a buffer, delete the
buffer and then move to the position of the mark, the file will be
reloaded and the cursor will point at the original character.
Normally there are three user-accessible marks (1) and one special
`auto-mark' which is used, amongst other things, to record the
"previous" position of the cursor, allowing you to retrace your last
major step.
The commands available on marks are,
Move to the mark #1, #2 or #3, depending on which function key is
pressed (F1 means mark #1, etc...). If the file pointed to is not
in memory it will be loaded into a new buffer.
`Shift-F1'
`Shift-F2'
`Shift-F3'
Set the position of mark #1, #2 or #3, depending on the function
key.
`Ctrl-x Ctrl-x'
Swap the positions of the cursor and the `auto-mark'.
`Ctrl-@'
Set the position of the `auto-mark'.
---------- Footnotes ----------
(1) There is no reason why you can't have more, the editor sets no
limitation on the number of marks available. This is just how I have
set the editor up.
File: jade.info, Node: Interrupting Jade, Next: Recursive Editing, Prev: Using Marks, Up: Using Jade
Interrupting Jade
=================
It is often useful to be able to tell Jade to quit whatever it is
doing and wait for more commands; this is called "interrupting" Jade.
When the editor receives an interrupt signal it will abort what it is
doing and rewind itself back to the inner-most recursive edit (see
*note Recursive Editing::.).
The interrupt signal differs with the operating system being used,
* Under Unix the `SIGINT' signal is used, this can be sent via the
`intr' character (get the editor into the foreground of the shell
it was started from and type `Ctrl-c' in the shell's terminal), or
directly through the `kill' shell command. For example, look at
the following shell session extract,
/var/src/jade/man$ ps
PID TT STAT TIME COMMAND
60 1 SW 0:02 (xinit)
87 1 S 0:08 fvwm
127 p0 S 0:00 /bin/bash
155 p0 S 0:04 jade
156 p1 S 0:00 /bin/bash
159 p1 R 0:00 ps
/var/src/jade/man$ kill -INT 155
First the `ps' command is used to find the Jade process' pid (155),
then the `kill' command is used to send the `INT' signal to this
process.
* The `Ctrl-c' signal is also used on Amigas, either type this in
the console window that Jade was launched from or use the `break'
(or possibly `breaktask') command to send the signal.
File: jade.info, Node: Recursive Editing, Next: Character Images, Prev: Interrupting Jade, Up: Using Jade
Recursive Editing
=================
Recursive editing is the act of editing a file while the current
command is still being evaluated. For example, when using the
`query-replace' command (`Meta-%') the `Ctrl-r' command enters a
recursive edit to let you edit the buffer, even though you are still
doing a query-replace (which will be resumed when the recursive edit
finishes).
As the name suggests a recursive edit calls the editor's main command
loop recursively from within a command. Any number of recursive edits
may be stacked up and then unwound back to the top-level of the editor.
When a recursive edit is in progress the name of the mode being used
to edit the buffer is shown in *square brackets*, not parentheses as in
the top-level instance.
The commands for manipulating recursive edits are as follows,
`Ctrl-]'
`Ctrl-Meta-c'
Exit the innermost recursive edit, this has no effect at the
top-level.
`Meta-x top-level'
Return to the outermost edit -- the top-level. This is useful when
you get "lost" inside a sequence of recursive edits.
`Meta-x recursive-edit'
Enter a new recursive edit; this command is usually best avoided to
save confusion.
In general, recursive editing is rarely used except in unavoidable
circumstances (i.e. in the Lisp debugger).
File: jade.info, Node: Character Images, Next: Client Editing, Prev: Recursive Editing, Up: Using Jade
Character Images
================
In general any character can be mapped to any sequence of up to four
character sized images (called glyphs) when it is drawn into a window.
The TAB character is a notable exception; it expands to as many spaces
as are needed to fill up to the next tab stop.
By default, the editor is set up to display the following,
0 to 31
A caret (`^') followed by the ASCII value of the character
exclusive-or'd with 0x40, i.e. `^@' to `^_'.
32 to 126
Printed literally, this includes all "normal" characters and
punctuation.
`^?'
128 to 255
Represented by the octal escape sequence (i.e. `\200') for that
character's numeric value.
If you want to edit files containing characters in the `Latin1'
character set (numerically, from 160 to 255) you can put the following
in your `.jaderc' file,
(latin-1-mode)
this will redefine the necessary characters.
If you want more details about this sort of thing see *Note Glyph
Tables::.
File: jade.info, Node: Client Editing, Next: Compiling Programs, Prev: Character Images, Up: Using Jade
Client Editing
==============
Normally you will only have one instance of Jade executing at a
single time. Often though, another program will want you to edit a
file, for example when you are composing a mail message. There is
normally a way to specify which editor you want to use, for example the
`EDITOR' environment variable.
If you were to ask to edit the file in `jade' an *additional*
process executing Jade would be started, totally separate from the
original. It is possible to use the original instance.
Firstly Jade must be set up to listen for clients wanting files
edited, this is done with the `server-open' command. You can either put
this in your `.jaderc' file (with a line like `(server-open)') or call
it manually with the command `Meta-x server-open'.
Only one instance of Jade may be a server at once. If you know that
there is no other Jade running but it still won't let you open a
server, and you are running on Unix, look for a dead socket called
`~/.Jade_rendezvous' and delete it if necessary.
Once the editor is listening for client messages the separate program
`jadeclient' may be used to load files into the server from an external
source. The format of `jadeclient' invocation is,
jadeclient [+LINE-NUMBER] FILE-NAME ...
When invoked, it will ask the server to edit each FILE-NAME (initially
positioned at line LINE-NUMBER) in turn, exiting only after each file
has finished being edited.
If when the `jadeclient' program is invoked their is no server open
(i.e. either Jade is not running or you haven't used the `server-open'
function) a message `Jade not running, waiting...' will be printed and
`jadeclient' will sit waiting for you to open a Jade server.
So, simpl