🚀 go-pugleaf

I've been using emacs 19.8 for almost a whole day now.

Things I like, relative to epoch:
vanilla configuration and building is easier
scroll bars
binding X keys is easier, more intuitive
documentation on X things is better (at least in info)
mouse pop-up menus (control-mouse-1 pops up a "deck of cards" menu,
  from which you can do just about anything)

Things I don't like:
custom configuration and building is harder
apparently won't do mouse-drag hiliting
can't underscore regions on mono displays
  (but you can change the color or invert the region)
doesn't run on my Apollo (but I can fix that)
mouse use is less intuitive (but can be changed)

I also can't figure out how to get it to work the way I like to use epoch,
which is to have a single minibuffer, and each buffer in its own window.  I
think this can be done but I haven't figured it out yet.  It's got a
variable you can set to give each buffer its own window ("screen" in epoch
terminology, "frame" in emacs, "window" to X) but it doesn't really work
the way I want.

For now I'm going to stick with epoch.

There are apparently some political bugs with emacs as well.  For example,
the code to make emacs run on Apollo Domain/OS has been around for years,
but rms refuses to incorporate it in to emacs without getting signatures on
paperwork from the authors of the Apollo code.  I don't know the details,
but I do know that it was no problem at all getting the Apollo code into
epoch, and epoch runs right out of the box on an Apollo.  I say this not
because I think the Apollo code is so imporant, but because I suspect the
same political considerations might apply to other modifications that could
be just as important.

I'm very happy about the reported merging of epoch with lucid.  I'm familiar
with Leonard Zubkoff's work, and I think a combined epoch/lucid would be
much better (for my purposes) than emacs 19.