Go to file
Erik Osheim 954c383a29 fixed token names in mode.dir
--HG--
branch : pmacs2
2009-06-11 00:00:33 -04:00
buffer start of the color overhaul 2009-06-10 16:07:03 -04:00
code_examples trying to make colors more sane and get 256 colors working 2009-06-10 12:05:24 -04:00
method fixed get-token bug 2009-06-11 00:00:25 -04:00
mode fixed token names in mode.dir 2009-06-11 00:00:33 -04:00
tools --HG-- 2008-11-12 20:48:37 +00:00
.hgignore created abstract base class vc-diff; refactored svn-diff 2009-05-10 01:45:57 -04:00
BUGS more bug reporting 2009-06-10 00:07:50 -04:00
IDEAS --HG-- 2009-05-05 04:20:04 +00:00
MODES updated documentation 2009-05-17 23:52:14 -04:00
README updated documentation 2009-05-17 23:52:14 -04:00
aesutil.py fix when pycrypto not installed 2009-05-21 14:49:12 -04:00
application.py start of the color overhaul 2009-06-10 16:07:03 -04:00
bufferlist.py --HG-- 2009-03-26 01:28:38 +00:00
cache.py try this again 2007-03-06 15:05:38 +00:00
color.py closer color matching 2009-06-10 23:41:53 -04:00
completer.py fixed some completion bugs 2009-03-06 14:21:52 +00:00
context.py fix bug i think 2009-03-22 04:01:45 +00:00
default.py better filename completion 2008-12-10 05:54:53 +00:00
dirutil.py --HG-- 2009-03-30 00:50:27 +00:00
gdb.py --HG-- 2008-03-28 22:16:59 +00:00
highlight.py --HG-- 2008-09-12 14:43:15 +00:00
ispell.py bugs about wrapping 2008-11-10 19:58:12 +00:00
keyinput.py fixed 8-bit bug with M-DELETE 2009-06-07 18:57:07 -04:00
lex.py some more fixes 2009-04-06 06:20:43 +00:00
minibuffer.py v2.6 clean-up 2008-03-16 20:26:32 +00:00
miniparse.py search is better, other stuff is worse 2007-07-05 20:18:09 +00:00
parse.py java fixes and parsing 2009-02-03 14:56:22 +00:00
point.py point2->point and buffer2->buffer 2007-10-22 00:50:11 +00:00
regex.py emacs/vi mode autodetection 2009-04-23 15:47:54 +00:00
render.py initial unicode support 2009-06-09 23:37:43 -04:00
searchutil.py started moving to newer-style exception (finally) 2008-05-16 23:02:22 +00:00
tab.py tab bug fix... base format fix, awk improvements 2009-04-06 15:21:43 +00:00
term.py --HG-- 2009-03-16 18:22:23 +00:00
util.py dir-grep improved; ignore_suffix improved 2009-06-09 02:12:07 -04:00
window.py some code clean-up and comment fixes 2009-05-10 02:01:33 -04:00

README

Pmacs

by Erik Osheim <erik@osheim.org>

Pmacs is an Emacs-like editor written entirely in Python. It is designed to
have maximally correct and powerful support for syntax highlighting, to support
various methods of automatically indenting lines, and to be extensible in
python.

Pmacs is available to you under the GNU GPL version 2.

While the general interface of Pmacs is related to Emacs, there was explicitly
no attempt to support all Emacs' functions, Emacs' underlying data structures,
or even all high-level functionality of Emacs. There is not currently a
formalized "public API" for pmacs, although some parts are "more public" than
others. The code is somewhat commented, although currently there is only one
author. Buyer beware!

Requirements:
    1. python 2.4 or higher (this may become 2.5 or higher)
    2. ncurses
    3. bash

Optional Dependencies:
    * aespipe   [for aes-encrypted buffers]
    * ispell    [for spell-checking]
    * cvs       [for cvs-based commands]
    * svn       [for svn-based commands]
    * mercurial [for hg-based commands]

    * perl     [for perl syntax-checking]
    * gcc      [for c compilation/syntax-checking]
    * make     [for c compilation]
    * latex    [for LaTeX compilation]
    * pdflatex [for LaTeX PDF rendering]
    * disinst  [for x86 instruction parsing]

Quick Start Guide:
    1. Download and unpack the pmacs tarball file. After this, there should be
        a directory called "pmacs2" somewhere in your filesystem. It doesn't
        matter where you put this. We'll call the full path to this directory
        PMACSDIR; in future steps substitute the actual path for this symbol.

    2. Create a symlink to PMACSDIR/application.py and put it in a directory
        listed in your $PATH (~/bin, /usr/local/bin, and /usr/bin are all good
        candidates). You can name this symlink whatever you want; I use "pmc".

    3. Try editing a file, by typing "pmc FILE" where FILE is the path to the
        file you want to edit.

    4. Edit the file!

        You can type Control-c and then Meta-h to get a list of all the
        available actions and which key(s) perform them. Type Control-x k to get
        out of the "help buffer". If you have used emacs, many (but not all) of
        these key bindings should seem familiar.

    5. Some basic key bindings:

        C-v (or PG_DN)    move down a page
        M-v (or PG_UP)    move up a page
        C-a (or HOME)     move to the beginning of the line
        C-e (or END)      move to the end of the line
        M-<               move to the beginning of the buffer
        M->               move to the end of the buffer
        M-g               goto line number

        C-s               interactive forward search
        C-r               interactive backward search
        M-%               interactive search-and-replace

        C-]               cancel

        C-/ (or C-x u)    undo last change
        M-/ (or C-x r)    redo last undone change

        C-x C-f           open file in a new buffer
        C-x k             close the current buffer

        C-c M-h           open a buffer listing all available key bindings
        C-c M-?           open a buffer listing all available functions
        M-?               get a help with a command by name
        M-h               get information about a key sequence

        C-x C-s           save your changes
        C-x C-c           quit

        NOTE: the notation used corresponds to the following:
            C-x     hold Control and press x.
            M-x     hold Meta and press x.
            C-c j   hold Control and press c, then press j
            C-x C-s hold Control and press x, then hold Control and press s

    6. Other documentation:

        a. MODES: this file describes in more detail how modes function, and
           how to write your own.

        b. other help commands

        c. comments in the source code

Good luck!