🚀 go-pugleaf

In article <ANDERSON.91Aug21212511@sapir.cog.jhu.edu> anderson@sapir.cog.jhu.edu (Stephen R. Anderson) writes:

   Organization: Dept. of Cognitive Science, The Johns Hopkins University
   Lines: 9
   Xref: laas gnu.epoch.misc:248 comp.sys.next.programmer:480 comp.sys.next.misc:1771

   I'd like to echo Chet's implication that anyone planning to use epoch
   should at least know how to set the load path themselves, and in
   general know their way around the emacs/epoch sources well enough to
   find the lisp libraries, etc. Epoch has always been advertised as an
   explicitly experimental variant of emacs: caveat emptor. Complain if
   it doesn't work, but not just because you have to find (and set) a
   couple of shell variables to get it to do what you want.

   --Steve Anderson

I am the original poster of the complaints about the screw up version of Epoch
Next....

n my original article I was not only complaining about the LOADPATH, but on the
fact that the archive was full of .o and temacs (2 copies) and various compiled
version of epoch (2 copies) ... All that for 5 megas...

What kind of impression do you have when you download 5 mega of software to
discover that 1) it has not been clean up 2) the change made to get this
version of epoch compiling are not even documented and installed in the source,
3) as a consequence it does not even compile again properly....???  If you
are lucky enough to download things for free... You probably do not care...

I do, and I am telling other people that this version of Epoch is pretty much
useless as is.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Francois Felix INGRAND                   "Read my Lisp... No new syntax" (nil)
felix@laas.fr