🚀 go-pugleaf

>Could some kind soul out there please give me a list of reasons why I should
>switch from emacs to epoch? What are some of the things that are easily done
>in epoch but not in emacs? Thank you very much.

I find epoch's basic ability, the multiple windows, to be the biggest
improvement.  I put each file I'm currently working with into a
separate window, and then iconify most of them (I have Motif give me
the tiny icons that just have the names); I can then bounce around
through the units of my code much more easily than I could with Emacs.
I also have icons I leave up permanently: my home directory, gnus,
rmail, and a note-taking program I wrote.  I have extended dired to
let me press F instead of f to find the file in another window, and
control-right-button for the same; I can scroll up or down with
shift-left or -right button (an extension of my own); and copying by
mouse is nice.  But the quick access to many files is the biggest
thing; it makes it much easier to perceive the structure of my code.

/===========================================================================\
|John (Francis) Stracke         |My opinions are my own.                    |
|Natl. Science Center Foundation|===========================================|
|Augusta, GA                    | Newt Nuggets!                             |
|francis@dogwood.atl.ga.us      |                                           |
\===========================================================================/
(Formerly francis@zaphod.uchicago.edu)

>>>>> On Fri, 26 Jun 1992 20:54:08 GMT, ggu@chpc.org (Gary G. Gu) said:
> Could some kind soul out there please give me a list of reasons why I should
> switch from emacs to epoch? What are some of the things that are easily done
> in epoch but not in emacs? Thank you very much.

I've become completely addicted to having comments, code and other
important bits in different colors (or fonts on monochrome).  Mouse
support is also much better in Epoch, though I don't use it as much.

Oddly enough I didn't use the multiple windows much at first because
if I'm looking at two windows at a time, paning seems better than
overlapping to me.  Now that I have to work on some code that's
formatted for 132 columns, I keep one wide window (with a smaller
font) and one normal window.  With the very recent advent of Rich
Mauri's VR (see export.lcs.mit.edu:/contrib/vr...), I keep one global
screen and one for each "room".

For a previously unposted example of what you can do with colors,
LaTeX users might want to load the following after hilit.el.  I find
that it does a great job of clarifying LaTeX commands embedded in
other text.

(setq latex-mode-hilit
      '(("^%.*" nil 0)			    ; Comments
        ("[\t]%.*" nil 0)		    ; End of line comments
        ("^\\\\.*" nil 2)		    ; Line commands
        ("\\\\[a-z][a-z][a-z]+{.*}" nil 2)  ; Indented major commands
        ("{\\\\[a-z][a-z] [^}]+}" nil 9)    ; Font changes
        ("[ \t]+\\\\item " nil 1)	    ; List items
        ("[ \t]+\\\\item \\[.*\\]" nil 1)   ; List (description) items
        ("\\\\footnote{[^}]+}" nil 6)	    ; Footnotes
        ("\\\\label{[^}]+}" nil 7)	    ; Cross Reference Label
        ("\\\\psfig{[^}]+}" nil 0)	    ; Postsript file load
	))
(hilit::mode-list-update "LaTeX" latex-mode-hilit)

                                            dan
--
Dan L. Pierson          Digital Equipment Corporation
pierson@crl.dec.com     Massively Parallel Systems Group