Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!<UNAUTHENTICATED>+
From: Sean.Levy@CS.CMU.EDU
Newsgroups: comp.windows.x
Subject: Re: Epoch 3.2 and Emacs 19.0
Message-ID: <UbLGPxK00hMw839Wlb@cs.cmu.edu>
Date: 5 Dec 90 16:57:33 GMT
References: <502@zok.UUCP>,
	<BRUCEC.90Nov29171101@phoebus.labs.tek.com>
Organization: Carnegie Mellon, Pittsburgh, PA
Lines: 22
In-Reply-To: <BRUCEC.90Nov29171101@phoebus.labs.tek.com>

> Excerpts from netnews.comp.windows.x: 30-Nov-90 Re: Epoch 3.2 and Emacs
> 19.0 Cohen;;50-662;LP=A;@phoe (993)

> I hope not.  Epoch has a lot of useful and interesting features, but it
> isn't very compatible with previously written emacs packages.  This is
> because of the model of "screens" as orthogonal to emacs buffers and
> windows.  Try for instance, to run gdb-mode or gnus in epoch.

I run gdb mode all the time under epoch. What's your problem? All the
other goodies I and others have written seem to work just fine (comint
mode and its derivatives, etc.). Could you elaborate on what kinds of
problems you have? I intend on writing much elisp, which, I expect, will
work without change under vanilla gnu emacs and epoch, modulo nifty
epochy things I add (in a modular way, of course).



		{ Sean }

Mail: Sean Levy | EDRC | CMU | 5000 Forbes Ave | Pittsburgh, PA 15213
Campus: Hamburg Hall 2212, Ext. 2257 (+1 412 268 2257)
EMail: snl+@cs.cmu.edu | ...!harvard!cs.cmu.edu!snl