joe-4.4/0000775000175000017500000000000013041211215007127 500000000000000joe-4.4/acinclude.m40000664000175000017500000000506513016320753011260 00000000000000dnl ------------------ dnl Check for properly working isblank() dnl ------------------ AC_DEFUN([joe_ISBLANK], [AC_CACHE_CHECK([whether isblank() works correctly with side effect expressions], [joe_cv_isblank], [AC_TRY_RUN([ #include int main() { int a = 0; isblank(a++); exit(a != 1); } ], [joe_cv_isblank=yes], [joe_cv_isblank=no], [joe_cv_isblank=no]) ]) if test "$joe_cv_isblank" = yes; then AC_DEFINE([HAVE_WORKING_ISBLANK], 1, [Define if isblank() works with expressions with side effects]) fi ]) dnl ------------------ dnl Check if setpgrp must have two arguments dnl autoconf-own macro is damaged for *BSD systems dnl ------------------ AC_DEFUN([joe_SETPGRP], [AC_CACHE_CHECK([whether setpgrp() takes no arguments], [joe_cv_setpgrp_void], [AC_TRY_RUN([ #if HAVE_UNISTD_H #include #endif int main() { /* exit succesfully if setpgrp() takes two args (*BSD systems) */ exit(setpgrp(0, 0) != 0); }], [joe_cv_setpgrp_void=no], [joe_cv_setpgrp_void=yes], [joe_cv_setpgrp_void=yes]) ]) if test "$joe_cv_setpgrp_void" = yes; then AC_DEFINE([SETPGRP_VOID], 1, [Define if setpgrp() takes no arguments]) fi ]) dnl ------------------ dnl Check to see if signal handlers must be reinstalled when invoked dnl ------------------ AC_DEFUN([joe_REINSTALL_SIGHANDLERS], [AC_CACHE_CHECK([whether sighandlers must be reinstalled], [joe_cv_reinstall_sighandlers], [AC_TRY_RUN([ #if HAVE_UNISTD_H #include #endif #if HAVE_SIGNAL_H #include #endif #ifndef HAVE_SIGHANDLER_T typedef RETSIGTYPE (*sighandler_t)(int); #endif int nsigint; void set_signal(int signum, sighandler_t handler) { #if HAVE_SIGACTION struct sigaction sact; sact.sa_handler = handler; sact.sa_flags = 0; sigemptyset(&sact.sa_mask); sigaction(signum, &sact, NULL); #elif HAVE_SIGVEC struct sigvec svec; svec.sv_handler = handler; svec.sv_flags = 0; sigemptyset(&svec.sv_mask); sigvec(signum, &svec, NULL); #else signal(signum, handler); #endif } RETSIGTYPE sigint(int s) { nsigint++; } int main() { nsigint = 0; set_signal(SIGINT, sigint); kill((int)getpid(), SIGINT); kill((int)getpid(), SIGINT); /* exit succesfully if don't have to reinstall sighandler when invoked */ exit(nsigint != 2); }], [joe_cv_reinstall_sighandlers=no], [joe_cv_reinstall_sighandlers=yes], [joe_cv_reinstall_sighandlers=yes]) ]) if test "$joe_cv_reinstall_sighandlers" = yes; then AC_DEFINE([NEED_TO_REINSTALL_SIGNAL], 1, [Define if we have to reinstall signal handler when invoked]) fi ]) joe-4.4/README.md0000664000175000017500000002210513016320753010340 00000000000000# Joe's Own Editor [User manual](https://sourceforge.net/p/joe-editor/mercurial/ci/default/tree/docs/man.md) [Release Notes](https://sourceforge.net/p/joe-editor/mercurial/ci/default/tree/NEWS.md) [List of Commands](https://sourceforge.net/p/joe-editor/mercurial/ci/default/tree/docs/man.md#list) [List of Options](https://sourceforge.net/p/joe-editor/mercurial/ci/default/tree/docs/man.md#options) [JOE for Windows tips](https://sourceforge.net/p/joe-editor/mercurial/ci/windows/tree/docs/windows.md) [Hacking](https://sourceforge.net/p/joe-editor/mercurial/ci/default/tree/docs/hacking.md) [Project page](http://www.sourceforge.net/projects/joe-editor) [Download source](https://sourceforge.net/projects/joe-editor/files/) [Build instructions](https://sourceforge.net/p/joe-editor/mercurial/ci/default/tree/INSTALL.md) [History](https://sourceforge.net/p/joe-editor/mercurial/ci/default/tree/docs/history.md)

JOE is a full featured terminal-based screen editor which is distributed under the GNU General Public License (GPL). JOE has been around since 1988 and comes standard with many Linux distributions.

JOE is being maintained by its original author Joseph Allen, plus all of the people who send bug reports, feature suggestions and patches to the project web site. JOE is hosted by SourceForge.net and its source code is controlled under Mercurial.

JOE is a blending of MicroPro's venerable microcomputer word processor WordStar and Richard Stallman's famous LISP based text editor GNU-EMACS (but it does not use code from either program): most of the basic editing keys are the same as in WordStar as is the overall feel of the editor. JOE also has some of the key bindings and many of the powerful features of EMACS.

JOE is written in C and its only dependency is libc. This makes JOE very easy to build (just "configure" and "make install"), making it feasible to include on small systems and recovery disks. The compiled binary is about 300K in x86. Note that JOE can use either the termcap or terminfo terminal capabilities databases (or a built-in termcap entry for ANSI terminals). The choice is controlled by a "configure" option. If terminfo is used, a library is required to access the database (on some systems this library is ncurses, but JOE does not use curses to control the terminal- it has its own code for this).

Much of the look and feel of JOE is determined by its simple configuration file "joerc". Several variants of the editor are installed by default in addition to "joe": "jmacs" (emulate GNU-EMACS), "jstar" emulate WordStar, "jpico" emulate the Pine mailer editor PICO and "rjoe"- a restricted version of JOE which allows the used to only edit the file given on the command line. JOE is linked to several names. The name which is used to invoke the editor with "rc" tacked on the end gives the name of configuration file to use. It is thus easy for you to make your own variant if you want. Also you can customize the editor by copying the system "joerc" file to your home directory.

Here is a basic screen shot of JOE running in a Cygwin console:

![screen capture](http://joe-editor.sourceforge.net/capture.gif)

Here is a screen shot showing several windows- the first has some example double-wide characters, the second is the same buffer as the first, but in hex-dump view mode, the third is a shell window and the fourth shows a selected rectangular block of numbers and their sum:

![elaborate screen capture](http://joe-editor.sourceforge.net/elaborate.gif) ### JOE has the following features: * Multi-file search and replace- file list is either given on command line or by a UNIX command (grep/find) run from within JOE. * Mouse support, including wheel (works best when using xterm). The mouse can resize windows, scroll windows, select and paste text, and select menu entries. * Context display on status line: allows you to see name of function cursor is in. * UTF-8 support, optional auto-detect of UTF-8 files. * Syntax highlighting for more than 40 languages. * Hexadecimal edit mode. Use JOE as a disk editor: joe -overwrite -hex /dev/hda1,0,512 (edit first sector of /dev/hda1). * Non-destructive editing of binary files even when handling MS-DOS or UNIX line endings. * Swap file allows editing files larger than memory. * Context sensitive on-line help. * Bash-like TAB completion and history for all prompts, or jump into the completion menu and use it to traverse the file system. * Complete word in edit buffer by hitting ESC Enter (uses other words in buffer for dictionary). * EMACS-compatible file locks and file modification checking. * Shell windows. * Multiple-windows onto same or different files. * Compile and step through errors or Grep and step through finds. * Goto matching character delimiter "() [] {} <>" which skips comments and quoted matter. * Goto matching word delimiter, including XML tags and C preprocessor directives. * Ctrl-arrow key block selection. * Search and replace system, including regular expression and optional incremental search. Regular expression key for matching balanced C expressions. * Tags file search (tab completion at tags search prompt uses tags file as database). * Spell check commands which invoke aspell or ispell. Language for aspell can be passed through editor. * Paragraph format which preserves news/mail quoting indentation characters. * Unlimited Undo and Redo. * Yank buffer allows stepping through and insertion of previously deleted text. * State file restores history buffers, yank buffer and last file cursor positions. * Cursor position history allows you to step through previously visited areas of a file. * Multiple interactive keyboard macros. Macros can be assigned to key sequences in joerc file. * Block move/copy/delete/filter. * Rectangle (columnar) block mode- search and replace can be narrowed to the rectangular block. Rectangular blocks can be filtered through UNIX commands. * Overtype/Insert modes. * Indent/Unindent (shift block left or right). * Auto-indent mode. * Picture mode for ASCII graphics. * Line number mode displays line number of each line. * Powerful scientific calculator with block statistics functions (sum/standard-deviation/count highlighted block of numbers). * Termcap/Terminfo support allows JOE to use any terminal or terminal emulator. * Can accept data from a pipe, for example: ls | joe

JOE does not have these features (yet):

  • Vertical windows
  • Folding
  • Right to left editing for Hebrew and Arabic
  • Direct editing of 16-bit character sets such as UCS-16 and BIG5
  • All encompassing macro language like elisp in GNU-EMACS
  • Background spell checking, like Microsoft WORD
  • Highlight all matching words
  • Automatic unzip/untar
  • Built-in FTP
  • X-Window version (use inside a terminal emulator)
  • Interface to debugger

Here are some other editors to consider:

http://www.gnu.org/software/emacs Richard Stallman's powerful LISP-based editor. http://www.jedsoft.org/jed John E. Davis' version of EMACS using the S-Lang language. http://www.jasspa.com Micro Emacs http://www.vile.cx Paul Fox's vi clone (built on top of Micro Emacs). Now maintained by Tom Dickey and others. http://www.nano-editor.org An open source PICO clone. http://www.washington.edu.pine/faq/whatis.html PICO: A simple editor built on Micro Emacs. http://www.vim.org Bram Moolenaar's vi clone http://elvis.the-little-red-haired-girl.org Elvis: A small vi clone http://www.jedit.org Powerful editor written in Java http://www.nedit.org X-Windowing System editor http://www.ibiblio.org/mc Midnight Commander file manager with built-in text editor with highlighting. Can browse ZIP and TAR files.
http://www.cs.yorku.ca/~oz/wily A UNIX/X clone of Rob Pike's Plan9 editor ACME. Originally written by Gary Capell, but now maintained by Ozan Yigit. This is an interesting minimalist IDE. http://www.eclipse.org/downloads Huge IDE written in Java. Performs same function as Wily, but is literally 1300 times larger. ftp://netlib.bell-labs.com/netlib/research/sam.shar.gz UNIX/X port of Rob Pike's Plan9 editor SAM. This interesting editor supports multi-file regular expression search & replace with unlimited undo. http://sed.sourceforge.net UNIX Stream EDitor. If you're on UNIX, you already have this editor, but follow this link to see the amazing things that can be done with it. joe-4.4/charmaps/0000775000175000017500000000000013041211214010724 500000000000000joe-4.4/charmaps/klingon.in0000664000175000017500000002516513016320753012661 00000000000000 Klingon-ASCII % / % version: 1.0 % An 8-bit character set with Klingon characters in range 0xD0 - 0xFF and % KOI8-R (ASCII w/ line drawing) for the rest. CHARMAP /x00 NULL (NUL) /x01 START OF HEADING (SOH) /x02 START OF TEXT (STX) /x03 END OF TEXT (ETX) /x04 END OF TRANSMISSION (EOT) /x05 ENQUIRY (ENQ) /x06 ACKNOWLEDGE (ACK) /x07 BELL (BEL) /x08 BACKSPACE (BS) /x09 CHARACTER TABULATION (HT) /x0a LINE FEED (LF) /x0b LINE TABULATION (VT) /x0c FORM FEED (FF) /x0d CARRIAGE RETURN (CR) /x0e SHIFT OUT (SO) /x0f SHIFT IN (SI) /x10 DATALINK ESCAPE (DLE) /x11 DEVICE CONTROL ONE (DC1) /x12 DEVICE CONTROL TWO (DC2) /x13 DEVICE CONTROL THREE (DC3) /x14 DEVICE CONTROL FOUR (DC4) /x15 NEGATIVE ACKNOWLEDGE (NAK) /x16 SYNCHRONOUS IDLE (SYN) /x17 END OF TRANSMISSION BLOCK (ETB) /x18 CANCEL (CAN) /x19 END OF MEDIUM (EM) /x1a SUBSTITUTE (SUB) /x1b ESCAPE (ESC) /x1c FILE SEPARATOR (IS4) /x1d GROUP SEPARATOR (IS3) /x1e RECORD SEPARATOR (IS2) /x1f UNIT SEPARATOR (IS1) /x20 SPACE /x21 EXCLAMATION MARK /x22 QUOTATION MARK /x23 NUMBER SIGN /x24 DOLLAR SIGN /x25 PERCENT SIGN /x26 AMPERSAND /x27 APOSTROPHE /x28 LEFT PARENTHESIS /x29 RIGHT PARENTHESIS /x2a ASTERISK /x2b PLUS SIGN /x2c COMMA /x2d HYPHEN-MINUS /x2e FULL STOP /x2f SOLIDUS /x30 DIGIT ZERO /x31 DIGIT ONE /x32 DIGIT TWO /x33 DIGIT THREE /x34 DIGIT FOUR /x35 DIGIT FIVE /x36 DIGIT SIX /x37 DIGIT SEVEN /x38 DIGIT EIGHT /x39 DIGIT NINE /x3a COLON /x3b SEMICOLON /x3c LESS-THAN SIGN /x3d EQUALS SIGN /x3e GREATER-THAN SIGN /x3f QUESTION MARK /x40 COMMERCIAL AT /x41 LATIN CAPITAL LETTER A /x42 LATIN CAPITAL LETTER B /x43 LATIN CAPITAL LETTER C /x44 LATIN CAPITAL LETTER D /x45 LATIN CAPITAL LETTER E /x46 LATIN CAPITAL LETTER F /x47 LATIN CAPITAL LETTER G /x48 LATIN CAPITAL LETTER H /x49 LATIN CAPITAL LETTER I /x4a LATIN CAPITAL LETTER J /x4b LATIN CAPITAL LETTER K /x4c LATIN CAPITAL LETTER L /x4d LATIN CAPITAL LETTER M /x4e LATIN CAPITAL LETTER N /x4f LATIN CAPITAL LETTER O /x50 LATIN CAPITAL LETTER P /x51 LATIN CAPITAL LETTER Q /x52 LATIN CAPITAL LETTER R /x53 LATIN CAPITAL LETTER S /x54 LATIN CAPITAL LETTER T /x55 LATIN CAPITAL LETTER U /x56 LATIN CAPITAL LETTER V /x57 LATIN CAPITAL LETTER W /x58 LATIN CAPITAL LETTER X /x59 LATIN CAPITAL LETTER Y /x5a LATIN CAPITAL LETTER Z /x5b LEFT SQUARE BRACKET /x5c REVERSE SOLIDUS /x5d RIGHT SQUARE BRACKET /x5e CIRCUMFLEX ACCENT /x5f LOW LINE /x60 GRAVE ACCENT /x61 LATIN SMALL LETTER A /x62 LATIN SMALL LETTER B /x63 LATIN SMALL LETTER C /x64 LATIN SMALL LETTER D /x65 LATIN SMALL LETTER E /x66 LATIN SMALL LETTER F /x67 LATIN SMALL LETTER G /x68 LATIN SMALL LETTER H /x69 LATIN SMALL LETTER I /x6a LATIN SMALL LETTER J /x6b LATIN SMALL LETTER K /x6c LATIN SMALL LETTER L /x6d LATIN SMALL LETTER M /x6e LATIN SMALL LETTER N /x6f LATIN SMALL LETTER O /x70 LATIN SMALL LETTER P /x71 LATIN SMALL LETTER Q /x72 LATIN SMALL LETTER R /x73 LATIN SMALL LETTER S /x74 LATIN SMALL LETTER T /x75 LATIN SMALL LETTER U /x76 LATIN SMALL LETTER V /x77 LATIN SMALL LETTER W /x78 LATIN SMALL LETTER X /x79 LATIN SMALL LETTER Y /x7a LATIN SMALL LETTER Z /x7b LEFT CURLY BRACKET /x7c VERTICAL LINE /x7d RIGHT CURLY BRACKET /x7e TILDE /x7f DELETE (DEL) /x80 BOX DRAWINGS LIGHT HORIZONTAL /x81 BOX DRAWINGS LIGHT VERTICAL /x82 BOX DRAWINGS LIGHT DOWN AND RIGHT /x83 BOX DRAWINGS LIGHT DOWN AND LEFT /x84 BOX DRAWINGS LIGHT UP AND RIGHT /x85 BOX DRAWINGS LIGHT UP AND LEFT /x86 BOX DRAWINGS LIGHT VERTICAL AND RIGHT /x87 BOX DRAWINGS LIGHT VERTICAL AND LEFT /x88 BOX DRAWINGS LIGHT DOWN AND HORIZONTAL /x89 BOX DRAWINGS LIGHT UP AND HORIZONTAL /x8a BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL /x8b UPPER HALF BLOCK /x8c LOWER HALF BLOCK /x8d FULL BLOCK /x8e LEFT HALF BLOCK /x8f RIGHT HALF BLOCK /x90 LIGHT SHADE /x91 MEDIUM SHADE /x92 DARK SHADE /x93 TOP HALF INTEGRAL /x94 BLACK SQUARE /x95 BULLET OPERATOR /x96 SQUARE ROOT /x97 ALMOST EQUAL TO /x98 LESS-THAN OR EQUAL TO /x99 GREATER-THAN OR EQUAL TO /x9a NO-BREAK SPACE /x9b BOTTOM HALF INTEGRAL /x9c DEGREE SIGN /x9d SUPERSCRIPT TWO /x9e MIDDLE DOT /x9f DIVISION SIGN /xa0 BOX DRAWINGS DOUBLE HORIZONTAL /xa1 BOX DRAWINGS DOUBLE VERTICAL /xa2 BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE /xa4 BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE /xa5 BOX DRAWINGS DOUBLE DOWN AND RIGHT /xa6 BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE /xa7 BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE /xa8 BOX DRAWINGS DOUBLE DOWN AND LEFT /xa9 BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE /xaa BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE /xab BOX DRAWINGS DOUBLE UP AND RIGHT /xac BOX DRAWINGS UP SINGLE AND LEFT DOUBLE /xad BOX DRAWINGS UP DOUBLE AND LEFT SINGLE /xae BOX DRAWINGS DOUBLE UP AND LEFT /xaf BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE /xb0 BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE /xb1 BOX DRAWINGS DOUBLE VERTICAL AND RIGHT /xb2 BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE /xb4 BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE /xb5 BOX DRAWINGS DOUBLE VERTICAL AND LEFT /xb6 BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE /xb7 BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE /xb8 BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL /xb9 BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE /xba BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE /xbb BOX DRAWINGS DOUBLE UP AND HORIZONTAL /xbc BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE /xbd BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE /xbe BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL /xbf COPYRIGHT SIGN /xd0 Klingon letter A /xd1 Klingon letter B /xd2 Klingon letter CH /xd3 Klingon letter D /xd4 Klingon letter E /xd5 Klingon letter GH /xd6 Klingon letter H /xd7 Klingon letter I /xd8 Klingon letter J /xd9 Klingon letter L /xda Klingon letter M /xdb Klingon letter N /xdc Klingon letter NG /xdd Klingon letter O /xde Klingon letter P /xdf Klingon letter Q /xe0 Klingon letter QH /xe1 Klingon letter R /xe2 Klingon letter S /xe3 Klingon letter T /xe4 Klingon letter TLH /xe5 Klingon letter U /xe6 Klingon letter V /xe7 Klingon letter W /xe8 Klingon letter Y /xe9 Klingon letter glottal stop /xf0 Klingon digit 0 /xf1 Klingon digit 1 /xf2 Klingon digit 2 /xf3 Klingon digit 3 /xf4 Klingon digit 4 /xf5 Klingon digit 5 /xf6 Klingon digit 6 /xf7 Klingon digit 7 /xf8 Klingon digit 8 /xf9 Klingon digit 9 /xfd Klingon , /xfe Klingon full stop /xff Klingon mummification glyph END CHARMAP joe-4.4/depcomp0000755000175000017500000005601613016320765010447 00000000000000#! /bin/sh # depcomp - compile a program generating dependencies as side-effects scriptversion=2013-05-30.07; # UTC # Copyright (C) 1999-2014 Free Software Foundation, Inc. # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2, or (at your option) # any later version. # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # You should have received a copy of the GNU General Public License # along with this program. If not, see . # As a special exception to the GNU General Public License, if you # distribute this file as part of a program that contains a # configuration script generated by Autoconf, you may include it under # the same distribution terms that you use for the rest of that program. # Originally written by Alexandre Oliva . case $1 in '') echo "$0: No command. Try '$0 --help' for more information." 1>&2 exit 1; ;; -h | --h*) cat <<\EOF Usage: depcomp [--help] [--version] PROGRAM [ARGS] Run PROGRAMS ARGS to compile a file, generating dependencies as side-effects. Environment variables: depmode Dependency tracking mode. source Source file read by 'PROGRAMS ARGS'. object Object file output by 'PROGRAMS ARGS'. DEPDIR directory where to store dependencies. depfile Dependency file to output. tmpdepfile Temporary file to use when outputting dependencies. libtool Whether libtool is used (yes/no). Report bugs to . EOF exit $? ;; -v | --v*) echo "depcomp $scriptversion" exit $? ;; esac # Get the directory component of the given path, and save it in the # global variables '$dir'. Note that this directory component will # be either empty or ending with a '/' character. This is deliberate. set_dir_from () { case $1 in */*) dir=`echo "$1" | sed -e 's|/[^/]*$|/|'`;; *) dir=;; esac } # Get the suffix-stripped basename of the given path, and save it the # global variable '$base'. set_base_from () { base=`echo "$1" | sed -e 's|^.*/||' -e 's/\.[^.]*$//'` } # If no dependency file was actually created by the compiler invocation, # we still have to create a dummy depfile, to avoid errors with the # Makefile "include basename.Plo" scheme. make_dummy_depfile () { echo "#dummy" > "$depfile" } # Factor out some common post-processing of the generated depfile. # Requires the auxiliary global variable '$tmpdepfile' to be set. aix_post_process_depfile () { # If the compiler actually managed to produce a dependency file, # post-process it. if test -f "$tmpdepfile"; then # Each line is of the form 'foo.o: dependency.h'. # Do two passes, one to just change these to # $object: dependency.h # and one to simply output # dependency.h: # which is needed to avoid the deleted-header problem. { sed -e "s,^.*\.[$lower]*:,$object:," < "$tmpdepfile" sed -e "s,^.*\.[$lower]*:[$tab ]*,," -e 's,$,:,' < "$tmpdepfile" } > "$depfile" rm -f "$tmpdepfile" else make_dummy_depfile fi } # A tabulation character. tab=' ' # A newline character. nl=' ' # Character ranges might be problematic outside the C locale. # These definitions help. upper=ABCDEFGHIJKLMNOPQRSTUVWXYZ lower=abcdefghijklmnopqrstuvwxyz digits=0123456789 alpha=${upper}${lower} if test -z "$depmode" || test -z "$source" || test -z "$object"; then echo "depcomp: Variables source, object and depmode must be set" 1>&2 exit 1 fi # Dependencies for sub/bar.o or sub/bar.obj go into sub/.deps/bar.Po. depfile=${depfile-`echo "$object" | sed 's|[^\\/]*$|'${DEPDIR-.deps}'/&|;s|\.\([^.]*\)$|.P\1|;s|Pobj$|Po|'`} tmpdepfile=${tmpdepfile-`echo "$depfile" | sed 's/\.\([^.]*\)$/.T\1/'`} rm -f "$tmpdepfile" # Avoid interferences from the environment. gccflag= dashmflag= # Some modes work just like other modes, but use different flags. We # parameterize here, but still list the modes in the big case below, # to make depend.m4 easier to write. Note that we *cannot* use a case # here, because this file can only contain one case statement. if test "$depmode" = hp; then # HP compiler uses -M and no extra arg. gccflag=-M depmode=gcc fi if test "$depmode" = dashXmstdout; then # This is just like dashmstdout with a different argument. dashmflag=-xM depmode=dashmstdout fi cygpath_u="cygpath -u -f -" if test "$depmode" = msvcmsys; then # This is just like msvisualcpp but w/o cygpath translation. # Just convert the backslash-escaped backslashes to single forward # slashes to satisfy depend.m4 cygpath_u='sed s,\\\\,/,g' depmode=msvisualcpp fi if test "$depmode" = msvc7msys; then # This is just like msvc7 but w/o cygpath translation. # Just convert the backslash-escaped backslashes to single forward # slashes to satisfy depend.m4 cygpath_u='sed s,\\\\,/,g' depmode=msvc7 fi if test "$depmode" = xlc; then # IBM C/C++ Compilers xlc/xlC can output gcc-like dependency information. gccflag=-qmakedep=gcc,-MF depmode=gcc fi case "$depmode" in gcc3) ## gcc 3 implements dependency tracking that does exactly what ## we want. Yay! Note: for some reason libtool 1.4 doesn't like ## it if -MD -MP comes after the -MF stuff. Hmm. ## Unfortunately, FreeBSD c89 acceptance of flags depends upon ## the command line argument order; so add the flags where they ## appear in depend2.am. Note that the slowdown incurred here ## affects only configure: in makefiles, %FASTDEP% shortcuts this. for arg do case $arg in -c) set fnord "$@" -MT "$object" -MD -MP -MF "$tmpdepfile" "$arg" ;; *) set fnord "$@" "$arg" ;; esac shift # fnord shift # $arg done "$@" stat=$? if test $stat -ne 0; then rm -f "$tmpdepfile" exit $stat fi mv "$tmpdepfile" "$depfile" ;; gcc) ## Note that this doesn't just cater to obsosete pre-3.x GCC compilers. ## but also to in-use compilers like IMB xlc/xlC and the HP C compiler. ## (see the conditional assignment to $gccflag above). ## There are various ways to get dependency output from gcc. Here's ## why we pick this rather obscure method: ## - Don't want to use -MD because we'd like the dependencies to end ## up in a subdir. Having to rename by hand is ugly. ## (We might end up doing this anyway to support other compilers.) ## - The DEPENDENCIES_OUTPUT environment variable makes gcc act like ## -MM, not -M (despite what the docs say). Also, it might not be ## supported by the other compilers which use the 'gcc' depmode. ## - Using -M directly means running the compiler twice (even worse ## than renaming). if test -z "$gccflag"; then gccflag=-MD, fi "$@" -Wp,"$gccflag$tmpdepfile" stat=$? if test $stat -ne 0; then rm -f "$tmpdepfile" exit $stat fi rm -f "$depfile" echo "$object : \\" > "$depfile" # The second -e expression handles DOS-style file names with drive # letters. sed -e 's/^[^:]*: / /' \ -e 's/^['$alpha']:\/[^:]*: / /' < "$tmpdepfile" >> "$depfile" ## This next piece of magic avoids the "deleted header file" problem. ## The problem is that when a header file which appears in a .P file ## is deleted, the dependency causes make to die (because there is ## typically no way to rebuild the header). We avoid this by adding ## dummy dependencies for each header file. Too bad gcc doesn't do ## this for us directly. ## Some versions of gcc put a space before the ':'. On the theory ## that the space means something, we add a space to the output as ## well. hp depmode also adds that space, but also prefixes the VPATH ## to the object. Take care to not repeat it in the output. ## Some versions of the HPUX 10.20 sed can't process this invocation ## correctly. Breaking it into two sed invocations is a workaround. tr ' ' "$nl" < "$tmpdepfile" \ | sed -e 's/^\\$//' -e '/^$/d' -e "s|.*$object$||" -e '/:$/d' \ | sed -e 's/$/ :/' >> "$depfile" rm -f "$tmpdepfile" ;; hp) # This case exists only to let depend.m4 do its work. It works by # looking at the text of this script. This case will never be run, # since it is checked for above. exit 1 ;; sgi) if test "$libtool" = yes; then "$@" "-Wp,-MDupdate,$tmpdepfile" else "$@" -MDupdate "$tmpdepfile" fi stat=$? if test $stat -ne 0; then rm -f "$tmpdepfile" exit $stat fi rm -f "$depfile" if test -f "$tmpdepfile"; then # yes, the sourcefile depend on other files echo "$object : \\" > "$depfile" # Clip off the initial element (the dependent). Don't try to be # clever and replace this with sed code, as IRIX sed won't handle # lines with more than a fixed number of characters (4096 in # IRIX 6.2 sed, 8192 in IRIX 6.5). We also remove comment lines; # the IRIX cc adds comments like '#:fec' to the end of the # dependency line. tr ' ' "$nl" < "$tmpdepfile" \ | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' \ | tr "$nl" ' ' >> "$depfile" echo >> "$depfile" # The second pass generates a dummy entry for each header file. tr ' ' "$nl" < "$tmpdepfile" \ | sed -e 's/^.*\.o://' -e 's/#.*$//' -e '/^$/ d' -e 's/$/:/' \ >> "$depfile" else make_dummy_depfile fi rm -f "$tmpdepfile" ;; xlc) # This case exists only to let depend.m4 do its work. It works by # looking at the text of this script. This case will never be run, # since it is checked for above. exit 1 ;; aix) # The C for AIX Compiler uses -M and outputs the dependencies # in a .u file. In older versions, this file always lives in the # current directory. Also, the AIX compiler puts '$object:' at the # start of each line; $object doesn't have directory information. # Version 6 uses the directory in both cases. set_dir_from "$object" set_base_from "$object" if test "$libtool" = yes; then tmpdepfile1=$dir$base.u tmpdepfile2=$base.u tmpdepfile3=$dir.libs/$base.u "$@" -Wc,-M else tmpdepfile1=$dir$base.u tmpdepfile2=$dir$base.u tmpdepfile3=$dir$base.u "$@" -M fi stat=$? if test $stat -ne 0; then rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" exit $stat fi for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" do test -f "$tmpdepfile" && break done aix_post_process_depfile ;; tcc) # tcc (Tiny C Compiler) understand '-MD -MF file' since version 0.9.26 # FIXME: That version still under development at the moment of writing. # Make that this statement remains true also for stable, released # versions. # It will wrap lines (doesn't matter whether long or short) with a # trailing '\', as in: # # foo.o : \ # foo.c \ # foo.h \ # # It will put a trailing '\' even on the last line, and will use leading # spaces rather than leading tabs (at least since its commit 0394caf7 # "Emit spaces for -MD"). "$@" -MD -MF "$tmpdepfile" stat=$? if test $stat -ne 0; then rm -f "$tmpdepfile" exit $stat fi rm -f "$depfile" # Each non-empty line is of the form 'foo.o : \' or ' dep.h \'. # We have to change lines of the first kind to '$object: \'. sed -e "s|.*:|$object :|" < "$tmpdepfile" > "$depfile" # And for each line of the second kind, we have to emit a 'dep.h:' # dummy dependency, to avoid the deleted-header problem. sed -n -e 's|^ *\(.*\) *\\$|\1:|p' < "$tmpdepfile" >> "$depfile" rm -f "$tmpdepfile" ;; ## The order of this option in the case statement is important, since the ## shell code in configure will try each of these formats in the order ## listed in this file. A plain '-MD' option would be understood by many ## compilers, so we must ensure this comes after the gcc and icc options. pgcc) # Portland's C compiler understands '-MD'. # Will always output deps to 'file.d' where file is the root name of the # source file under compilation, even if file resides in a subdirectory. # The object file name does not affect the name of the '.d' file. # pgcc 10.2 will output # foo.o: sub/foo.c sub/foo.h # and will wrap long lines using '\' : # foo.o: sub/foo.c ... \ # sub/foo.h ... \ # ... set_dir_from "$object" # Use the source, not the object, to determine the base name, since # that's sadly what pgcc will do too. set_base_from "$source" tmpdepfile=$base.d # For projects that build the same source file twice into different object # files, the pgcc approach of using the *source* file root name can cause # problems in parallel builds. Use a locking strategy to avoid stomping on # the same $tmpdepfile. lockdir=$base.d-lock trap " echo '$0: caught signal, cleaning up...' >&2 rmdir '$lockdir' exit 1 " 1 2 13 15 numtries=100 i=$numtries while test $i -gt 0; do # mkdir is a portable test-and-set. if mkdir "$lockdir" 2>/dev/null; then # This process acquired the lock. "$@" -MD stat=$? # Release the lock. rmdir "$lockdir" break else # If the lock is being held by a different process, wait # until the winning process is done or we timeout. while test -d "$lockdir" && test $i -gt 0; do sleep 1 i=`expr $i - 1` done fi i=`expr $i - 1` done trap - 1 2 13 15 if test $i -le 0; then echo "$0: failed to acquire lock after $numtries attempts" >&2 echo "$0: check lockdir '$lockdir'" >&2 exit 1 fi if test $stat -ne 0; then rm -f "$tmpdepfile" exit $stat fi rm -f "$depfile" # Each line is of the form `foo.o: dependent.h', # or `foo.o: dep1.h dep2.h \', or ` dep3.h dep4.h \'. # Do two passes, one to just change these to # `$object: dependent.h' and one to simply `dependent.h:'. sed "s,^[^:]*:,$object :," < "$tmpdepfile" > "$depfile" # Some versions of the HPUX 10.20 sed can't process this invocation # correctly. Breaking it into two sed invocations is a workaround. sed 's,^[^:]*: \(.*\)$,\1,;s/^\\$//;/^$/d;/:$/d' < "$tmpdepfile" \ | sed -e 's/$/ :/' >> "$depfile" rm -f "$tmpdepfile" ;; hp2) # The "hp" stanza above does not work with aCC (C++) and HP's ia64 # compilers, which have integrated preprocessors. The correct option # to use with these is +Maked; it writes dependencies to a file named # 'foo.d', which lands next to the object file, wherever that # happens to be. # Much of this is similar to the tru64 case; see comments there. set_dir_from "$object" set_base_from "$object" if test "$libtool" = yes; then tmpdepfile1=$dir$base.d tmpdepfile2=$dir.libs/$base.d "$@" -Wc,+Maked else tmpdepfile1=$dir$base.d tmpdepfile2=$dir$base.d "$@" +Maked fi stat=$? if test $stat -ne 0; then rm -f "$tmpdepfile1" "$tmpdepfile2" exit $stat fi for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" do test -f "$tmpdepfile" && break done if test -f "$tmpdepfile"; then sed -e "s,^.*\.[$lower]*:,$object:," "$tmpdepfile" > "$depfile" # Add 'dependent.h:' lines. sed -ne '2,${ s/^ *// s/ \\*$// s/$/:/ p }' "$tmpdepfile" >> "$depfile" else make_dummy_depfile fi rm -f "$tmpdepfile" "$tmpdepfile2" ;; tru64) # The Tru64 compiler uses -MD to generate dependencies as a side # effect. 'cc -MD -o foo.o ...' puts the dependencies into 'foo.o.d'. # At least on Alpha/Redhat 6.1, Compaq CCC V6.2-504 seems to put # dependencies in 'foo.d' instead, so we check for that too. # Subdirectories are respected. set_dir_from "$object" set_base_from "$object" if test "$libtool" = yes; then # Libtool generates 2 separate objects for the 2 libraries. These # two compilations output dependencies in $dir.libs/$base.o.d and # in $dir$base.o.d. We have to check for both files, because # one of the two compilations can be disabled. We should prefer # $dir$base.o.d over $dir.libs/$base.o.d because the latter is # automatically cleaned when .libs/ is deleted, while ignoring # the former would cause a distcleancheck panic. tmpdepfile1=$dir$base.o.d # libtool 1.5 tmpdepfile2=$dir.libs/$base.o.d # Likewise. tmpdepfile3=$dir.libs/$base.d # Compaq CCC V6.2-504 "$@" -Wc,-MD else tmpdepfile1=$dir$base.d tmpdepfile2=$dir$base.d tmpdepfile3=$dir$base.d "$@" -MD fi stat=$? if test $stat -ne 0; then rm -f "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" exit $stat fi for tmpdepfile in "$tmpdepfile1" "$tmpdepfile2" "$tmpdepfile3" do test -f "$tmpdepfile" && break done # Same post-processing that is required for AIX mode. aix_post_process_depfile ;; msvc7) if test "$libtool" = yes; then showIncludes=-Wc,-showIncludes else showIncludes=-showIncludes fi "$@" $showIncludes > "$tmpdepfile" stat=$? grep -v '^Note: including file: ' "$tmpdepfile" if test $stat -ne 0; then rm -f "$tmpdepfile" exit $stat fi rm -f "$depfile" echo "$object : \\" > "$depfile" # The first sed program below extracts the file names and escapes # backslashes for cygpath. The second sed program outputs the file # name when reading, but also accumulates all include files in the # hold buffer in order to output them again at the end. This only # works with sed implementations that can handle large buffers. sed < "$tmpdepfile" -n ' /^Note: including file: *\(.*\)/ { s//\1/ s/\\/\\\\/g p }' | $cygpath_u | sort -u | sed -n ' s/ /\\ /g s/\(.*\)/'"$tab"'\1 \\/p s/.\(.*\) \\/\1:/ H $ { s/.*/'"$tab"'/ G p }' >> "$depfile" echo >> "$depfile" # make sure the fragment doesn't end with a backslash rm -f "$tmpdepfile" ;; msvc7msys) # This case exists only to let depend.m4 do its work. It works by # looking at the text of this script. This case will never be run, # since it is checked for above. exit 1 ;; #nosideeffect) # This comment above is used by automake to tell side-effect # dependency tracking mechanisms from slower ones. dashmstdout) # Important note: in order to support this mode, a compiler *must* # always write the preprocessed file to stdout, regardless of -o. "$@" || exit $? # Remove the call to Libtool. if test "$libtool" = yes; then while test "X$1" != 'X--mode=compile'; do shift done shift fi # Remove '-o $object'. IFS=" " for arg do case $arg in -o) shift ;; $object) shift ;; *) set fnord "$@" "$arg" shift # fnord shift # $arg ;; esac done test -z "$dashmflag" && dashmflag=-M # Require at least two characters before searching for ':' # in the target name. This is to cope with DOS-style filenames: # a dependency such as 'c:/foo/bar' could be seen as target 'c' otherwise. "$@" $dashmflag | sed "s|^[$tab ]*[^:$tab ][^:][^:]*:[$tab ]*|$object: |" > "$tmpdepfile" rm -f "$depfile" cat < "$tmpdepfile" > "$depfile" # Some versions of the HPUX 10.20 sed can't process this sed invocation # correctly. Breaking it into two sed invocations is a workaround. tr ' ' "$nl" < "$tmpdepfile" \ | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \ | sed -e 's/$/ :/' >> "$depfile" rm -f "$tmpdepfile" ;; dashXmstdout) # This case only exists to satisfy depend.m4. It is never actually # run, as this mode is specially recognized in the preamble. exit 1 ;; makedepend) "$@" || exit $? # Remove any Libtool call if test "$libtool" = yes; then while test "X$1" != 'X--mode=compile'; do shift done shift fi # X makedepend shift cleared=no eat=no for arg do case $cleared in no) set ""; shift cleared=yes ;; esac if test $eat = yes; then eat=no continue fi case "$arg" in -D*|-I*) set fnord "$@" "$arg"; shift ;; # Strip any option that makedepend may not understand. Remove # the object too, otherwise makedepend will parse it as a source file. -arch) eat=yes ;; -*|$object) ;; *) set fnord "$@" "$arg"; shift ;; esac done obj_suffix=`echo "$object" | sed 's/^.*\././'` touch "$tmpdepfile" ${MAKEDEPEND-makedepend} -o"$obj_suffix" -f"$tmpdepfile" "$@" rm -f "$depfile" # makedepend may prepend the VPATH from the source file name to the object. # No need to regex-escape $object, excess matching of '.' is harmless. sed "s|^.*\($object *:\)|\1|" "$tmpdepfile" > "$depfile" # Some versions of the HPUX 10.20 sed can't process the last invocation # correctly. Breaking it into two sed invocations is a workaround. sed '1,2d' "$tmpdepfile" \ | tr ' ' "$nl" \ | sed -e 's/^\\$//' -e '/^$/d' -e '/:$/d' \ | sed -e 's/$/ :/' >> "$depfile" rm -f "$tmpdepfile" "$tmpdepfile".bak ;; cpp) # Important note: in order to support this mode, a compiler *must* # always write the preprocessed file to stdout. "$@" || exit $? # Remove the call to Libtool. if test "$libtool" = yes; then while test "X$1" != 'X--mode=compile'; do shift done shift fi # Remove '-o $object'. IFS=" " for arg do case $arg in -o) shift ;; $object) shift ;; *) set fnord "$@" "$arg" shift # fnord shift # $arg ;; esac done "$@" -E \ | sed -n -e '/^# [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \ -e '/^#line [0-9][0-9]* "\([^"]*\)".*/ s:: \1 \\:p' \ | sed '$ s: \\$::' > "$tmpdepfile" rm -f "$depfile" echo "$object : \\" > "$depfile" cat < "$tmpdepfile" >> "$depfile" sed < "$tmpdepfile" '/^$/d;s/^ //;s/ \\$//;s/$/ :/' >> "$depfile" rm -f "$tmpdepfile" ;; msvisualcpp) # Important note: in order to support this mode, a compiler *must* # always write the preprocessed file to stdout. "$@" || exit $? # Remove the call to Libtool. if test "$libtool" = yes; then while test "X$1" != 'X--mode=compile'; do shift done shift fi IFS=" " for arg do case "$arg" in -o) shift ;; $object) shift ;; "-Gm"|"/Gm"|"-Gi"|"/Gi"|"-ZI"|"/ZI") set fnord "$@" shift shift ;; *) set fnord "$@" "$arg" shift shift ;; esac done "$@" -E 2>/dev/null | sed -n '/^#line [0-9][0-9]* "\([^"]*\)"/ s::\1:p' | $cygpath_u | sort -u > "$tmpdepfile" rm -f "$depfile" echo "$object : \\" > "$depfile" sed < "$tmpdepfile" -n -e 's% %\\ %g' -e '/^\(.*\)$/ s::'"$tab"'\1 \\:p' >> "$depfile" echo "$tab" >> "$depfile" sed < "$tmpdepfile" -n -e 's% %\\ %g' -e '/^\(.*\)$/ s::\1\::p' >> "$depfile" rm -f "$tmpdepfile" ;; msvcmsys) # This case exists only to let depend.m4 do its work. It works by # looking at the text of this script. This case will never be run, # since it is checked for above. exit 1 ;; none) exec "$@" ;; *) echo "Unknown depmode $depmode" 1>&2 exit 1 ;; esac exit 0 # Local Variables: # mode: shell-script # sh-indentation: 2 # eval: (add-hook 'write-file-hooks 'time-stamp) # time-stamp-start: "scriptversion=" # time-stamp-format: "%:y-%02m-%02d.%02H" # time-stamp-time-zone: "UTC" # time-stamp-end: "; # UTC" # End: joe-4.4/setup.hint0000664000175000017500000000034213016320753011104 00000000000000category: Editors requires: cygwin sdesc: "An easy to use, modeless text editor." ldesc: "JOE is a powerful, easy to use, modeless text editor. It uses the same WordStar keybindings used in Borland's development environment." joe-4.4/Makefile.am0000664000175000017500000000212113041210672011105 00000000000000AUTOMAKE_OPTIONS = foreign SUBDIRS = man rc po syntax joe EXTRA_DIST = COPYING docs/hacking.md ChangeLog NEWS.md docs/README.old README.md INSTALL.md INSTALL.AMIGA \ docs/help-system.html charmaps/klingon.in \ cygbuild setup.hint autojoe docs/man.md sysconf_joedir = $(sysconfdir)/joe data_joedir = $(datadir)/joe data_charmapsdir = $(data_joedir)/charmaps data_charmaps_DATA = charmaps/klingon data_docdir = $(docdir) data_doc_DATA = README.md docs/README.old docs/man.md ChangeLog docs/hacking.md NEWS.md install-exec-hook: rm -f $(DESTDIR)$(bindir)/jmacs $(DESTDIR)$(bindir)/jstar $(DESTDIR)$(bindir)/rjoe $(DESTDIR)$(bindir)/jpico rm -f $(DESTDIR)$(bindir)/jmacs.exe $(DESTDIR)$(bindir)/jstar.exe $(DESTDIR)$(bindir)/rjoe.exe $(DESTDIR)$(bindir)/jpico.exe for i in jmacs jstar rjoe jpico ; do $(LN_S) joe $(DESTDIR)$(bindir)/$$i ; done uninstall-local: rm -f $(DESTDIR)$(bindir)/jmacs $(DESTDIR)$(bindir)/jstar $(DESTDIR)$(bindir)/rjoe $(DESTDIR)$(bindir)/jpico rm -f $(DESTDIR)$(bindir)/jmacs.exe $(DESTDIR)$(bindir)/jstar.exe $(DESTDIR)$(bindir)/rjoe.exe $(DESTDIR)$(bindir)/jpico.exe joe-4.4/man/0000775000175000017500000000000013041211214007701 500000000000000joe-4.4/man/Makefile.am0000664000175000017500000000056013016320753011671 00000000000000sysconf_joedir = $(sysconfdir)/joe data_joedir = $(datadir)/joe data_docdir = $(docdir) SUBDIRS = ru man_MANS = joe.1 EXTRA_DIST = joe.1.in joe.1 : joe.1.in LC_ALL=C sed 's,@JOERC\@,$(sysconf_joedir),; s,@JOEDOC\@,$(data_docdir),; s,@JOEDATA\@,$(data_joedir),; s,@SPELL\@,@SPELL@,; s,@BINDIR\@,$(bindir),' $(srcdir)/joe.1.in > $@ MOSTLYCLEANFILES = $(man_MANS) joe-4.4/man/joe.1.in0000664000175000017500000037357313016320753011122 00000000000000.\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . .TH "JOE" "" "March 2016" "" "" . .SH "NAME" \fBJOE\fR \- Joe\'s Own Editor . .SH "Syntax" \fBjoe [global\-options] [ [local\-options] filename ]\.\.\.\fR . .br \fBjstar [global\-options] [ [local\-options] filename ]\.\.\.\fR . .br \fBjmacs [global\-options] [ [local\-options] filename ]\.\.\.\fR . .br \fBrjoe [global\-options] [ [local\-options] filename ]\.\.\.\fR . .br \fBjpico [global\-options] [ [local\-options] filename ]\.\.\.\fR . .SH "Description" JOE is a powerful console screen editor\. It has a "mode\-less" user interface which is similar to many user\-friendly PC editors\. Users of Micro\-Pro\'s WordStar or Borland\'s "Turbo" languages will feel at home\. JOE is a full featured UNIX screen\-editor though, and has many features for editing programs and text\. . .P JOE also emulates several other editors\. JSTAR is a close imitation of WordStar with many "JOE" extensions\. JPICO is a close imitation of the Pine mailing system\'s PICO editor, but with many extensions and improvements\. JMACS is a GNU\-EMACS imitation\. RJOE is a restricted version of JOE, which allows you to edit only the files specified on the command line\. . .P Although JOE is actually five different editors, it still requires only one executable, but one with five different names\. The name of the editor with an "rc" appended gives the name of JOE\'s initialization file, which determines the personality of the editor\. . .P JOE is free software; you can distribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation\. JOE is available over the Internet from \fIhttp://www\.sourceforge\.net/projects/joe\-editor\fR\. . .SH "Usage" To start the editor, type \fBjoe\fR followed by zero or more names of files you want to edit\. Each file name may be preceded by a local option setting (see the local options table which follows)\. Other global options, which apply to the editor as a whole, may also be placed on the command line (see the global options table which follows)\. If you are editing a new file, you can either give the name of the new file when you invoke the editor, or in the editor when you save the new file\. A modified syntax for file names is provided to allow you to edit program output, standard input/output, or sections of files or devices\. See the section \fIFilenames\fR below for details\. . .P Once you are in the editor, you can type in text and use special control\-character sequences to perform other editing tasks\. To find out what the control\-character sequences are, read the rest of this man page or type \fB^K H\fR for help in the editor\. . .P Now for some obscure computer\-lore: . .P The \fB^\fR means that you hold down the \fBControl\fR key while pressing the following key (the same way the \fBShift\fR key works for uppercase letters)\. A number of control\-key sequences are duplicated on other keys, so that you don\'t need to press the control key: \fBEsc\fR will work in place of \fB^[\fR, \fBDel\fR will work in place of \fB^?\fR, \fBBackspace\fR will work in place of \fB^H\fR, \fBTab\fR will work in place of \fB^I\fR, \fBReturn\fR or \fBEnter\fR will work in place of \fB^M\fR and \fBLinefeed\fR will work in place of \fB^J\fR\. Some keyboards may give you trouble with some control keys\. \fB^\fR_, \fB^^\fR and \fB^@\fR can usually be entered without pressing shift (i\.e\., try \fB^\-\fR, \fB^6\fR and \fB^2\fR)\. Other keyboards may reassign these to other keys\. Try: \fB^\.\fR, \fB^,\fR and \fB^/\fR\. \fB^Space\fR can usually be used in place of \fB^@\fR\. \fB^\e\fR and \fB^]\fR are interpreted by many communication programs, including telnet and kermit\. Usually you just hit the key twice to get it to pass through the communication program\. . .P On some keyboards, holding the \fBAlt\fR key down while pressing another key is the same as typing \fBEsc\fR before typing the other key\. . .P Once you have typed \fB^K H\fR, the first help window appears at the top of the screen\. You can continue to enter and edit text while the help window is on\. To page through other topics, hit \fBEsc ,\fR and \fBEsc \.\fR (that is, \fBEsc ,\fR and \fBEsc \.\fR)\. Use \fB^K H\fR to dismiss the help window\. . .P You can customize the keyboard layout, the help screens and a number of behavior defaults by copying JOE\'s initialization file (usually \fB/etc/joe/joerc\fR) to \fB\.joerc\fR in your home directory and then by modifying it\. See the section \fIjoerc\fR below\. . .P To have JOE used as your default editor for e\-mail and News, you need to set the \fBEDITOR\fR and \fBVISUAL\fR environment variables in your shell initialization file (\fB\.cshrc\fR or \fB\.profile\fR) to refer to JOE (JOE usually resides as \fB/usr/bin/joe\fR)\. . .P There are a number of other obscure invocation parameters which may have to be set, particularly if your terminal screen is not updating as you think it should\. See the section \fIEnvironment variables\fR below\. . .P \fI\fR . .SH "Command Line Options" These options can also be specified in the joerc file\. Local options can be set depending on the file\-name extension\. Programs (\.c, \.h or \.p extension) usually have autoindent enabled\. Wordwrap is enabled on other files, but rc files have it disabled\. . .P An option is enabled when it\'s given like this: . .IP "" 4 . .nf \-wordwrap . .fi . .IP "" 0 . .P An option is disabled when it\'s given like this: . .IP "" 4 . .nf \-\-wordwrap . .fi . .IP "" 0 . .P Some options take arguments\. Arguments are given like this: . .IP "" 4 . .nf \-lmargin 5 . .fi . .IP "" 0 . .P The following global options may be specified on the command line: . .IP "\(bu" 4 asis . .br Characters with codes above 127 will be sent to the terminal as\-is, instead of as inverse of the corresponding character below 128\. If this does not work, check your terminal server\. This option has no effect if UTF\-8 encoding is used\. . .br . .IP "\(bu" 4 assume_256color . .br Assume ANSI\-like terminal emulator supports 256 colors even if termcap entry says it doesn\'t\. . .br . .IP "\(bu" 4 assume_color . .br Assume ANSI\-like terminal emulator supports color even if termcap entry says it doesn\'t\. . .br . .IP "\(bu" 4 text_color \fBcolor\fR . .br Set color for text\. . .br . .IP "\(bu" 4 status_color \fBcolor\fR . .br Set color for status bar\. . .br . .IP "\(bu" 4 help_color \fBcolor\fR . .br Set color for help\. . .br . .IP "\(bu" 4 menu_color \fBcolor\fR . .br Set color for menus\. . .br . .IP "\(bu" 4 prompt_color \fBcolor\fR . .br Set color for prompts\. . .br . .IP "\(bu" 4 msg_color \fBcolor\fR . .br Set color for messages\. . .br . .IP "\(bu" 4 autoswap . .br Automatically swap \fB^K B\fR with \fB^K K\fR if necessary to mark a legal block during block copy/move commands\. . .br . .IP "\(bu" 4 backpath path . .br Sets path to a directory where all backup files are to be stored\. If this is unset (the default) backup files are stored in the directory containing the file\. . .br . .IP "\(bu" 4 baud nnn . .br Set the baud rate for the purposes of terminal screen optimization (overrides value reported by stty)\. JOE inserts delays for baud rates below 19200, which bypasses tty buffering so that typeahead will interrupt the screen output\. Scrolling commands will not be used for 38400 baud and above\. This is useful for X\-terms and other console ttys which really aren\'t going over a serial line\. . .br . .IP "\(bu" 4 beep . .br Enable beeps when edit commands return errors, for example when the cursor goes past extremes\. . .br . .IP "\(bu" 4 break_links . .br When enabled, JOE first deletes the file before writing it in order to break hard\-links and symbolic\-links\. . .br . .IP "\(bu" 4 break_hardlinks . .br When enabled, and the file is not a symbolic links, JOE first deletes the file before writing it in order to break hard\-links\. . .br . .IP "\(bu" 4 brpaste . .br When JOE starts, send command to the terminal emulator that enables "bracketed paste mode" (but only if the terminal seems to have the ANSI command set)\. In this mode, text pasted into the window is bracketed with ESC [ 2 0 0 ~ and ESC [ 2 0 1 ~\. . .br . .IP "\(bu" 4 columns nnn . .br Set number of columns in terminal emulator (in case termcap entry is wrong)\. This is only useful on old system which don\'t have the "get window size" ioctl\. . .br . .IP "\(bu" 4 csmode . .br Enable continued search mode: Successive \fB^K F\fRs repeat the current search instead of prompting for a new one\. . .br . .IP "\(bu" 4 dopadding . .br Enable JOE to send padding NULs to the terminal (for very old terminals)\. . .br . .IP "\(bu" 4 exask . .br When set, \fB^K X\fR prompts for a new name before saving the file\. . .br . .IP "\(bu" 4 floatmouse . .br When set, mouse clicks can position the cursor beyond the ends of lines\. . .br . .IP "\(bu" 4 guess_crlf . .br When set, JOE tries to guess the file format MS\-DOS or UNIX\. . .br . .IP "\(bu" 4 guess_indent . .br When set, JOE tries to guess the indentation character and indentation step based on the contents of the file\. The algorithm is to find the greatest common factor of the three most common indentations found in the file\. . .br . .IP "\(bu" 4 guess_non_utf8 . .br When set, enable guessing of non\-UTF\-8 files in UTF\-8 locales\. . .br . .IP "\(bu" 4 guess_utf8 . .br When set, enable guessing of UTF\-8 files in non\-UTF\-8 locales\. . .br . .IP "\(bu" 4 guess_utf16 . .br When set, enable guessing of UTF\-16 files\. If a UTF\-16BE or UTF\-16LE file is detected, it is converted to UTF\-8 during load, and converted back to UTF\-16 during save\. . .br . .IP "\(bu" 4 helpon . .br When set, start off with the on\-line help enabled\. . .br . .IP "\(bu" 4 help_is_utf8 . .br When set, the help text in the joerc file is assumed to be UTF\-8\. . .br . .IP "\(bu" 4 icase . .br Search is case insensitive by default when set\. . .br . .IP "\(bu" 4 joe_state . .br Enable reading and writing of ~/\.joe_state file . .br . .IP "\(bu" 4 joexterm . .br Set this if xterm was configured with \-\-paste64 option for better mouse support\. . .br . .IP "\(bu" 4 keepup . .br The column number on the status line is updated constantly when this is set, otherwise it is updated only once a second\. . .br . .IP "\(bu" 4 language \fBlanguage\fR . .br Sets language for aspell\. . .br . .IP "\(bu" 4 lightoff . .br Automatically turn off \fB^K B\fR \fB^K K\fR highlighting after a block operation\. . .br . .IP "\(bu" 4 lines nnn . .br Set number of lines in terminal emulator (in case termcap entry is wrong)\. This is only useful on old system which don\'t have the "get window size" ioctl\. . .br . .IP "\(bu" 4 marking . .br Enable marking mode: highlights between \fB^K B\fR and cursor\. . .br . .IP "\(bu" 4 menu_above . .br Put menus above prompt instead of below them\. . .br . .IP "\(bu" 4 menu_explorer . .br Stay in menu when a directory is selected (otherwise the directory is added to the path and the cursor jumps back to the prompt)\. . .br . .IP "\(bu" 4 menu_jump . .br Jump into the file selection menu when \fBTab\fR \fBTab\fR is hit\. . .br . .IP "\(bu" 4 mid . .br If this option is set and the cursor moves off the window, the window will be scrolled so that the cursor is in the center\. This option is forced on slow terminals which don\'t have scrolling commands\. . .br . .IP "\(bu" 4 left nn . .br This sets the number of columns the screen scrolls to the left when cursor moves past the left edge or when the crawll command is issued\. If nn is negative, then it\'s the fraction of the screen to scroll\. For example, \-2 means scroll 1/2 the screen\. . .br . .IP "\(bu" 4 right nn . .br This sets the number of columns the screen scrolls to the right when cursor moves past the right edge or when the crawlr command is issued\. If nn is negative, then it\'s the fraction of the screen to scroll\. For example, \-3 means scroll 1/3 the screen\. . .br . .IP "\(bu" 4 mouse . .br Enable xterm mouse support\. . .br . .IP "\(bu" 4 nobackups . .br Disable backup files\. . .br . .IP "\(bu" 4 nocurdir . .br Disable current\-directory prefix in prompts\. . .br . .IP "\(bu" 4 noexmsg . .br Disable exiting message ("File not changed so no update needed") . .br . .IP "\(bu" 4 nolinefeeds . .br Disable sending linefeeds to preserve screen history in terminal emulator\'s scroll\-back buffer (only relevant when notite mode is enabled)\. . .br . .br . .IP "\(bu" 4 nolocks . .br Disable EMACS compatible file locks\. . .br . .IP "\(bu" 4 nomodcheck . .br Disable periodic file modification check\. . .br . .IP "\(bu" 4 nonotice . .br This option prevents the copyright notice from being displayed when the editor starts\. . .br . .IP "\(bu" 4 nosta . .br This option eliminates the top\-most status line\. It\'s nice for when you only want to see your text on the screen or if you\'re using a vt52\. . .br . .IP "\(bu" 4 notagsmenu . .br Disable selection menu for tags search with multiple results\. . .br . .IP "\(bu" 4 notite . .br Disable ti and te termcap sequences which are usually set up to save and restore the terminal screen contents when JOE starts and exits\. . .br . .IP "\(bu" 4 pastehack . .br If keyboard input comes in as one block assume it\'s a mouse paste and disable autoindent and wordwrap\. . .br . .IP "\(bu" 4 noxon . .br Disable \fB^S\fR and \fB^Q\fR flow control, possibly allowing \fB^S\fR and \fB^Q\fR to be used as editor keys\. . .br . .IP "\(bu" 4 orphan . .br Orphan extra files given on the command line instead of creating windows for them (the files are loaded, but you need to use switch\-buffer commands to access them)\. . .br . .IP "\(bu" 4 pg nnn . .br Set number of lines to keep during Page Up and Page Down (use \-1 for 1/2 window size)\. . .br . .IP "\(bu" 4 regex . .br Use standard regular expression syntax by default, instead of the JOE syntax (where special characters have their meaning only when preceded with backslash)\. . .br . .IP "\(bu" 4 restore . .br Set to have cursor positions restored to last positions of previously edited files\. . .br . .IP "\(bu" 4 rtbutton . .br Swap left and right mouse buttons\. . .br . .IP "\(bu" 4 search_prompting . .br Show previous search string in search command (like in PICO)\. . .br . .IP "\(bu" 4 skiptop nnn . .br When set to N, the first N lines of the terminal screen are not used by JOE and are instead left with their original contents\. This is useful for programs which call JOE to leave a message for the user\. . .br . .IP "\(bu" 4 square . .br Enable rectangular block mode\. . .br . .IP "\(bu" 4 transpose . .br Transpose rows with columns in all menus\. . .br .IP "\(bu" 4 title . .br Display context (titles) in status line. When enabled this shows the first line of the function that the cursor is in on the status line\. The syntax file context.jsf identifies which lines are title lines\. . .br . .IP "\(bu" 4 type . .br Select file type, overriding the automatically determined type\. The file types are defined in the \fBftyperc\fR file\. . .br . .IP "\(bu" 4 undo_keep nnn . .br Sets number of undo records to keep (0 means infinite)\. . .br . .IP "\(bu" 4 usetabs . .br Set to allow rectangular block operations to use tabs\. . .br . .IP "\(bu" 4 wrap . .br Enable search to wrap to beginning of file\. . .br . .IP "" 0 . .P The following local options may be specified on the command line: . .IP "\(bu" 4 +nnn . .br The cursor starts on the specified line\. . .br . .IP "\(bu" 4 autoindent . .br Enable auto\-indent mode\. When you hit \fBEnter\fR on an indented line, the indentation is duplicated onto the new line\. . .br . .IP "\(bu" 4 c_comment . .br Enable \fB^G\fR skipping of C\-style comments /\fI\.\.\.\fR/ . .br . .IP "\(bu" 4 cpara \fBcharacters\fR . .br Sets list of characters which can indent paragraphs\. . .br . .IP "\(bu" 4 cnotpara \fBcharacters\fR . .br Sets list of characters which begin lines which are definitely not part of paragraphs\. . .br . .IP "\(bu" 4 cpp_comment . .br Enable \fB^G\fR skipping of C++\-style comments // \.\.\. . .br . .IP "\(bu" 4 crlf . .br JOE uses CR\-LF as the end of line sequence instead of just LF\. This is for editing MS\-DOS or VMS files\. . .br . .IP "\(bu" 4 encoding \fBencoding\fR . .br Set file encoding (like utf\-8 or 8859\-1)\. . .br . .IP "\(bu" 4 flowed . .br Set to force an extra space after each line of a paragraph but the last\. . .br . .IP "\(bu" 4 force . .br When set, a final newline is appended to the file if there isn\'t one when the file is saved\. . .br . .IP "\(bu" 4 french . .br When set, only one space is inserted after periods in paragraph reformats instead of two\. . .br . .IP "\(bu" 4 hex . .br Enable hex\-dump mode\. . .br . .IP "\(bu" 4 highlight . .br Enable syntax highlighting\. . .br . .IP "\(bu" 4 highlighter_context . .br Enable use of syntax file to identify comments and strings which should be skipped over during \fB^G\fR matching\. . .br . .IP "\(bu" 4 indentc nnn . .br Sets the indentation character for shift left and shift right (\fB^K ,\fR and \fB^K \.\fR)\. Use 32 for \fBSpace\fR, 9 for \fBTab\fR\. . .br . .IP "\(bu" 4 indentfirst . .br When set, the smart home key jumps to the indentation point first, otherwise it jumps to column 1 first\. . .br . .IP "\(bu" 4 istep nnn . .br Sets indentation step\. . .br . .IP "\(bu" 4 linums . .br Enable line number display\. . .br . .IP "\(bu" 4 lmargin . .br Set left margin\. . .br . .IP "\(bu" 4 lmsg . .br Define left\-side status bar message\. . .br . .IP "\(bu" 4 overwrite . .br Enable overtype mode\. Typing overwrites existing characters instead of inserting before them\. . .br . .IP "\(bu" 4 picture . .br Enable "picture" mode\- allows cursor to go past ends of lines\. . .br . .IP "\(bu" 4 pound_comment . .br \fB^G\fR ignores # \.\.\. comments\. . .br . .IP "\(bu" 4 purify . .br Fix indentation if necessary before shifting or smart backspace\. For example, if indentation uses a mix of tabs and spaces, and indentc is space, then indentation will be converted to all spaces before the shifting operation\. . .br . .IP "\(bu" 4 rdonly . .br Set read\-only mode\. . .br . .IP "\(bu" 4 rmargin nnn . .br Set right margin\. . .br . .IP "\(bu" 4 rmsg \fBstring\fR . .br Define right\-side status bar message\. . .br . .IP "\(bu" 4 semi_comment . .br \fB^G\fR ignores ; \.\.\. comments\. . .br . .IP "\(bu" 4 single_quoted . .br \fB^G\fR ignores \'\.\.\.\' . .br . .IP "\(bu" 4 smartbacks . .br Enable smart backspace and tab\. When this mode is set backspace and tab indent or unindent based on the values of the istep and indentc options\. . .br . .IP "\(bu" 4 smarthome . .br Home key first moves cursor to beginning of line, then if hit again, to the first non\-blank character\. . .br . .IP "\(bu" 4 smsg \fBstring\fR . .br Define status command format when cursor is on a character\. . .br . .IP "\(bu" 4 spaces . .br Insert spaces when \fBTab\fR key is hit\. . .br . .IP "\(bu" 4 syntax \fBsyntax\fR . .br Set syntax for syntax highlighting\. . .br . .IP "\(bu" 4 tab nnn . .br Set tab stop width\. . .br . .IP "\(bu" 4 text_delimiters \fBword delimiter list\fR . .br Give list of word delimiters which \fB^G\fR will step through\. . .IP "" 0 . .P For example, "begin=end:if=elif=else=endif" means that \fB^G\fR will jump between the matching if, elif, else and endif\. . .IP "\(bu" 4 vhdl_comment . .br \fB^G\fR ignores \-\- \.\.\. comments . .br . .IP "\(bu" 4 wordwrap . .br JOE wraps the previous word when you type past the right margin\. . .br . .IP "\(bu" 4 zmsg \fBstring\fR . .br Define status command format when cursor is at end of file\. . .br . .IP "\(bu" 4 xmsg \fBstring\fR . .br Define startup message (usually the copyright notice)\. . .br . .IP "\(bu" 4 aborthint \fBstring\fR . .br Give the key sequence to show in prompts for abort (usually ^C)\. . .br . .IP "\(bu" 4 helphint \fBstring\fR . .br Give the key sequence to show in prompts for help (usually ^K H)\. . .br . .IP "" 0 . .SS "Colors and attributes" Combine attributes and up to one foreground color and one background color to create arguments for color options like text_color\. For example: bold+bg_green+blue . .IP "\(bu" 4 Attributes: bold, inverse, blink, dim, underline, and italic . .IP "\(bu" 4 Foreground colors: white, cyan, magenta, blue, yellow, green, red, or black . .IP "\(bu" 4 Background colors: bg_white, bg_cyan, bg_magenta, bg_blue, bg_yellow, bg_green, bg_red or bg_black . .IP "" 0 . .P With a 16 color or 256 color terminal emulator (export TERM=xterm\-16color), these brighter than normal colors become available: . .IP "\(bu" 4 Foreground: WHITE, CYAN, MAGENTA, BLUE, YELLOW, GREEN, RED or BLACK . .IP "\(bu" 4 Background: bg_WHITE, bg_CYAN, bg_MAGENTA, bg_BLUE, bg_YELLOW, bg_GREEN, bg_RED or bg_BLACK . .IP "" 0 . .P With a 256 color terminal emulator (export TERM=xterm\-256color), these become available: . .IP "\(bu" 4 fg_RGB and bg_RGB, where R, G and B rand from 0 \- 5\. So: fg_500 is bright red\. . .IP "\(bu" 4 fg_NN and bg_NN give shades of grey, where the intensity, NN, ranges from 0 \- 23\. . .IP "" 0 . .SS "Status line definition strings" \-lmsg defines the left\-justified string and \-rmsg defines the right\-justified string\. The first character of \-rmsg is the background fill character\. . .P \-smsg defines the status command (\fB^K Space\fR)\. \-zmsg defines it when the cursor is at the end of the file\. The last character of smsg or zmsg is the fill character\. . .P The following escape sequences can be used in these strings: . .IP "" 4 . .nf %t 12 hour time %u 24 hour time %T O for overtype mode, I for insert mode %W W if wordwrap is enabled %I A if autoindent is enabled %X Rectangle mode indicator %n File name %m \'(Modified)\' if file has been changed %* \'*\' if file has been changed %R Read\-only indicator %r Row (line) number %c Column number %o Byte offset into file %O Byte offset into file in hex %a Ascii value of character under cursor %A Ascii value of character under cursor in hex %w Width of character under cursor %p Percent of file cursor is at %l No\. lines in file %k Entered prefix keys %S \'*SHELL*\' if there is a shell running in window %M Macro recording message %y Syntax %e Encoding %x Context (first non\-indented line going backwards) %dd day %dm month %dY year %Ename% value of environment variable %Tname% value of option (ON or OFF for Boolean options) . .fi . .IP "" 0 . .P These formatting escape sequences may also be given: . .IP "" 4 . .nf \ei Inverse \eu Underline \eb Bold \ed Dim \ef Blink \el Italic . .fi . .IP "" 0 . .P . .br . .SH "Basic Editing" When you type characters into the editor, they are normally inserted into the file being edited (or appended to the file if the cursor is at the end of the file)\. This is the normal operating mode of the editor\. If you want to replace some existing text, you have to delete the old text before or after you type in the replacement text\. The \fBBackspace\fR key can be used for deleting text: move the cursor to right after the text you want to delete and hit \fBBackspace\fR a number of times\. . .P Hit the \fBEnter\fR or \fBReturn\fR key to insert a line\-break\. For example, if the cursor was in the middle of a line and you hit \fBEnter\fR, the line would be split into two lines with the cursor appearing at the beginning of the second line\. Hit \fBBackspace\fR at the beginning of a line to eliminate a line\-break\. . .P Use the arrow keys to move around the file\. If your keyboard doesn\'t have arrow keys (or if they don\'t work for some reason), use \fB^F\fR to move forwards (right), \fB^B\fR to move backwards (left), \fB^P\fR to move to the previous line (up), and \fB^N\fR to move to the next line (down)\. The right and left arrow keys simply move forwards or backwards one character at a time through the text: if you\'re at the beginning of a line and you press left\-arrow, you will end up at the end of the previous line\. The up and down arrow keys move forwards and backwards by enough characters so that the cursor appears in the same column that it was in on the original line\. . .P If you want to indent the text you enter, you can use the \fBTab\fR key\. This inserts a special control character which makes the characters which follow it begin at the next tab stop\. Tab stops normally occur every 8 columns, but this can be changed with the \fB^T D\fR command\. PASCAL and C programmers often set tab stops on every 4 columns\. . .P If for some reason your terminal screen gets messed up (for example, if you receive a mail notice from biff), you can have the editor refresh the screen by hitting \fB^R\fR\. . .P There are many other keys for deleting text and moving around the file\. For example, hit \fB^D\fR to delete the character the cursor is on instead of deleting backwards like \fBBackspace\fR\. \fB^D\fR will also delete a line\-break if the cursor is at the end of a line\. Type \fB^Y\fR to delete the entire line the cursor is on or \fB^J\fR to delete just from the cursor to the end of the line\. . .P Hit \fB^A\fR to move the cursor to the beginning of the line it\'s on\. Hit \fB^E\fR to move the cursor to the end of the line\. Hit \fB^U\fR or \fB^V\fR for scrolling the cursor up or down 1/2 a screen\'s worth\. . .br "Scrolling" means that the text on the screen moves, but the cursor stays at the same place relative to the screen\. Hit \fB^K U\fR or \fB^K V\fR to move the cursor to the beginning or the end of the file\. Look at the help screens in the editor to find even more delete and movement commands\. . .P If you make a mistake, you can hit \fB^_\fR to "undo" it\. On most keyboards you hit just \fB^\-\fR to get \fB^_\fR, but on some you might have to hold both the \fBShift\fR and \fBControl\fR keys down at the same time to get it\. If you "undo" too much, you can "redo" the changes back into existence by hitting \fB^^\fR (type this with just \fB^6\fR on most keyboards)\. . .SS "Cursor position history" If you were editing in one place within the file, and you then temporarily had to look or edit some other place within the file, you can get back to the original place by hitting \fB^K \-\fR\. This command actually returns you to the last place you made a change in the file\. You can step through a history of places with \fB^K \-\fR and \fB^K =\fR, in the same way you can step through the history of changes with the "undo" and "redo" commands\. . .SS "Save and exit" When you are done editing the file, hit \fB^K X\fR to exit the editor\. You will be prompted for a file name if you hadn\'t already named the file you were editing\. . .P When you edit a file, you actually edit only a copy of the file\. So if you decide that you don\'t want the changes you made to a file during a particular edit session, you can hit \fB^C\fR to exit the editor without saving them\. . .P If you edit a file and save the changes, a backup copy of that file is created in the current directory, with a \fB~\fR appended to the name, which contains the original version of the file\. . .SS "File operations" You can hit \fB^K D\fR to save the current file (possibly under a different name from what the file was called originally)\. After the file is saved, you can hit \fB^K E\fR to edit a different file\. . .P If you want to save only a selected section of the file, see the section on \fIBlocks\fR below\. . .P If you want to include another file in the file you\'re editing, use \fB^K R\fR to insert it\. . .P \fI\fR . .SS "Filenames" Wherever JOE expects you to enter a file name, whether on the command line or in prompts within the editor, you may also type: . .IP "\(bu" 4 !command . .IP "" 0 . .P To read or write data to or from a shell command\. For example, use \fBjoe \'!ls\'\fR to get a copy of your directory listing to edit or from within the editor use \fB^K D !mail jhallen@world\.std\.com\fR to send the file being edited to me\. . .IP "\(bu" 4 >>filename . .IP "" 0 . .P Use this to have JOE append the edited text to the end of the file "filename\." . .IP "\(bu" 4 filename,START,SIZE . .IP "" 0 . .P Use this to access a fixed section of a file or device\. \fBSTART\fR and \fBSIZE\fR may be entered in decimal (ex\.: 123) octal (ex\.: 0777) or hexadecimal (ex\.: 0xFF)\. For example, use \fBjoe /dev/fd0,508,2\fR to edit bytes 508 and 509 of the first floppy drive in Linux\. . .IP "\(bu" 4 \- . .IP "" 0 . .P Use this to get input from the standard input or to write output to the standard output\. For example, you can put JOE in a pipe of commands: \fBquota \-v | joe | mail root\fR, if you want to complain about your low quota\. . .SS "Using JOE in a shell script" JOE used to use /dev/tty to access the terminal\. This caused a problem with idle\-session killers (they would kill JOE because the real tty device was not being accessed for a long time), so now JOE only uses /dev/tty if you need to pipe a file into JOE, as in: . .IP "" 4 . .nf echo "hi" | joe . .fi . .IP "" 0 . .P If you want to use JOE in a shell script which has its stdin/stdout redirected, but you do not need to pipe to it, you should simply redirect JOE\'s stdin/stdout to /dev/tty: . .IP "" 4 . .nf joe filename /dev/tty . .fi . .IP "" 0 . .P . .br . .br . .SS "Word wrap and formatting" If you type past the right edge of the screen in a C or PASCAL language file, the screen will scroll to the right to follow the cursor\. If you type past the right edge of the screen in a normal file (one whose name doesn\'t end in \.c, \.h or \.p), JOE will automatically wrap the last word onto the next line so that you don\'t have to hit \fBEnter\fR\. This is called word\-wrap mode\. Word\-wrap can be turned on or off with the \fB^T W\fR command\. JOE\'s initialization file is usually set up so that this mode is automatically turned on for all non\-program files\. See the section below on the \fIjoerc\fR file to change this and other defaults\. . .P Aside for Word\-wrap mode, JOE does not automatically keep paragraphs formatted like some word\-processors\. Instead, if you need a paragraph to be reformatted, hit \fB^K J\fR\. This command "fills in" the paragraph that the cursor is in, fitting as many words in a line as is possible\. A paragraph, in this case, is a block of text separated above and below by a blank line\. . .P The margins which JOE uses for paragraph formatting and word\-wrap can be set with the \fB^T L\fR and \fB^T R\fR commands\. If the left margin is set to a value other than 1, then when you start typing at the beginning of a line, the cursor will immediately jump to the left margin\. . .P There are a number of options which control the paragraph reformatter and word wrapper: . .IP "\(bu" 4 The \fBcpara\fR option provides a list of characters which can indent a paragraph\. For example, in e\-mail quoted matter is indicated by \fB>\fR at the beginnings of line, so this character should be in the cpara list\. . .IP "\(bu" 4 The \fBcnotpara\fR option provides a list of characters which, if they are the first non\-whitespace character of a line, indicate that the line is not to be included as part of a paragraph for formatting\. For example, lines beginning with \'\.\' in nroff can not be paragraph lines\. . .IP "\(bu" 4 Autoindent mode affects the formatter\. If autoindent is disabled, only the first line will be indented\. If autoindent is enabled, the entire paragraph is indented\. . .IP "\(bu" 4 \fBfrench\fR determines how many spaces are inserted after periods\. . .IP "\(bu" 4 When \fBflowed\fR is enabled, a space is inserted after each but the last line of the paragraph\. This indicates that the lines belong together as a single paragraph in some programs\. . .IP "\(bu" 4 When \fBovertype\fR is enabled, the word wrapper will not insert lines\. . .IP "" 0 . .SS "Centering" If you want to center a line within the margins, use the \fB^K A\fR command\. . .SS "Spell checker" Hit \fBEsc N\fR to check the spelling of the word the cursor is on using the aspell program (or ispell program if you modify the joerc file)\. Hit \fBEsc L\fR to check the highlighted block or the entire file if no block is highlighted\. . .P JOE passes the language and character encoding to the spell checker\. To change the language, hit \fB^T V\fR\. For example, use en_US for English\. . .SS "Overtype mode" Sometimes it\'s tiresome to have to delete old text before or after you insert new text\. This happens, for example, when you are changing a table and you want to maintain the column position of the right side of the table\. . .br When this occurs, you can put the editor in overtype mode with \fB^T T\fR\. . .br When the editor is in this mode, the characters you type in replace existing characters, in the way an idealized typewriter would\. Also, \fBBackspace\fR simply moves left instead of deleting the character to the left, when it\'s not at the end or beginning of a line\. Overtype mode is not the natural way of dealing with text electronically, so you should go back to insert\-mode as soon as possible by typing \fB^T T\fR again\. . .P If you need to insert while you\'re in overtype mode, hit \fB^@\fR\. This inserts a single \fBSpace\fR into the text\. . .SS "Control and Meta characters" Each character is represented by a number\. For example, the number for \'A\' is 65 and the number for \'1\' is 49\. All of the characters which you normally see have numbers in the range of 32 \- 126 (this particular arbitrary assignment between characters and numbers is called the ASCII character set)\. The numbers outside of this range, from 0 to 255, aren\'t usually displayed, but sometimes have other special meanings\. The number 10, for example, is used for the line\-breaks\. You can enter these special, non\-displayed \fBcontrol characters\fR by first hitting \fB^Q\fR and then hitting a character in the range \fB@ A B C \.\.\. X Y Z [ ^ ] \e _\fR to get the number 0 \- 31, and ? to get 127\. For example, if you hit \fB^Q J\fR, you\'ll insert a line\-break character, or if you hit \fB^Q I\fR, you\'ll insert a \fBTab\fR character (which does the same thing the \fBTab\fR key does)\. A useful control character to enter is 12 (\fB^Q L\fR), which causes most printers to advance to the top of the page\. You\'ll notice that JOE displays this character as an underlined L\. You can enter the characters above 127, the \fBmeta characters\fR, by first hitting \fB^\e\fR\. This adds 128 to the next (possibly control) character entered\. JOE displays characters above 128 in inverse\-video\. Some foreign languages, which have more letters than English, use the meta characters for the rest of their alphabet\. You have to put the editor in \fBasis\fR mode to have these passed untranslated to the terminal\. . .P \fBNote:\fR JOE now normally passes all 8\-bits to the terminal unless the locale is set to C or POSIX\. If the locale is C or POSIX, then the \fBasis\fR flag determines if \fBmeta characters\fR are shown in inverse video or passed directly to the terminal\. . .P \fBNote:\fR In older version of JOE, you had to use \fBEsc \'\fR to enter control characters\. . .SH "Character sets and UTF\-8" JOE natively handles two classes of character sets: UTF\-8 and byte coded (like ISO\-8859\-1)\. For these character sets, the file is loaded as\-is into memory, and is exactly preserved during save, even if it contains UTF\-8 coding errors\. . .P It can not yet natively 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\. . .P 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\. . .P JOE now supports UTF\-16 (both big endian and little endian)\. It supports UTF\-16 by converting to UTF\-8 during load, and converting back to UTF\-16 during save\. . .P 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 work\. . .P 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)\. . .P For example, if LC_ALL is set to: . .IP "" 4 . .nf de_DE . .fi . .IP "" 0 . .P Then the character set will be ISO\-8859\-1\. . .P If LC_ALL is set to: . .IP "" 4 . .nf de_DE\.UTF\-8 . .fi . .IP "" 0 . .P The character set will be UTF\-8\. . .P Hit \fB^T E\fR to change the coding for the file\. Hit \fBTab\fR \fBTab\fR 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 ~/\.joe/charmaps and /usr/share/joe/charmaps directories\. . .P 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 files 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/share/joe/charmaps\. . .P You can hit \fB^K Space\fR to see the current character set\. . .P You can hit \fB^Q x\fR to enter a Unicode character if the file coding is UTF\-8\. . .SH "Prompts" Most prompts record a history of the responses you give them\. You can hit up and down arrow to step through these histories\. . .P Prompts are actually single line windows with no status line, so you can use any editing command that you normally use on text within the prompts\. The prompt history is actually just other lines of the same "prompt file"\. Thus you can can search backwards though the prompt history with the normal \fB^K F\fR command if you want\. . .P Since prompts are windows, you can also switch out of them with \fB^K P\fR and \fB^K N\fR\. . .SS "Completion and selection menus" You can hit \fBTab\fR in just about any prompt to request JOE to complete the word you are typing\. If JOE beeps, there are either no completions or many\. As with the "bash" shell, hit \fBTab\fR twice to bring up a list of all the possibilities\. This list is actually a menu, but by default, the cursor does not jump into it since it is usually easier to just type in your selection\. You can, however, jump into the menu window with \fB^K P\fR (move to previous window) and use the arrow keys and to make your selection\. Also in a menu, you can hit the first letter of any of the items to make the cursor jump directly to it\. The \fB^T\fR option menu works like this\. . .P If the menu is too large to fit in the window, you can hit Page Up and Page Down to scroll it (even if you have not jumped into it)\. . .P \fBTab\fR completion works in the search and replace prompts as well\. In this case, JOE tries to complete the word based on the contents of the buffer\. If you need search for the \fBTab\fR character itself, you can enter it with \fB^Q Tab\fR\. . .P Also, you can hit \fBEsc Enter\fR in a text window to request JOE to complete the word you are typing\. As with the search prompt, JOE tries to complete the word based on the contents of the buffer\. It will bring up a menu of possibilities if you hit \fBEsc Enter\fR twice\. . .SH "Where am I?" Hit \fB^K Space\fR to have JOE report the line number, column number, and byte number on the last line of the screen\. The number associated with the character the cursor is on (its ASCII code) is also shown\. You can have the line number and/or column number always displayed on the status line by placing the appropriate escape sequences in the status line setup strings\. Edit the joerc file for details\. . .SH "What if I hit ^K by accident?" Hit the space bar\. This runs an innocuous command (it shows the line number on the status bar)\. . .SH "Temporarily suspending the editor" If you need to temporarily stop the editor and go back to the shell, hit \fB^K Z\fR\. You might want to do this to stop whatever you\'re editing and answer an e\-mail message or read this man page, for example\. You have to type \fBfg\fR or \fBexit\fR (you\'ll be told which when you hit \fB^K Z\fR) to return to the editor\. . .SH "Searching for text" Hit \fB^K F\fR to have the editor search forwards or backwards for a text fragment (\fBstring\fR) for you\. You will be prompted for the text to search for\. After you hit \fBEnter\fR, you are prompted to enter options\. . .br You can just hit \fBEnter\fR again to have the editor immediately search forwards for the text, or you can enter one or more of these options: . .IP "\(bu" 4 \fBb\fR . .br . .IP "" 0 . .P Search backwards instead of forwards\. . .IP "\(bu" 4 \fBi\fR . .br . .IP "" 0 . .P Treat uppercase and lower case letters as the same when searching\. Normally uppercase and lowercase letters are considered to be different\. . .IP "\(bu" 4 \fBnnn\fR . .br . .IP "" 0 . .P (where \fBnnn\fR is a number) If you enter a number, JOE searches for the Nth occurrence of the text\. This is useful for going to specific places in files structured in some regular manner\. . .IP "\(bu" 4 \fBr\fR . .br . .IP "" 0 . .P Replace text\. If you enter the \fBr\fR option, then you will be further prompted for replacement text\. Each time the editor finds the search text, you will be prompted as to whether you want to replace the found search text with the replacement text\. You hit: \fBy\fR to replace the text and then find the next occurrence, \fBn\fR to not replace this text, but to then find the next occurrence, \fBr\fR to replace all of the remaining occurrences of the search text in the remainder of the file without asking for confirmation (subject to the \fBnnn\fR option above), or \fB^C\fR to stop searching and replacing\. . .P You can also hit \fBB\fR or \fBBackspace\fR to back up to the previously found text (if it had been replaced, the replacement is undone)\. . .IP "\(bu" 4 \fBa\fR . .br . .IP "" 0 . .P The search covers all loaded buffers\. So to replace all instances of "foo" with "bar" in all \.c files in the current directory: . .IP "" 4 . .nf joe *\.c ^K F foo ra bar . .fi . .IP "" 0 . .IP "\(bu" 4 \fBe\fR . .br . .IP "" 0 . .P The search covers all files in the grep or make error list\. You can use a UNIX command to generate a list of files and search and replace through the list\. So to replace all instances of "foo" with "bar" in all \.c files which begin with f\. You can also use "ls" and "find" instead of grep to create the file list\. . .IP "" 4 . .nf Esc G grep \-n foo f*\.c ^K F foo re bar . .fi . .IP "" 0 . .IP "\(bu" 4 \fBx\fR . .br . .IP "" 0 . .P JOE will use the standard syntax for regular expressions if this option is given\. In the standard syntax, these characters have their special meanings directly, and do not have to be escaped with backslash: \., *, +, ?, {, }, (, ), |, ^, $ and [\. . .IP "\(bu" 4 \fBy\fR . .br . .IP "" 0 . .P JOE will use the JOE syntax for regular expressions instead of the standard syntax\. This overrides the "\-regex" option\. . .IP "\(bu" 4 \fBv\fR . .br . .IP "" 0 . .P JOE will send debug information about the regular expression to the startup log\. The log can be viewed with the showlog command\. . .P You can hit \fB^L\fR to repeat the previous search\. . .P You can hit \fB^K H\fR at the search and replace options prompt to bring up a list of all search and replace options\. . .SS "Regular Expressions" A number of special character sequences may be entered as search text: . .IP "\(bu" 4 \fB\e*\fR . .br . .IP "" 0 . .P This finds zero or more of the item to the left\. For example, if you give \fBAB\e*C\fR as the search text, JOE will try to find an A followed by any number of Bs, and then a C\. . .IP "\(bu" 4 \fB\e+\fR . .br . .IP "" 0 . .P This finds one or more of the item to the left\. For example, if you give \fBAB\e+C\fR as the search text, JOE will try to find an A followed by one or more Bs, and then a C\. . .IP "\(bu" 4 \fB\e?\fR . .br . .IP "" 0 . .P This indicates that the item to the left is optional\. For example, if you give \fBAB\e?C\fR as the search text, JOE will find AC or ABC\. . .IP "\(bu" 4 \fB\e{min,max}\fR . .br . .IP "" 0 . .P This indicates that JOE should try to find a string with a specific number of occurrences of the item to the left\. For example, \fBAX\e{2,5}B\fR will match these strings: AXXB, AXXXB, AXXXXB, and AXXXXXB\. Min can be left out to indicate 0 occurrences\. Max (and the comma) can be left out to indicate any number of occurrences\. . .IP "\(bu" 4 \fB\e\.\fR . .br . .IP "" 0 . .P This finds exactly one character\. For example, if you give \fBA\e\.B\fR as the search text, JOE will find AXB, but not AB or AXXB\. . .IP "\(bu" 4 \fB\e!\fR . .br . .IP "" 0 . .P This works like \fB\.\fR, but matches a balanced C\-language expression\. For example, if you search for \fBmalloc(\e!\e*)\fR, then JOE will find all function calls to \fBmalloc\fR, even if there was a \fB)\fR within the parenthesis\. . .IP "\(bu" 4 \fB\e|\fR . .br . .IP "" 0 . .P This finds the item on the left or the item on the right\. For example, if you give \fBA\e|B\fR as the search text, JOE will try to find either an A or a B\. . .IP "\(bu" 4 \fB\e( \e)\fR . .br . .IP "" 0 . .P Use these to group characters together\. For example, if you search for \fB\e(foo\e)\e+\fR, then JOE will find strings like "foo", and "foofoofoo"\. . .IP "\(bu" 4 \fB^ \e$\fR . .br . .IP "" 0 . .P These match the beginnings and endings of lines\. For example, if you give \fB^test\e$\fR, then JOE with find \fBtest\fR on a line by itself\. . .IP "\(bu" 4 \fB\e\fI\e\e\fR\fR . .br . .IP "" 0 . .P These match the beginnings and endings of words\. For example, if you give \fB\e\fIis\e\e\fR\fR, then JOE will find the word "is" but will not find the "is" in "this"\. . .IP "\(bu" 4 \fB\e[\.\.\.]\fR . .br . .IP "" 0 . .P This matches any single character which appears within the brackets\. For example, if \fB\e[Tt]his\fR is entered as the search string, then JOE finds both \fBThis\fR and \fBthis\fR\. Ranges of characters can be entered within the brackets\. For example, \fB\e[A\-Z]\fR finds any uppercase letter\. If the first character given in the brackets is \fB^\fR, then JOE tries to find any character not given in the the brackets\. To include \fB\-\fR itself, include it as the last or first character (possibly after \fB^\fR)\. . .IP "\(bu" 4 \fB\e\e\fR . .br . .IP "" 0 . .P Matches a single \e\. . .IP "\(bu" 4 \fB\en\fR . .br . .IP "" 0 . .P This finds the special end\-of\-line or line\-break character\. . .P A number of special character sequences may also be given in the replacement string: . .IP "\(bu" 4 \fB\e&\fR . .br . .IP "" 0 . .P This gets replaced by the text which matched the search string\. For example, if the search string was \fB\e\fI\e*\e\e\fR\fR, which matches words, and you give \fB"\e&"\fR, then JOE will put quote marks around words\. . .IP "\(bu" 4 \fB\e1 \- \e9\fR . .br . .IP "" 0 . .P These get replaced with the text which matched the Nth grouping; the text within the Nth set of \e( \e)\. . .IP "\(bu" 4 \fB\el, \eu\fR . .br . .IP "" 0 . .P Convert the next character of the replacement text to lowercase or uppercase\. . .IP "\(bu" 4 \fB\eL, \eU\fR . .br . .IP "" 0 . .P Convert all following replacement text to lowercase or uppercase\. Conversion stops when \eE is encountered\. . .IP "\(bu" 4 \fB\e\e\fR . .br . .IP "" 0 . .P Use this if you need to put a \fB\e\fR in the replacement string\. . .IP "\(bu" 4 \fB\en\fR . .br . .IP "" 0 . .P Use this if you need to put a line\-break in the replacement string\. . .P Some examples: . .P Suppose you have a list of addresses, each on a separate line, which starts with "Address:" and has each element separated by commas\. Like so: . .P Address: S\. Holmes, 221b Baker St\., London, England . .P If you wanted to rearrange the list, to get the country first, then the city, then the person\'s name, and then the address, you could do this: . .P Type \fB^K F\fR to start the search, and type: . .P \fBAddress:\e(\e\.\e*\e),\e(\e\.\e*\e),\e(\e\.\e*\e),\e(\e\.\e*\e)\e$\fR . .P to match "Address:", the four comma\-separated elements, and then the end of the line\. When asked for options, you would type \fBr\fR to replace the string, and then type: . .P \fBAddress:\e4,\e3,\e1,\e2\fR . .P To shuffle the information the way you want it\. After hitting return, the search would begin, and the sample line would be changed to: . .P Address: England, London, S\. Holmes, 221b Baker St\. . .P \fI\fR . .SS "Escape sequences" JOE understands the following escape sequences withing search and replacement strings: . .IP "\(bu" 4 \ex{10ffff} . .br . .IP "" 0 . .P This matches a specific Unicode code point given in hexadecimal\. . .IP "\(bu" 4 \exFF . .br . .IP "" 0 . .P This matches a specific character specified in hexadecimal\. . .IP "\(bu" 4 \e377 . .br . .IP "" 0 . .P This matches a specific character specified in octal\. . .IP "\(bu" 4 \ep{Ll} . .br . .IP "" 0 . .P This matches any character in the named Unicode category or block\. . .P The block names, such as "Latin\-1 Supplement" or "Arabic" can be found here: . .P Unicode Blocks \fIftp://ftp\.unicode\.org/Public/8\.0\.0/ucd/Blocks\.txt\fR . .P The category names such as "Ll" can be found here: . .P Unicode Categories \fIftp://ftp\.unicode\.org/Public/5\.1\.0/ucd/UCD\.html#General_Category_Values\fR . .P Note that a single letter matches all of the category names which start with that letter\. For example, \ep{N} (any number) include \ep{Nd} (decimal digit), \ep{Nl} (letter number) and \ep{No} (other number)\. . .IP "\(bu" 4 \ed . .br . .IP "" 0 . .P This matches any Unicode digit\. This is the same as \ep{Nd}\. . .IP "\(bu" 4 \eD . .br . .IP "" 0 . .P This matches anything except for a Unicode digit\. This is the same as \e[^\ep{Nd}]\. . .IP "\(bu" 4 \ew . .br . .IP "" 0 . .P This matches any word character\. This is the same as \e[^\ep{C}\ep{P}\ep{Z}]\. . .IP "\(bu" 4 \eW . .br . .IP "" 0 . .P This matches anything except for a word character\. This is the same as \e[\ep{C}\ep{P}\ep{Z}]\. . .IP "\(bu" 4 \es . .br . .IP "" 0 . .P This matches any space character\. This is the same as \e[\et\er\ef\en\ep{Z}]\. . .IP "\(bu" 4 \eS . .br . .IP "" 0 . .P This matches anything except for a spacing character\. This is the same as \e[^\et\er\ef\en\ep{Z}]\. . .IP "\(bu" 4 \ei . .br . .IP "" 0 . .P This matches an identifier start character\. This is the same as \e[\ep{L}\ep{Pc}\ep{Nl}]\. . .IP "\(bu" 4 \eI . .br . .IP "" 0 . .P This matches anything except for an identifier start character\. This is the same as \e[^\ep{L}\ep{Pc}\ep{Nl}]\. . .IP "\(bu" 4 \ec . .br . .IP "" 0 . .P This matches an identifier continuation character\. This is the same as \e[\ei\ep{Mn}\ep{Mc}\ep{Nd}\ex{200c}\ex{200d}]\. . .IP "\(bu" 4 \eC . .br . .IP "" 0 . .P This matches anything except for an identifier continuation character\. This is the same as \e[^\ei\ep{Mn}\ep{Mc}\ep{Nd}\ex{200c}\ex{200d}]\. . .IP "\(bu" 4 \et Tab . .IP "\(bu" 4 \en Newline . .IP "\(bu" 4 \er Carriage return . .IP "\(bu" 4 \eb Backspace . .IP "\(bu" 4 \ea Alert . .IP "\(bu" 4 \ef Formfeed . .IP "\(bu" 4 \ee Escape . .IP "\(bu" 4 \e\e Backslash . .IP "" 0 . .SH "Incremental search" Use \fBEsc S\fR to start an increment search forwards, or \fBEsc R\fR to start an incremental search backwards\. As you type the search string, the cursor will jump to the first text that matches the regular expression you have entered so far\. . .P Hit \fBEsc S\fR or \fBEsc R\fR again to find the next occurrence of the text or to switch the direction of the search\. . .P \fB^S\fR, \fB^\e\fR and \fB^L\fR have the same effect as \fBEsc S\fR\. \fB^R\fR has the same effect as \fBEsc R\fR\. These keys are to support JMACS\. . .P Hit \fBBackspace\fR to undo the last incremental search action\. The last action could be a repeat of a previous search or the entering of a new character\. . .P Use \fB^Q\fR to insert control characters into the search text\. Previously, ` could also be used for this\. . .P Hit any other key to exit the increment search\. . .SH "Goto matching delimiter" Hit \fB^G\fR to jump between matching delimiters\. This works on both character delimiters (like \'(\' and \')\') and word delimiters for languages like Pascal and Verilog which use "begin" and "end" to delimit blocks\. It also works for matching start and end tags in XML\. If a word is not known, \fB^G\fR starts a search with the word moved into the search prompt\. . .P For \fB^G\fR to work on word delimiters, the cursor must be positioned on the first letter of the word\. So in XML, if the cursor is on the < in , it will jump to the >\. But if it is one the \'f\', it will jump to the matching \. Likewise, in C, \fB^G\fR will jump between #if, #else and #endif, but you need to position the cursor on the letter, not the \'#\'\. . .P \fB^G\fR is smart enough to skip delimiters found in quoted or commented\-out matter\. You need to tell JOE how your language indicates this: see the \fBftyperc\fR file for examples of how this is done\. . .P The are a number of options which control the behavior of \fB^G\fR\. These options control which kinds of comments \fB^G\fR can skip over: . .IP "\(bu" 4 c_comment . .IP "\(bu" 4 cpp_comment . .IP "\(bu" 4 pount_comment . .IP "\(bu" 4 semi_comment . .IP "\(bu" 4 vhdl_comment . .IP "" 0 . .P These options determine which kinds of strings \fB^G\fR can skip over: . .IP "\(bu" 4 single_quoted . .IP "\(bu" 4 double_quoted . .IP "" 0 . .P This option allows an annotated syntax file to determine which text can be counted as comments or strings which can be skipped over by \fB^G\fR: . .IP "\(bu" 4 highlighter_context . .IP "" 0 . .P This option enables the use of syntax files to identify comments and strings which should be skipped over during \fB^G\fR matching\. The syntax file states should be annotated with the \fBstring\fR and \fBcomment\fR keywords for this to work\. . .IP "\(bu" 4 text_delimiters . .IP "" 0 . .P This option provides a list of word delimiters to match\. For example, "begin=end:if=elif=else=endif" means that \fB^G\fR will jump between the matching if, elif, else and endif\. It will also jump between begin and end\. . .P \fB^G\fR has a built\-in table for matching character delimiters\- it knows that \fB(\fR goes with \fB)\fR\. . .P \fB^G\fR has a built\-in parser to handle start/end tag matching for XML\. . .P \fI\fR . .SH "Regions" If you want to move, copy, save or delete a specific section of text, you can do it with highlighted blocks\. First, move the cursor to the start of the section of text you want to work on, and press \fB^K B\fR\. Then move the cursor to the character just after the end of the text you want to affect and press \fB^K K\fR\. The text between the \fB^K B\fR and \fB^K K\fR should become highlighted\. Now you can move your cursor to someplace else in your document and press \fB^K M\fR to move the highlighted text there\. . .br You can press \fB^K C\fR to make a copy of the highlighted text and insert it to where the cursor is positioned\. \fB^K Y\fR to deletes the highlighted text\. \fB^K W\fR, writes the highlighted text to a file\. . .P A very useful command is \fB^K /\fR, which filters a block of text through a UNIX command\. For example, if you select a list of words with \fB^K B\fR and \fB^K K\fR, and then type \fB^K / sort\fR, the list of words will be sorted\. Another useful UNIX command for \fB^K /\fR, is \fBtr\fR\. If you type \fB^K / tr a\-z A\-Z\fR, then all of the letters in the highlighted block will be converted to uppercase\. . .SS "How do I deselect a highlighted region?" After you are finished with some region operations, you can just leave the highlighting on if you don\'t mind it (but don\'t accidentally hit \fB^K Y\fR)\. If it really bothers you, however, just hit \fB^K B ^K K\fR, to turn the highlighting off\. . .P Beginning with JOE 4\.2, you can hit \fB^C\fR to cancel the region selection\. . .SS "New ways of selecting regions" The classic way is to hit \fB^K B\fR at the beginning and \fB^K K\fR at the end\. These set pointers called markb and markk\. Once these are set you can jump to markb with \fBEsc B\fR and jump to markk with \fBEsc K\fR\. . .P New way: hit Ctrl\-\fBRight Arrow\fR to start selecting rightward\. Each time you hit Ctrl\-\fBRight Arrow\fR, the block is extended one more to the right\. This uses a simple macro: "begin_marking,rtarw,toggle_marking"\. . .P Unfortunately, there is no standard way to get the keysequence given by the terminal emulator when you hit Ctrl\-\fBRight Arrow\fR\. 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 \fB^Q\fR Ctrl\-\fBRight Arrow\fR within JOE to have the sequence shown on your screen\. Note that Putty uses \fBEsc Esc [ C\fR which will not appear with \fB^Q Right Arrow\fR (also \fBEsc Esc\fR is the set bookmark command, so you need to unbind it to do this in Putty)\. . .P Also you can hit Ctrl\-\fBDelete\fR to cut and Ctrl\-\fBInsert\fR to paste if the sequence for these keys are known\. . .P The mouse can also be used to select text if mouse support is enabled in JOE\. . .SH "Indenting program blocks" Auto\-indent mode is toggled with the \fB^T I\fR command\. The \fBjoerc\fR file is normally set up so that files with names ending with \.p, \.c or \.h have auto\-indent mode enabled\. When auto\-indent mode is enabled and you hit \fBEnter\fR, the cursor will be placed in the same column that the first non\-whitespace character was on in the original line\. . .P You can use the \fB^K ,\fR and \fB^K \.\fR commands to shift a block of text to the left or right\. If no highlighting is set when you give these commands, the program block (as indicated by indentation) that the cursor is located in will be selected, and will be moved by subsequent \fB^K ,\fR and \fB^K \.\fR commands\. . .P The number of columns these commands shift by and the character used for shifting can be set through the istep and indentc options\. These options are available in the \fB^T\fR menu\. Also, \fB^T =\fR can be used to quickly select from a number of common values for indentation step and character\. . .P JOE has a number of additional options related to indenting programs: . .IP "\(bu" 4 smartbacks . .br Enable smart backspace and tab\. When this mode is set \fBBackspace\fR and \fBTab\fR indent or unindent based on the values of the istep and indentc options\. . .br . .IP "\(bu" 4 smarthome . .br The \fBHome\fR and \fB^A\fR keys first move the cursor to the beginning of the line, then if hit again, to the first non\-blank character\. . .br . .IP "\(bu" 4 indentfirst . .br Smart home goes to first non\-blank character first, instead of going to the beginning of the line first\. . .br . .IP "\(bu" 4 purify . .br Fix indentation if necessary before shifting or smart backspace\. For example, if indentation uses a mix of tabs and spaces, and indentc is space, then indentation will be converted to all spaces before the shifting operation\. . .br . .IP "\(bu" 4 guess_indent . .br When set, JOE tries to guess the indentation character and indentation step based on the contents of the file\. The algorithm is to find the greatest common factor of the three most common indentations found in the file\. . .br . .IP "" 0 . .SH "Rectangle mode" Type \fB^T X\fR to have \fB^K B\fR and \fB^K K\fR select rectangular blocks instead of stream\-of\-text blocks\. This is also known as columnar mode\. This mode is useful for moving, copying, deleting or saving columns of text\. You can also filter columns of text with the \fB^K /\fR command\- if you want to sort a column, for example\. The insert file command, \fB^K R\fR is also affected\. . .P When rectangle mode is selected, overtype mode is also useful (\fB^T T\fR)\. When overtype mode is selected, rectangles will replace existing text instead of getting inserted before it\. Also the delete block command (\fB^K Y\fR) will clear the selected rectangle with \fBSpaces\fR and \fBTabs\fR instead of deleting it\. Overtype mode is especially useful for the filter block command (\fB^K /\fR), since it will maintain the original width of the selected column\. . .SH "Picture mode" Use \fB^T P\fR to enter or exit picture mode\. Picture mode helps with ASCII drawings\. . .P Picture mode controls how JOE handles the case where the cursor is past the ends of lines\. This happens when you use the up or down arrow keys to move the cursor from the end of a long line to a short line\. . .P If you attempt to type a character in this case: . .P If picture mode is off, the cursor will jump to the end of the line and insert it there\. . .P If picture mode is on, the line is filled with spaces so that the character can be inserted at the cursor position\. . .SH "Windows" You can edit more than one file at the same time or edit two or more different places of the same file\. To do this, hit \fB^K O\fR, to split the screen into two windows\. Use \fB^K P\fR or \fB^K N\fR to move the cursor into the top window or the lower window\. Use \fB^K E\fR to edit a new file in one of the windows\. A window will go away when you save the file with \fB^K X\fR or abort the file with \fB^C\fR\. If you abort a file which exists in two windows, one of the window goes away, not the file\. . .P You can hit \fB^K O\fR within a window to create even more windows\. If you have too many windows on the screen, but you don\'t want to eliminate them, you can hit \fB^K I\fR\. This will show only the window the cursor is in, or if there was only one window on the screen to begin with, try to fit all hidden windows on the screen\. If there are more windows than can fit on the screen, you can hit \fB^K N\fR on the bottom\-most window or \fB^K P\fR on the top\-most window to get to them\. . .P If you gave more than one file name to JOE on the command line, each file will be placed in a different window\. . .P You can change the height of the windows with the \fB^K G\fR and \fB^K T\fR commands\. . .SS "Windowing system model" JOE has an unusual model for its windowing system\. Basically you have a ring of windows, but only a section of this ring may fit on the screen\. The windows not on the screen still exist, they are just scrolled off\. When you hit \fB^K N\fR on the bottom window of the screen, it scrolls further windows from the ring onto the screen, possibly letting the top window scroll out of view\. . .P Native JOE tries to keep each loaded buffer in a window, so users can find all of the buffers by scrolling through the windows\. The \fBexplode\fR command (\fB^K I\fR) either expands all windows to the size of the screen so that only one window can fit on the screen, or shrinks them all as much as possible to fit many on the screen\. . .P On the other hand, JOE supports "orphan" buffers\- files loaded into the editor, but which are not in a window\. \fB^C\fR normally closes a window and discards the buffer that was in it\. If you hit \fB^C\fR on the last remaining window, it will normally exit the editor\. However, if there are orphan buffers, \fB^C\fR will instead load them into this final window to give you a chance to explicitly discard them\. If the \fBorphan\fR option is given on the command line, as in \fBjoe \-orphan *\.c\fR, then JOE only loads the first file into a window and leaves all the rest as orphans\. . .P \fBorphan\fR also controls whether the edit command \fB^K E\fR creates a new window for a newly loaded file, or reuses the current window (orphaning its previous occupant)\. . .P The \fBbufed\fR command prompts for a name of a buffer to switch into a window\. Its completion list will show all buffers, including orphans and buffers which appear in other windows\. \fBEsc V\fR and \fBEsc U\fR (\fBnbuf\fR and \fBpbuf\fR commands) allow you to cycle through all buffers within a single window\. . .P Windows maintain a stack of occupants to support the pop\-up shell window feature\. When a pop\-up window is dismissed, the previous buffer is returned to the window\. . .SH "Scratch buffers" Scratch buffers are buffers which JOE does not worry about trying to preserve\. JOE will not ask to save modified scratch buffers\. Pop\-up shell windows, the startup log and compile and grep message windows are scratch buffers\. You can create your own scratch buffer with the \fBscratch\fR command\. . .P The following commands load scratch buffers: . .IP "\(bu" 4 \fBshowlog\fR Show startup log . .IP "\(bu" 4 \fBmwind\fR Show message window (compile / grep messages from \fBEsc C\fR and \fBEsc G\fR commands)\. . .IP "" 0 . .SH "Keyboard macros" Macros allow you to record a series of keystrokes and replay them with the press of two keys\. This is useful to automate repetitive tasks\. To start a macro recording, hit \fB^K [\fR followed by a number from 0 to 9\. The status line will display (Macro n recording\.\.\.)\. Now, type in the series of keystrokes that you want to be able to repeat\. The commands you type will have their usual effects\. Hit \fB^K ]\fR to stop recording the macro\. Hit \fB^K\fR followed by the number you recorded the macro in to execute one iteration of the key\-strokes\. . .P For example, if you want to put "**" in front of a number of lines, you can type: . .P \fB^K [ 0 ^A **\fR\fIdown arrow\e\fR \fB^K ]\fR . .P Which starts the macro recording, moves the cursor to the beginning of the line, inserts "**", moves the cursor down one line, and then ends the recording\. Since we included the key\-strokes needed to position the cursor on the next line, we can repeatedly use this macro without having to move the cursor ourselves, something you should always keep in mind when recording a macro\. . .SS "Keyboard macro subroutines" If you find that the macro you are recording itself has a repeated set of key\-strokes in it, you can record a macro within the macro, as long as you use a different macro number\. Also you can execute previously recorded macros from within new macros\. . .SS "Query suspend" If your macro includes a prompt for user input, and you want the user to fill in the prompt every time the macro is executed, hit \fB^K ?\fR at the point in the macro recording where the user action is required\. Keyboard input will not be recorded at this point\. When the user completes the prompt, macro recording will continue\. . .P When the macro is executed, the macro player will pause at the point where \fB^K ?\fR was entered to allow user input\. When the user completes the prompt, the player continues with the rest of the macro\. . .SS "Repeat" You can use the repeat command, \fB^K \e\fR, to repeat a macro, or any other edit command or even a normal character, a specified number of times\. Hit \fB^K \e\fR, type in the number of times you want the command repeated and press \fBEnter\fR\. The next edit command you now give will be repeated that many times\. For example, to delete the next 20 lines of text, type: . .P \fB^K \e 20\fR\fIreturn\fR\fB^Y\fR . .SH "Macros and commands" A macro is a comma separated list of commands\. When the macro is executed, each command is executed until either the end of the list is reached, or one of the commands fails (non\-zero return value from the command)\. Failed commands beep if you have beeps enabled (\fB^T B\fR)\. . .P Hit \fBEsc D\fR to insert the current set of keyboard macros as text into the current buffer\. For example, the "**" insert macro above looks like this: . .IP "" 4 . .nf home,"**",dnarw ^K 0 Macro 0 . .fi . .IP "" 0 . .P You could insert this into your \.joerc file and change the key sequence (the \fBK 0\fR) to something more permanent\. . .SS "Define your own" You can bind macros to key sequences or define your own named macros in the joerc file\. For example, this will define a macro called \fBfoo\fR: . .IP "" 4 . .nf :def foo eof,bol . .fi . .IP "" 0 . .P \fBfoo\fR will position the cursor at the beginning of the last line of the file\. \fBeof\fR jumps to the end of the file\. \fBbol\fR jumps to the beginning of a line\. Once a macro has been named this way it will show up in the completion list of the \fBEsc X\fR command prompt\. . .SS "Command prompt" You can execute a macro directly by typing it into the command prompt\. Hit \fBEsc X\fR to bring up the command prompt\. Hit \fBTab\fR at this prompt for a completion list of all available commands\. . .P Here is a \fIcomplete list of commands\fR\. . .SS "Macro don\'t stop modifier" Sometimes, you expect commands to sometimes fail, but want the rest of the commands in the list to be executed anyway\. To mark a command which is allowed to fail, postfix it with \'!\'\. For example, here a macro which hits down page in the window above: . .IP "" 4 . .nf prevw,pgdn!,nextw . .fi . .IP "" 0 . .P If prevw fails, the macro is aborted as usual\. Even if pgdn fails (already at end of buffer), nextw will be executed so that the cursor is returned to the original window\. . .SS "Macro repeat argument modifiers" Repeat arguments can be specified with \fB^K \e\fR\. When a command is executed with a repeat argument, it is repeatedly executed the specified number of times\. If the repeat argument is negative, an opposite command (if one exists) is executed instead\. For example, if you repeat "rtarw" \-3 times, "ltarw" will be repeated 3 times\. If a negative argument is given for a command which does not have an opposite, the repeat argument is ignored\. . .P Normally, if a repeat argument is specified for a macro, the macro is simply repeated the given number of times\. If a negative argument is given, the argument is ignored\. . .P Sometimes you want to allow negative arguments for macros and have their behavior modified\. To do this, postfix each command within the macro which should be switched to its opposite for negative arguments with \'\-\'\. For example, here is the page down other window macro: . .IP "" 4 . .nf prevw,pgdn\-!,nextw . .fi . .IP "" 0 . .P Now if you execute this with an argument of \-2, it will be repeated twice, but pgup will be executed instead of pgdn\. (note that several postfix modifiers can be placed after each command)\. . .P Sometimes when a repeat argument is given to macro, you want only one of the commands in the list to be repeated, not the entire macro\. This can be indicated as follows: . .IP "" 4 . .nf prevw,pgdn#!,nextw . .fi . .IP "" 0 . .P If this is executed with an argument of 2, prevw is executed once, pgdn is executed twice, and nextw is executed once\. . .P Finally, even more complex semantics can be expressed with the "if" command: . .IP "" 4 . .nf if~,"arg<0",then, ltarw, else, rtarw, endif . .fi . .IP "" 0 . .P When the macro is executed, the "arg" math variable is set to the given repeat argument\. The "argset" variable is set to true if the user set an argument, even if it\'s 1\. If no argument was given, argset is false\. . .P If any command in the list is postfixed with ~ (if above), the macro is not repeated, even if there is an argument\. \'arg\' is still set to the given repeat count, however\. . .SS "\'psh\'/\'query\' interaction" The \'psh\' command saves the \fB^K B\fR and \fB^K K\fR positions on a stack\. When the macro completes, (or when the \'pop\' command is called) the positions are restored\. . .P The \'query\' command suspends macro execution until the current dialog is complete\. It also suspends the automatic \'pop\' which happens at the end of a macro\- so if the macro ends in a dialog you often want to call \'query\' to prevent the \fB^K B\fR \fB^K K\fR positions from being restored too early\. . .SH "Tags search" If you are editing a large C program with many source files, you can use the \fBctags\fR program to generate a \fBtags\fR file\. This file contains a list of program symbols and the files and positions where the symbols are defined\. . .P First, create the tags file with the "ctags" program\. For example: . .IP "" 4 . .nf ctags *\.c *\.h . .fi . .IP "" 0 . .P This will create a file called "tags" in the current directory\. . .P JOE looks for the "tags" file in the current directory\. If there is none, it will try to open the file specified by the TAGS environment variable\. . .P Paths in the tags file are always relative to location of the tags file itself\. . .P The tags file contains a list of identifier definition locations in one of these formats: . .IP "" 4 . .nf identifier filename /search\-expression/[;comments] identifier filename ?search\-expression?[;comments] identifier filename line\-number[;comments] . .fi . .IP "" 0 . .P Some versions of ctags include class\-names in the identifiers: . .IP "" 4 . .nf class::member . .fi . .IP "" 0 . .P In this case, JOE will match on any of these strings: . .IP "" 4 . .nf member ::member class::member . .fi . .IP "" 0 . .P Some versions of ctags include a filename in the identifier: . .IP "" 4 . .nf filename:identifier . .fi . .IP "" 0 . .P In this case JOE will only find the identifier if the buffer name matches the filename\. . .P The search\-expression is a vi regular expression, but JOE only supports the following special characters: . .IP "" 4 . .nf ^ at the beginning means expression starts at beginning of line $ at the end means expression ends at end of line \ex quote x (suppress meaning of /, ?, ^ or $) . .fi . .IP "" 0 . .P Type \fB^K ;\fR to bring up a tags search prompt\. If the cursor had been on an identifier, the prompt is pre\-loaded with it\. Tab completion works in this prompt (it uses the tags file to find completions)\. . .P When you hit \fBEnter\fR, the tags search commences: . .P If there is one and only one match, JOE will jump directly to the definition\. . .P If there are multiple matches, then the behavior is controlled by the notagsmenu option\. If notagsmenu is enabled JOE jumps to the first definition\. If you hit \fB^K ;\fR again before hitting any other keys, JOE jumps to the next definition, and so on\. The "tagjump" command also performs this function\. . .P If notagsmenu is disabled, JOE brings up a menu of all the matches\. You select the one you want and JOE jumps to it\. If you hit \fB^K ;\fR again before hitting any other keys, the same menu re\-appears with the cursor left in the original location\. . .P You can hit \fB^K \-\fR to move the cursor back to the original location before the tags search (often \fB^C\fR will work as well)\. . .P Since \fB^K ;\fR loads the definition file into the current window, you probably want to split the window first with \fB^K O\fR, to have both the original file and the definition file loaded\. . .SH "Calculator" JOE has a built\-in calculator which can be invoked with \fBEsc M\fR\. . .SS "Math functions" sin, cos, tan, exp, sqrt, cbrt, ln, log, asin, acos, atan, sinh, cosh, tanh, asinh, acosh, atanh, int, floor, ceil, abs, erf, erfc, j0, j1, y0, y1 . .SS "Variables" . .IP "\(bu" 4 e . .br Set to \'e\' . .br . .IP "\(bu" 4 pi . .br Set to \'pi\' . .br . .IP "\(bu" 4 top . .br Set to line number of top window line . .br . .IP "\(bu" 4 lines . .br Set to number of lines in file . .br . .IP "\(bu" 4 line . .br Set to current line number . .br . .IP "\(bu" 4 col . .br Set to current column number . .br . .IP "\(bu" 4 byte . .br Set to current byte number . .br . .IP "\(bu" 4 size . .br Set to buffer size . .br . .IP "\(bu" 4 height . .br Set to window height . .br . .IP "\(bu" 4 width . .br Set to window width . .br . .IP "\(bu" 4 char . .br Set to ASCII val of character under cursor . .br . .IP "\(bu" 4 markv . .br True if there is a valid block set (^KB \.\.\. ^KK) . .br . .IP "\(bu" 4 rdonly . .br True if file is read\-only . .br . .IP "\(bu" 4 arg . .br Current repeat argument . .br . .IP "\(bu" 4 argset . .br True if a repeat argument was given . .br . .IP "\(bu" 4 is_shell . .br True if executed in an active shell window . .br . .IP "\(bu" 4 no_windows . .br No\. buffer windows on the screen . .br . .IP "\(bu" 4 ans . .br Result of previous expression . .br . .IP "" 0 . .SS "Commands" . .IP "\(bu" 4 hex . .br Hex display mode . .br . .IP "\(bu" 4 dec . .br Decimal display mode . .br . .IP "\(bu" 4 ins . .br Insert \'ans\' into buffer . .br . .IP "\(bu" 4 sum . .br Sum of numbers in block . .br . .IP "\(bu" 4 cnt . .br Count numbers in block . .br . .IP "\(bu" 4 avg . .br Average value of numbers in block . .br . .IP "\(bu" 4 dev . .br Standard deviation of numbers in block . .br . .IP "\(bu" 4 eval . .br Evaluate math expressions in block (or whole file if no block set)\. . .br . .IP "\(bu" 4 joe(\.\.\.) . .br Execute a JOE macro (argument in same format as joerc file macros)\. Return value of JOE macro is returned (for macro success, return true (non\-zero))\. . .br . .IP "" 0 . .P For example: . .IP "" 4 . .nf joe(sys,"[ 1 == 1 ]",rtn) . .fi . .IP "" 0 . .P ([ 1 == 1 ]) is a shell command\. "[" is a synonym for the "test" UNIX command\. . .P Returns true\. . .P Remember: argument for JOE macro command "if" is a math expression\. So for example, the macro: . .IP "" 4 . .nf if,"joe(sys,\e"[ 1 == 1 ]\e",rtn)",then,"TRUE",endif . .fi . .IP "" 0 . .P Types TRUE into the buffer\. . .SS "Operators:" . .IP "\(bu" 4 !x . .br Logical not of x\. . .br . .IP "\(bu" 4 x . .br Raise x to power of y\. . .br . .IP "\(bu" 4 a*b . .br Multiply\. . .br . .IP "\(bu" 4 a/b . .br Divide\. . .br . .IP "\(bu" 4 a%b . .br Modulus\. . .br . .IP "\(bu" 4 a+b . .br Add\. . .br . .IP "\(bu" 4 a\-b . .br Subtract\. . .br . .IP "\(bu" 4 ab . .br True if a is greater than b\. . .br . .IP "\(bu" 4 a>=b . .br True if a is greater than or equal to b\. . .br . .IP "\(bu" 4 a==b . .br True if a equals b\. . .br . .IP "\(bu" 4 a!=b . .br True if a does not equal b\. . .br . .IP "\(bu" 4 a&&b . .br True if both a and b are true\. . .br . .IP "\(bu" 4 a||b . .br True if ether a or b are true\. . .br . .IP "\(bu" 4 a?b:c . .br If a is true return b, otherwise return c\. . .br . .IP "\(bu" 4 a=b . .br Assign b to a\. . .br . .IP "\(bu" 4 a:b . .br Execute a, then execute b\. . .br . .IP "" 0 . .TP &&, || and ? : work as in C and sh as far as side effects: if the . .TP left side of && is false, the right side is not evaluated\. is expression separator\. . .SH "Shell windows" Hit \fB^K \'\fR to run a command shell in one of JOE\'s windows\. When the cursor is at the end of a shell window (use \fB^K V\fR if it\'s not), whatever you type is passed to the shell instead of the buffer\. Any output from the shell or from commands executed in the shell is appended to the shell window (the cursor will follow this output if it\'s at the end of the shell window)\. This command is useful for recording the results of shell commands\- for example the output of \fBmake\fR, the result of \fBgrep\fRping a set of files for a string, or directory listings from \fBFTP\fR sessions\. Besides typeable characters, the keys \fB^C\fR, \fBBackspace\fR, \fBDel\fR, \fBReturn\fR and \fB^D\fR are passed to the shell\. Type the shell \fBexit\fR command to stop recording shell output\. If you press \fB^C\fR in a shell window, when the cursor is not at the end of the window, the shell is \fBkill\fRed\. . .P If you use Bash, you can hit: \fB^Q Up Arrow\fR and \fB^Q Down Arrow\fR to scroll through Bash\'s history buffer\. Other keys work as well: try \fB^Q ^A\fR to go to beginning of line or \fB^Q ^E\fR to go to end of line\. Unfortunately JOE only emulates a dumb terminal, so you have to use a lot of imagination to do any editing beyond hitting backspace\. . .P In general, any character quoted with \fB^Q\fR is sent to the shell\. . .P Also sent to the shell: \fBTab\fR, \fBBackspace\fR, \fBEnter\fR, \fB^C\fR and \fB^D\fR\. . .P \fI\fR . .SH "Pop\-up shell windows" Hit F1 \- F4 to open and switch between shell windows\. . .P Pop\-up shell windows use a full terminal emulator so that when you type "man ls" it\'s formatted correctly (it works well enough so that some interactive programs can be used)\. Even so, the shell window is still an edit buffer\. . .P The old shell window (with no terminal emulation) still exists: use \fB^K \'\fR to invoke it as usual\. This is useful to see control sequences emitted by a program\. . .P More of the keys get passed to the running program in pop\-up shell windows compared with the older one\. There is a :vtshell section of the joerc file to control which ones\. In particular arrow keys and Ctrl\-C are passed to the program\. It means you can easily step through bash history with the arrow keys, or abort programs the normal way with Ctrl\-C\. . .P On the other hand, loss of Ctrl\-C means it\'s less obvious how to close the window\. One way is to move the cursor off of the shell data entry point (with Ctrl\-P), and then hit Ctrl\-C\. Another is to hit \fB^K Q\fR\. Finally, you can type \'pop\' at the command prompt\. . .P If you need to pass a key to the shell that JOE normally uses, quote it\. For example, if you invoke "emacs \-nw" in the shell window, you can exit it with: . .IP "" 4 . .nf ^Q ^X ^C . .fi . .IP "" 0 . .P To quickly position the cursor back to the point where data is entered into the shell, hit \fB^K V\fR\. . .P When you open a shell window, a JOE\-specific startup\-script is sourced\. It\'s located in /etc/joe/shell\.sh (also /etc/joe/shell\.csh)\. It contains some aliases which allow you to control JOE with fake shell commands\. I have these commands so far: . .IP "\(bu" 4 clear . .br erase shell window (delete buffer contents) . .br . .IP "\(bu" 4 joe file . .br edit a file in JOE . .br . .IP "\(bu" 4 math 1+2 . .br evaluate equation using JOE\'s calculator . .br . .IP "\(bu" 4 cd xyz . .br change directory, keep JOE up to date . .br . .IP "\(bu" 4 markb . .br same as ^KB . .br . .IP "\(bu" 4 markk . .br same as ^KK . .br . .IP "\(bu" 4 mark command . .br execute shell command, mark it\'s output . .br . .IP "\(bu" 4 parse command . .br execute shell command, parse it\'s output for file names and line numbers (for find or grep) . .br . .IP "\(bu" 4 parser comman . .br execute shell command, parse it\'s output for errors (for gcc) . .br . .IP "\(bu" 4 release . .br release parsed errors . .br . .IP "\(bu" 4 pop . .br dismiss shell window (same as ^K Q) . .br . .IP "" 0 . .P These work by emitting an escape sequence recognized by the terminal emulator: \fBEsc { joe_macro }\fR\. When this is received, the macro is executed\. For security, only macros defined in the joerc file which begin with "shell_" can be executed this way\. . .SS "Use cases" Pop\-up shell windows have a number of nice use cases: . .IP "\(bu" 4 Use it to browse manual pages . .IP Hit F1 and type "man fopen"\. Use \'b\' (\'u\') and space to control \fImore\fR (or \fIless\fR) while viewing the manual\. You can leave the manual on the screen in one window while editing in another window\. . .IP "\(bu" 4 Use it to switch directories . .IP Hit F1 and navigate to the directory while using \fIcd\fR\. Once you are in the right place, hit \fB^K E\fR to load a file (or type "edit file" from the shell)\. . .IP "\(bu" 4 Use it in conjunction with the error parser to find files . .IP Hit F1 and navigate to a directory\. Use grep or find (or both) to generate a list of files): . .IP "" 0 . .IP "" 4 . .nf parse grep \-n FIXME *\.c . .fi . .IP "" 0 . .P Or: . .IP "" 4 . .nf markb; find \. | xargs grep \-n FIXME; markk; parse . .fi . .IP "" 0 . .P (Note that you can\'t say this: . .IP "" 4 . .nf parse find \. | xargs grep \-n FIXME . .fi . .IP "" 0 . .P \&\.\.\.the issue is that only the words to the left of the pipe symbol are passed as arguments to the parse command)\. . .P Now use \fB^P\fR to position the cursor on one of the lines of the list\. Hit \fBEsc Space\fR to have JOE edit the file and jump to the specified line (also you can use \fBEsc \-\fR and \fBEsc =\fR to step through the list)\. . .IP "\(bu" 4 Use it in conjunction with search and replace to edit many files . .IP Once JOE has a list of files (from above), use search and replace with the \'e\' option to visit all of them: . .IP "" 0 . .IP "" 4 . .nf ^K F Find: Options: re Replace: . .fi . .IP "" 0 . .IP "\(bu" 4 Build your project . .IP "" 0 . .P Easily capture errors from a build with: . .IP "" 4 . .nf parserr make . .fi . .IP "" 0 . .P Hit \fBEsc =\fR and \fBEsc \-\fR to step through the errors\. . .SS "How it works\.\." . .IP "\(bu" 4 There is a new mode "ansi"\. (\fBEsc X\fR mode ansi)\. When this mode is enabled, the screen updater hides escape sequences which are in the buffer\. Otherwise you get a big mess from the sequences surrounding colored output from \'ls\'\. . .IP "\(bu" 4 There is a new built\-in syntax: "ansi"\. (\fB^T Y\fR ansi)\. This syntax parses the ANSI color control sequences so that text gets colored\. . .IP "\(bu" 4 There is a terminal emulator to interpret control sequences from the shell program\. It emulates a terminal by modifying the contents of an edit buffer\. . .IP "\(bu" 4 When the edit window is resized we tell the shell by issuing the TIOCSSIZE or TIOCSWINSZ ioctl\. This way, the program running in the shell knows the window size\. . .IP "" 0 . .SH "Compiler and grep/find parsers" JOE has two parsers which can be used to generate the error list (list of file names / line numbers)\. . .P The "parserr" command parses the entire buffer, or if the block is set, just the highighted block for compiler error messages\. The messages should be in this format: . .IP "" 4 . .nf file\.name line\-number : . .fi . .IP "" 0 . .P The file name needs to be made of numbers, letters, \'/\', \'\.\' and \'\-\'\. It must have at leat one \'\.\' in it\. There needs to be a colon somewhere after the line number\. Lines not in this format are ignored\. . .P The "gparse\' command parses the entire buffer, or if the block is set, just the highlighted block for a list of filenames or filenames with line numbers from "grep \-n", "find" and similar programs\. . .IP "" 4 . .nf filename filename: filename:line\-number: . .fi . .IP "" 0 . .P Once JOE has the error list, there are a number of things you can do with it: . .IP "\(bu" 4 Visit the files/locations in the list with \fBEsc \-\fR and \fBEsc =\fR . .IP "\(bu" 4 Search and replace across all files in the list by using the \'e\' search and replace option\. . .IP "\(bu" 4 Clear the list by using the "release" command\. . .IP "" 0 . .P Also, you can use \fBEsc Space\fR (\'jump\' command) to parse the line the cursor is on and jump to the parsed filename and line number\. \'jump\' uses the grep/find parser unless \'parserr\' had been previously issued in the buffer\. . .SS "Grep\-find" Hit \fBEsc G\fR to bring up the prompt\. Enter a command which results in file names with line numbers, for example: \'grep \-n fred *\.c\'\. This will list all instances of \'fred\' in the *\.c files\. You need the \'\-n\' to get the line numbers\. . .P Now you can hit \fBEsc Space\fR on one of the lines to jump to the selected file\. Also, you can use \fBEsc =\fR and \fBEsc \-\fR to step through each line\. . .SS "Compile" Hit \fBEsc C\fR to save all modified files and then bring up the compile prompt\. Enter the command you want to use for the compiler (typically "make \-w")\. The compiler will run in a shell window\. When it\'s complete, the results are parsed\. . .P The \'\-w\' flag should be given to "make" so that it prints messages whenever it changes directories\. The message are in this format: . .IP "" 4 . .nf make[1]: Entering directory `/home/jhallen/joe\-editor\-mercurial/joe\' . .fi . .IP "" 0 . .P If there are any errors or warnings from the compiler you can hit \fBEsc Space\fR on one of the lines to jump to the selected file\. Also, you can use \fBEsc =\fR and \fBEsc \-\fR to step through each line\. . .SH "Syntax highlighting" To enable highlight use \fB^T H\fR\. . .P To select the syntax, use \fB^T Y\fR\. You can hit \fBTab\fR \fBTab\fR at the prompt for a completion list\. . .P JOE tries to determine the syntax to use based on the name and contents of the file\. The configuration file /etc/joe/ftyperc contains the definitions\. . .P Each syntax is defined by a file located /usr/share/joe/syntax/\. . .SH "How JOE syntax highlighting works" \fIfrom c\.jsf \fIhttp://joe\-editor\.hg\.sourceforge\.net/hgweb/joe\-editor/joe\-editor/file/tip/syntax/c\.jsf\.in\fR, slightly modified\fR . .P A deterministic state machine that performs lexical analysis of the target language is provided in a syntax file\. (This is the "assembly language" of syntax highlighting\. A separate program could in principal be used to convert a regular expression NFA syntax into this format)\. . .P Each state begins with: . .IP "" 4 . .nf : . .fi . .IP "" 0 . .P \fIname\e\fR is the state\'s name\. . .P \fIcolor\-name\e\fR is the color used for characters eaten by the state (really a symbol for a user definable color)\. . .P \fIcontext\e\fR tells JOE if the current character is part of a comment or a string\. This allows JOE to skip over comments and strings when matching characters such as parentheses\. To use this feature, the highlighter_context option must be applied to the files highlighted by the corresponding syntax\. To apply the option, add it to ftyperc for those file entries\. . .P The valid contexts are: . .IP "\(bu" 4 comment This character is part of a comment\. Example: /* comment */ . .IP "\(bu" 4 string This character is part of a string\. Examples: "string" \'c\' \'string\' . .IP "" 0 . .P The comment and string delimiters themselves should be marked with the appropriate context\. The context is considered to be part of the color, so the recolor=\-N and recolormark options apply the context to previous characters\. . .P The first state defined is the initial state\. . .P Within a state, define transitions (jumps) to other states\. Each jump has the form: . .IP "" 4 . .nf [