This documentation should go elsewhere, but I haven't gotten around to it
Disable the following warnings; the code doesn't cope with it:
-Wno-pointer-sign -Wno-unused-parameter -Wno-cast-qual
Do note that the joerc files must be written using the 8-bit encoding,
not in UTF-8. Syntax files, on the other hand, absolutely must be
written in UTF-8 since jupp29.
JOE now handles two classes of character sets: UTF-8 and byte coded (like
ISO-8859-1). It can not yet handle other major classes such as UTF-16 or
GB2312. There are other restrictions: character sets must use LF (0x0A) or
CR-LF (0x0D - 0x0A) as line terminators, space must be 0x20 and tab must be
0x09. Basically, the files must be UNIX or MS-DOS compatible text files.
This means EBCDIC will not work properly (but you would need to handle fixed
record length lines anyway) and character sets which use CR terminated lines
(MACs) will not yet work.
The terminal and the file can have different encodings. JOE will translate
between the two. Currently, one of the two must be UTF-8 for translation to
The character set for the terminal and the default character set assumed for
files is determined by the 'LC_ALL' environment variable (and if that's not
set, LC_CTYPE and LANG are also checked). 'JOECHARMAP' overrides this value.
For example, if LC_ALL is set to:
Then the character set will be ISO-8859-1.
If LC_ALL is set to:
The character set will UTF-8.
Hit ^T E to change the coding for the file. Hit <tab> <tab> at this prompt
to get a list of available codings. There are a number of built-in
character sets, plus you can install character sets in the ~/.jupp/charmaps
and /usr/local/etc/joe/charmaps directories.
Check: /usr/share/i18n/charmaps for example character set files. Only
byte oriented character sets will work. Also, the file should not be
gzipped (all of the charmap file in /usr/share/i18n/charmaps on my computer
were compressed). The parser is very bad, so basically the file has to look
exactly like the example one in /usr/local/etc/joe/charmaps.
You can hit ^K <space> to see the current character set.
You can hit ` x to enter a UCS character if the file coding is UTF-8.
Try ^K , and ^K . These keys select the current block (based on
indentation) and shift it left or right by the -istep and -indentc.
The "classic" way is to hit ^K B at the beginning and ^K K at the
end. These set pointers called markb and markk. Once these are set you
can jump to markb with ^[ b and jump to markk with ^[ k.
New way no.1: hit Ctrl-space to start selecting, move the cursor,
then hit Ctrl-space to complete the block. Hit Ctrl-space in the block to
cancel it. Hit Ctrl-space outside of the block to start selecting a new
one. This uses the "toggle_marking" function. Also any block command will
complete the block. (joe flavour only)
New way no.2: hit Ctrl-rtarw to start selecting rightward. Each
time you hit Ctrl-rtarw, the block is extended one more to the right. This
uses a simple macro: "begin_marking,rtarw,toggle_marking". Unfortunately,
there is no standard way to get the keysequence given by the terminal
emulator when you hit Ctrl-rtarw. Instead you have to determine this
sequence yourself and enter it directly in the joerc file. Some examples
are given for xterm and gnome-terminal. Hit ` rtarw to have the sequence
shown on your screen. Note that Putty uses ^[ ^[ [ C which will not appear
with ` rtarw (also ^[ ^[ is set book mark, so you need to unbind it to do
this in Putty). (joe flavour only)
Also you can hit Ctrl-delete to cut and Ctrl-insert to paste if the
sequence for these keys are known. (joe flavour only)
New way No.3: press down shift, then move the cursor with the
arrow keys or, optionally with ctrl, the Home and End keys; release the
shift key when done and remember that the cursor indicator on screen is
not part of the selection. (all flavours)
Also, you can pass "-keymap cua" on the command line to change
the key bindings for ^Z (Undo), ^X (Cut), ^C (Copy), ^V (Paste) as in
contemporary GUI editors. (joe, rjoe, jstar, jupp flavours only)
Using Picture mode and Rectangle mode may help with that.
Hex edit mode
When this mode is selected (either put -hex on the command line, or look for
"Hex edit mode" after hitting ^T), the buffer is displayed as a hex dump,
but all of the editing commands operate the same way. It is most useful to
select overtype mode in conjunction with hex dump (hit ^T T). Then typing
will not insert.
- To enter the hex byte 0xF8 type ` x F 8
- You can use ^KC to copy a block as usual. If overtype mode is selected,
the block will overwrite the destination data without changing the size of
the file. Otherwise it inserts.
- Hit ESC x byte <Enter>, to jump to a particular byte offset. Hex values
can be entered into this prompt like this: 0x2000.
- Search, incremental search, and search & replace all operate as usual.
$MirOS: contrib/code/jupp/HINTS,v 1.17 2018/08/10 02:53:42 tg Exp $