SET's Editor documentation for Version 0.2.18b

July 1997

This is the documentation for SET's Editor.

Copyright © 1996, 1997 Salvador Eduardo Tropea

This documentation may be freely distributed, provided this copyright notice is left intact on all copies.

This documentation may be freely distributed with the editor or the RHIDE package or any part thereof, provided this copyright notice is left intact 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.

People who helped me develop the editor:

• Robert Höhne (with some base routines, a lot of patches and reports)
• Molnar Laszlo (with the calculator, tests and a lot of ideas)
• Marek Habersack (with tests and a lot of ideas)
• Frank Donahoe (with a lot of corrections to this text)

This editor is included in the Robert Höhne's RHIDE as a replacement for the original TVision's editor class.

SET's editor is an editor designed to be used by programmers; the main target of the editor is C and C++ code but Pascal and Clipper are supported too.

The editor was designed to be very similar to the DOS standard editors for C, especially to Borland's IDE editor. The editor supports a lot of WordStar style commands plus some CUA commands, so if you have used any editor that uses these kinds of commands you'll find my editor very familiar. On the other hand if you have never used a DOS editor, especially if you use VI on UNIX machines you'll feel lost. You can configure the keyboard but this feature is relatively limited. How to configure the keyboard .

1.2 Requirements

For now I only plan to distribute my editor inside of RHIDE. Requirements are the requirements of RHIDE.

1.3 About the Author

     E-Mail: Salvador Eduardo Tropea
     
     Telephone: (+541) 759-0013
     Postal Address:
     Salvador E. Tropea
     Curapaligüe 2124
     (1678) Caseros - 3 de Febrero
     Prov: Buenos Aires
     Argentina

Read the conventions topic first to understand my way of indicating keystrokes.

In the description of each command I'll include the internal name used by the editor because this name is needed to configure the keyboard.

I'll use some conventions when talking about the keystrokes needed to trigger some command. So here is what I use:

The key named Ctrl or Control is represented as ^; this key doesn't have any effect used alone inside of the editor so the ^ symbol will be used only in conjunction with the name of some key indicating that you must press the two keys at the same time. For example, ^A is Ctrl and A at the same time. When I say "at the same time" that means: press Ctrl, hold it, and press the other key; that's the reason to put A after Ctrl.

To indicate a sequence of keystrokes I'll use a dash to separate the keys. For example, ^K-B is Ctrl and K at the same time, and then press B, of course release ^K first.

To indicate keys pressed at the same time other than ^x I'll use a plus. For example, Shift+^Insert is the three keys at the same time!

I don't think that you are stupid; the editor is written for programmers, but I wanted to make that clear to avoid problems ;-).

2.2 Cursor movement

2.4 Blocks

A block is a selected portion of the text. You can copy, delete, etc. blocks of text. The associated commands are:

There are two block modes. One is the mode that the old editor of RHIDE used. This mode is used in CUA programs. The other is called Persistent Blocks.

In the normal mode each time you select a block and then insert anything in it (with cmbPaste or by typing anything) the selected block is deleted and is replaced by the new text.

In persistent blocks the selection is not replaced and is not lost when you move the cursor. From this comes the name "Persistent." In this mode you can use cmbMoveBlock and cmbCopyBlock without using the Clipboard. In addition you can apply indentations to the block ( Indentation ), search only inside it, etc. That's what makes this mode much more powerful than the former. If you really like to replace the selected text by the selection of the Clipboard, that's the default behaviour of the first mode. You can use the cmbReplaceSelect command to achieve the same in the Persistent Blocks mode.

2.4.2 Selecting with the mouse or Shift

The described commands for selecting a block, cmbStartSelect and cmbEndSelect, are good but not so quick. There are other ways to do this.

Using the mouse you need only point to the start place, hold the left button pressed and move the mouse to the end point of your block.

To select a word with the mouse just double click on it.

2.4.2.2 Using the Shift key

Using the Shift key you only need to move the cursor to the start point, hold Shift pressed and move the cursor to the end point with any of the available cursor commands. Cursor movement .

2.4.3 Indentation

You can indent or unindent a block of text using various commands, but you must keep in mind that for now the editor is limited in the following: Real Tabs If you are using tabs to indent your text, don't mix the tabs with spaces and, if you are using spaces to indent, don't mix them with real tabs.

cmbIndentBlk acts according to the mode. If you are using tabs, the editor will put one tab beginning each line. If you aren't using tabs the editor will operate the Tab command on the first line and then will use this amount of indentation on the entire block. Real Tabs .

cmbUnIndentBlk acts according to the mode too. Real Tabs mode. This is just like cmbUnIndentBlkOne deleting one tab but if you don't use tabs the editor uses Backspace on the first used column of the first line of the block and unindents by the resulting amount all the block.

cmbSmartIndent and cmbSmartUnIndent indents taking as reference the { } pair where the block is, for example:

       {
     line1
          line2
        line3
       }

       {
        line1
        line2
        line3
       }

2.4.4 Rectangular Blocks

The editor includes a mode where you can select a rectangular portion of the text and copy, cut, clear, paste, move, etc. this region. This tool is very useful for modifications on columns.

Attention! The selected area is based on the X,Y coordinates. For this reason if you insert lines before the bottom of the rectangle the area won't be moved. I don't plan to move the area by now because that takes some CPU and I think that this selection is made just before using it. So don't report that like a bug. That is the way it works!

This feature is very useful to save some keystrokes. With this feature you can create a lot of shortcuts to make your life easiest.

So now, What's a Pseudo Macro? It's like a macro but is triggered by two things: one the text behind the cursor, and two the ^Space combination.

And what's the result? The result is customizable, but by default there are some predefined behaviours. For example, type in a new window the following two characters: #i and the press ^Space ...

Surprised? I bet! You got: #include <.h> and the cursor just in the right place to write the name of the header.

Now write the famous stdio word, press End, then Enter twice and now write the following two letters: ma and then ^Space ...

I bet this time you predicted better what will happen so you aren't so surprised ;-). Anyways, Surprise! Now type pr and the magic keys and ... printf(""); appears. To end the happy history now type "Hello world!" That's all. You wrote the hello world program at a very good speed.

Now you know what I mean when I say pseudo-macros.

2.5.2 How can I customize that?

Is very easy. There is a file called pmacros.txt in the same directory where you started the editor. This file contains the definitions for each pseudo macro. You can define up to 32 pseudo macros. (Please tell me if that isn't enough. I can sacrifice some time to make it dynamically expandable).

Important: If you are using RHIDE consult the RHIDE documentation to know where is stored the pmacros.txt file.

The pmacros.txt file is a very good example and is self-explained but I'll include here one example.

Trigger: "i("
Mode: 0,1,0,1,0
 "if (@0)\n"
 "  {@1\n"
   "}\n"
 "\belse\n"
 "  {@2\n"
   "}"

The Mode keyword indicates the mode that the editor will use when inserting the text. The modes are:

• Overwrite Overwrite
• Autoindent Autoindent
• Use Tabs Real Tabs
• Persistent blocks Block modes
• Intelligent C indent Intelligent C indent

The rest is the code to insert surrounded by ". You can use \b to indicate backspace, \n for newline and \\ to indicate a simple \. If you want to insert a @ you have to type it twice @@, because this character has a special meaning (see below).

After the insertion the cursor is positioned in the place marked with @0. Don't forget to signal this point or the cursor will positioned at the beginning of the file. The places marked with @1, @2 and @3 are saved in the markers 7, 8 and 9.

2.6 Miscellaneous

There are three associated files with the keyboard: keybind.cc, keybind.h and keybind.txt.

The keybind.h file contains the scancode number for each key and the number for each command. This file is included in keybind.cc. If your keyboard has a different assignment you can modify the scancodes in this file. For example, the German keyboards have the following sequence QWERTZ instead of the more common QWERTY, so each time you press ^Z you won't get the function of ^Z, but of ^Y instead. Some can live with it, but it is fixable. To fix this problem you must correct the scancode of the Z key in keybind.h. But of course this affects ^Y too. That's only an example. The most common problem is with the symbols like {, }, [, etc. If you don't know how to find the scancode of a key take this link. A program to find the scancodes .

The keybind.cc file is a C++ file but you don't need to compile it and link with the editor, you only need to preprocess it (I used this method to save the time needed to make a parser ;-).

To convert this file into a keybind.txt file use:

     cpp keybind.cc > keybind.txt

There are seven sections in the file, each section is the keyboard translation under certain situation. The sections are:

     Scan_Code = Command

     RSHIFT = xxxxx

1. put BACKSPACE = cmbNoCommand in the NORMAL section,
2. put O = cmbBackSpace in the CONTROL section.

II) If some thing is wrong in the keybind.txt file the program will inform the error. The line number is for the keybind.txt and not for keybind.cc (Sorry, some day I'll fix this). To continue the execution press any key and then enter.

III) You can repeat an assignment, the last wins:

     BACKSPACE = cmbNoCommand
     BACKSPACE = cmbBackSpace

3.2 A program to find the scancodes

The author of the following program is Robert Höhne:

#include 
#include 

#ifdef __GNUC__
#include 
#define REGS __dpmi_regs
#define INTR(nr,r) __dpmi_int(nr,&r)
#else
#define REGS union REGS
#define INTR(nr,r) int86(nr,&r,&r)
#endif

unsigned short getshiftstate(void)
{
  REGS r;
  r.h.ah = 0x12;
  INTR(0x16,r);
  return r.x.ax;
}

unsigned short gkey(void)
{
  REGS r;
  r.h.ah = 0x10;
  INTR(0x16,r);
  if (r.h.al == 0xE0 || r.h.al == 0) r.h.al = 0;
  return r.x.ax;
}

main()
{
  unsigned short key;
  do
  {
    key = gkey();
    fprintf(stdout,"%04X, scan code: %d\n",key,key>>8);
  } while (1);
}

The settings are:

This setting controls if the typed characters are inserted in the buffer or if the typed characters replace the original ones. Insert and Delete for a detailed explanation.

4.2 Autoindent

This setting controls what happend when you press ENTER. If this setting is off the cursor goes to the column 1 of a new line. If the mode is on the editor will try to keep the indentation of the code inserting spaces.

4.3 Real Tabs

This setting controls what happend when you press TAB. If this setting is on the editor will insert an ASCII 9 in this place.

An ASCII 9 is a TAB, that means that the width of this char is enough to move the cursor to the next tabulator column. In the editor the tabulator columns are equidistant and the positions are controled by the Tab Size value.

If this setting is off the editor won't put any ASCII 9 in your text. Instead the editor will insert enough spaces to move the cursor to the next tab-stop, but if the cursor is positioned on the first character of the line the editor will insert spaces to move this position to the next hole in the line over the line where you are. Confused? Sorry for my English, an example will clarify that:

This is a line over the line where you are

That's the line where the cursor is, at column one.

After pressing TAB you'll get:

This is a line over the line where you are

That's the line where the cursor is, at column one.

Now can ask, Why this? Is that useful? The answer is that's very useful to keep your code indented, experiment using that under a line with if, for, etc.

Another thing controlled by this setting is the behaviour of the Backspace key, when the setting is on the key is just 'delete the character at the left of the cursor' but when the setting is off this key is the 'Unindent' key.

The editor is much more coherent when you choose to use TABs or not use TABs. If you mix the two modes you'll get some unexpected things, specially in the indentation of the blocks.

Is better if you always work in a file without tabs and with this setting off. Then you'll get much from the editor.

Now you can say: But I really need tabs because I'm editing a make file! or because I'll send the file using an ultra slow link and I want the compression granted by the tabs. In these cases you can first expand all tabs, then work without real tabs and at the finish of your work compact all possible spaces and generate a file with all the tabs that you need. Miscellaneous section.

4.4 Persistent Blocks

This setting controls the behaviour of the selected area.

Block modes chapter for a detailed explanation.

4.5 Intelligent C indent

This mode was designed to be used in jointly with the Pseudo Macros ( Pseudo Macros ) and the Real Tabs mode in off to achieve an easy way to indent the code making a better work than the Autoindent mode.

In this mode the spaces inserted after pressing ENTER depend on the first word in the last line. For example, if you have:

     if (a==b)_

     if (a==b)
       _

     if (a==b)
       {
        _

     if (a==b)
       {
        1st line;
        2nd line;
       _

     if (a==b)
       {
        1st line;
        2nd line;
       }
     _

I tried to make this mode as smart as possible, but needs more work. If you have suggestions contact me.

Another important thing is that this indentation has a personal style, my style ;-), so maybe you don't like it. If that's your case you can do the following things:

• Use another way of indentation offered by the editor. For example, turn on the Real Tabs mode and indent with tabs.
• Customize the pmacros.txt file ( Pseudo Macros ), actually this file is coherent with this mode.
• The editor isn't configurable like Emacs or Brief using a language, but is written in C++ and chances that you know C++ are over the 90% so contact me and I'll help you to write the routines that you need to get an indentation in your own style :-).

I'll try to describe the behaviour of the mode:

Each time you press ENTER the editor inserts a rn string in your text, after that the editor searchs one line located above the new line that has at least one character inside. This line is taken as reference. The editor analyzes this line searching for:

• The first non-blank character on this line.
• The first word on this line.
• The first parenthesis.
• The balance of parentheses on the line.
• The last non-blank and non-comment character in the line.

If the line contains } at the start the editor will go to the same column of the } and then will perform a Backspace. If the Real Tabs mode is off, that's an unindent. Real Tabs .

If the line starts with a C++ comment the effect is the same as in Autoindent. Autoindent .

If the line starts with a C comment the editor will try to skip the comment and analyze the rest of the line, but if the comment doesn't end on this line the editor will go to the column where the / is.

If the line starts with / the editor goes to this column.

If the line has more ( than ) the editor will go to the column of the first non-blank after the first (.

If the line has more ) than ( the editor will search the line where the number of parentheses is balanced, then will analyze this line. If the whole line still generates an unbalanced situation the editor will go to the first used column in the line that was found the first time. But if this line lets all balanced the editor will take the first word on the line and will use it as reference.

At last, and according to the word found, the editor will use this word as reference. The editor recognises the following keywords:

Seasick? Do you have more examples? .

Note: Some of these features were added in v0.2.14 of the editor based on a suggestion of about the behaviour of the mode on a line like this printf("Num: %d" with the rest of the parameters on the next line.

4.5.2 Do you have more examples?

Well here are some examples. I used a strange convention, like this: if I say type `a[ENTER]{', type the letter a, then press ENTER and finally press the `{' key.

Example 1: (Is similar to one explained before but is to show the convention)

     Type:
     if (a==1)[ENTER]{[ENTER]a=2;[ENTER]b=3;[ENTER][BACKSPACE]}[ENTER]
     
     You'll get:
     
     if (a==1)
       {
        a=2;
        b=3;
       }
     [<--- cursor here]

     Type:
     switch(a)[ENTER]{[ENTER]case 1:[ENTER]a=2;[ENTER]b=3;[ENTER]break;
     [ENTER]case 2:[ENTER]b=5;[ENTER]break;[ENTER][BACKSPACE]}[ENTER]
     
     You'll get:
     
     switch(a)
       {
        case 1:
             a=2;
             b=3;
             break;
        case 2:
             b=5;
             break;
       }
     [<--- cursor here]

     Type:
     printf([SPACE]"Num: %d",[ENTER]a[SPACE]);[ENTER]
     
     You'll get:
     
     printf( "Num: %d",
             a );
     [<--- cursor here]

     Type:
     if[SPACE]([SPACE](a==1)[SPACE]||[ENTER](b==2)[SPACE]||[ENTER]
     c[SPACE])[ENTER]
     
     You'll get:
     
     if ( (a==1) ||
          (b==2) ||
          c )
       [<--- cursor here]

     Type:
     /*-a-*/for[SPACE](x=1;x;--x)[ENTER]
     
     You'll get:
     
     /*-a-*/for (x=1;x;--x)
               [<--- cursor here]

     Type:
     for[SPACE](x=1;x;--x);[SPACE]//-b[ENTER]
     
     You'll get:
     
     for (x=1;x;--x); //-b
     [<--- cursor here]

4.6 Column cursor

This setting enables an strange feature of the editor, when this mode is on the column where the cursor is is highlighted. This feature is very good to check if some part of your code is aligned.

If you like this mode but is very uncomfortable to use all the time contact me and if I get enough feedback I'll put this thing in a key to be turned on/off quickly.

4.7 Row cursor

This setting is similar to the column cursor but acts on the row where the cursor is. If you enable the two modes you'll get a cross on the screen showing where the cursor is.

4.8 Match pair highlight

This mode acts showing the pairs of (/), [/] and {/} on the fly. Each time you type one of these symbols the editor will search the matching pair, if the editor finds it and the match is on the screen both will be highlighted, if the match is outside the screen the editor will inform the position on the status line, and if there is no match the editor will inform the situation in the status line too.

That's very useful when you are typing complex parenthetical expressions or a very nested code. You can use it jointly with the cmbSearchStart, cmbSearchEnd, cmbSearchOpPar, cmbSearchClPar, cmbSearchOpCor and cmbSearchClCor commands. ( Miscellaneous ).

4.9 Syntax Highlight

The editor can highlight the syntax of your code. The available modes are:

• No highlight, all the code is with the same color.
• C/C++ Highlight.
• Pascal Highlight.
• Clipper Highlight.

The C/C++ highlight was designed for the GNU C compiler.

The Pascal highlight was designed for the GNU Pascal compiler.

The Clipper highlight was designed for the CA-Clipper 5 compiler.

The sources of the calculator are in the parser.c file. They are free and you can use it for any purpose.

Here is the documentation of the calculator written by Laszlo:

The purpose of this program, to provide a simple but powerful 'calculator' for programmers, to help with coding and debugging, where GDB's expression evaluator is not enough.

You may say "Hey, I can write a better one with flex and bison", and you may be right. I can make a better one too. But it'll be 4-5 times longer! This calculator is only 10 kbytes of C code. What I think? It's not that bad.

The parser algorithm I use is called 'Operator Precedence Parsing' (I translated this from Hungarian, so I may be wrong ;-). It works with 'operator precedence grammars' (a subset of LR(1) grammars), which means that there can't be two non-terminating tokens next to each other on the right side of your grammar rules. It's ideal for expression evaluation.

With this parser you can use numbers, operators, parentheses and functions like in C.

Here are the operators in decreasing precedence:

1. ~ unary not - unary minus
2. ** power
3. * multiplication / division % modulo
4. + plus - binary minus
5. << shift left >> shift right
6. & logical and
7. ^ logical xor
8. | logical or

The calculator includes the following functions: sin, cos, tan, sinh, cosh, tanh, asin, acos, atan, log, log10, exp, abs, sqrt, ceil and floor. They work as you expected. Additionally the calculator provides some radix conversion routines: bin, oct, dec and hex.

The calculator uses doubles, but you can use numbers in the usual integer formats also: 0x... for base 16, 0b... for base 2 and 0... for base 8. The result of the calculation is displayed as a double for base 10, and converted to long long format for the other radixes.

Error codes:

If you find a bug please contact me, the Undo thing is the most complex one and I know that needs some work on it.

When reporting a bug please don't tell me: Some times some strange thing happend ... Try to find a pattern to the problem. What situation triggers the problem? ... with which file(s)? Then send me the file and the description.

When sending to me a file UUEncode it to avoid problems related with the e-mail.

• Autoindent
• Blocks
• Blocks - Rectangular
• Bugs
• Column cursor
• How to contact me
• Indentation
• Insert and Delete
• Intelligent C indent
• keybind.cc
• keybind.h
• keybind.txt
• Match pair highlight
• Movement
• Overwrite
• Persistent Blocks
• pmacros.txt
• Pseudo Macros
• Real Tabs
• Row cursor
• scan codes
• TABs
• Use Real Tabs

• Autoindent mode on/off <^O>
• Beginning of line <Home>
• Bottom of file <^Q-C>
• Bottom of window <^Q-X>
• Character left <Left arrow>
• Character right <Right arrow>
• cmbBackSpace <Backspace>
• cmbCharLeft <Left arrow>
• cmbCharRight <Right arrow>
• cmbClear <^Del>
• cmbCompactBuffer <From menu>
• cmbCopy <^Ins>
• cmbCopyBlock <^K-C>
• cmbCut <^K-Y>
• cmbDelChar <Del>
• cmbDelEnd <^Q-Y>
• cmbDelLine <^Y>
• cmbDelPrevWord <^Backspace>
• cmbDelStart <^Q-H>
• cmbDelWord <^T>
• cmbEndSelect <^K-K>
• cmbExpandAllTabs <From menu>
• cmbExpandCode <^Space>
• cmbFirstLineInScreen <^Q-E>
• cmbGoBeginBlock <^Q-B>
• cmbGoEndBlock <^Q-K>
• cmbGotoEditorLine <^J>
• cmbGotoMarkn <^Q n*>
• cmbHideSelect <^K-H>
• cmbIndentBlk <^K-Tab>
• cmbIndentBlkOne <^K-I>
• cmbIndentMode <^O>
• cmbInsMode <Ins>
• cmbLastLineInScreen <^Q-X>
• cmbLineDown <Down arrow>
• cmbLineEnd <End>
• cmbLineStart <Home>
• cmbLineUp <Up arrow>
• cmbMarkLine <^K-L>
• cmbMarkWord <^K-T>
• cmbMoveBlock <^K+V>
• cmbNewLine <Enter>
• cmbPageDown <PgDn>
• cmbPageUp <PgUp>
• cmbPaste <Shift+Ins>
• cmbPlayMacro <^F10>
• cmbPutMarkn <^K n*>
• cmbReadBlock <^K-R>
• cmbRecordMacro <Shift+F10>
• cmbReplaceSelect <Shift+^Ins>
• cmbScrollDown <^Z>
• cmbScrollUp <^W>
• cmbSearchClCor <Shift+^]>
• cmbSearchClPar <Shift+^0>
• cmbSearchEnd <^]>
• cmbSearchOpCor <Shift+^[>
• cmbSearchOpPar <Shift+^9>
• cmbSearchStart <^[>
• cmbSelLength <^Q-L>
• cmbSelRectCopy <^K-Shift+C>
• cmbSelRectCut <^K-ShiftT>
• cmbSelRectDel <^K-Shift+L>
• cmbSelRectEnd <^K-Shift+K>
• cmbSelRectHide <^K-Shift+H>
• cmbSelRectMove <^K+Shift+V>
• cmbSelRectPaste <^K-Shift+P>
• cmbSelRectStart <^K-Shift+B>
• cmbSetGlobalOptions <Alt+G>
• cmbSetLocalOptions <Alt+L>
• cmbSmartIndent <^Tab>
• cmbSmartUnIndent <Shift+^Tab>
• cmbStartSelect <^K-B>
• cmbStopMacro <Alt+F10>
• cmbTextEnd <^Q-C>
• cmbTextStart <^Q-R>
• cmbToLower <^K-O>
• cmbToUpper <^K-M>
• cmbUndo <Alt+Backspace>
• cmbUnIndentBlk <^K-Shift+Tab>
• cmbUnIndentBlkOne <^K-U>
• cmbWordLeft <^Left arrow>
• cmbWordRight <^Right arrow>
• cmbWriteBlock <^K-W>
• Compact the text using tabs <From menu>
• Convert all tabs in spaces <From menu>
• Convert to Lowercase <^K-O>
• Convert to Uppercase <^K-M>
• Copy the selected block <^K-C>
• Copy to Clipboard <^Ins>
• Copy to special Clipboard <^K-Shift+C>
• Delete block <^Del>
• Delete block <^K-Shift+L>
• Delete block and copy it to an special Clipboard <^K-ShiftT>
• Delete block and copy it to the Clipboard <^K-Y>
• Delete character to left <Backspace>
• Delete line <^Y>
• Delete the character under cursor <Del>
• Delete to end of line <^Q-Y>
• Delete to start of line <^Q-H>
• Delete word at left <^T>
• Delete word at right <^Backspace>
• End of line <End>
• Find place marker <^Q n*>
• Goto Line <^J>
• Hide/Show block <^K-H>
• Hide/Show block <^K-Shift+H>
• Indent block <^K-Tab>
• Indent block one position adding a space <^K-I>
• Insert line <Enter>
• Insert mode on/off <Ins>
• Line down <Down arrow>
• Line up <Up arrow>
• Mark line <^K-L>
• Mark word <^K-T>
• Move block <^K+Shift+V>
• Move block <^K+V>
• Move to beginning of block <^Q-B>
• Move to end of block <^Q-K>
• Page down <PgDn>
• Page up <PgUp>
• Paste from Clipboard <Shift+Ins>
• Paste from special Clipboard <^K-Shift+P>
• Play a macro <^F10>
• PMacro's Trigger <^Space>
• Read block from disk <^K-R>
• Replace the block by the Clipboard block <Shift+^Ins>
• Report the length of the block <^Q-L>
• Scroll the screen one line down <^Z>
• Scroll the screen one line up <^W>
• Search the ( where the cursor is <Shift+^9>
• Search the ) where the cursor is <Shift+^0>
• Search the [ where the cursor is <Shift+^[>
• Search the ] where the cursor is <Shift+^]>
• Search the close curly bracket where the cursor is <^]>
• Search the open curly bracket where the cursor is <^[>
• Set beginning of block <^K-B>
• Set beginning of block <^K-Shift+B>
• Set end of block <^K-K>
• Set end of block <^K-Shift+K>
• Set marker <^K n*>
• Set the default options (Not in RHIDE) <Alt+G>
• Set the options of the current window (Not in RHIDE) <Alt+L>
• Smart Indent block <^Tab>
• Smart Unindent block <Shift+^Tab>
• Start recording a macro <Shift+F10>
• Stop recording a macro <Alt+F10>
• Top of file <^Q-R>
• Top of window <^Q-E>
• Undo <Alt+Backspace>
• Unindent block <^K-Shift+Tab>
• Unindent block one character - not an x position <^K-U>
• Word left <^Left arrow>
• Word right <^Right arrow>
• Write block to disk <^K-W>