Thread View: gnu.epoch.misc
2 messages
2 total messages
Started by Ranjan Bagchi
Thu, 28 Feb 1991 20:38
testing epoch
Author: Ranjan Bagchi
Date: Thu, 28 Feb 1991 20:38
Date: Thu, 28 Feb 1991 20:38
19 lines
1410 bytes
1410 bytes
I've built epoch 3.2, applied the first patch, and then
proceeded to modify the directory structure and placement of the lisp
code and such. It wasn't just for fun, I wanted to use as much of the
already-existant lisp code in the emacs tree so I wouldn't eat up too
much file space. Anyway, the crux of what I need is some code I can
run epoch over to determine if I've done anything really terrible or
not.
Can I be helped?
-rj
--
--------------------------------------------------------------------------------
Ranjan Bagchi - At Large. Well Kinda. | what kind of person
bagchi@[eecs | would want to count syllables
caen, | just to write haiku?
math.lsa].umich.edu |
--------------------------------------------------------------------------------
Re: testing epoch
Author: Chris Weikart
Date: Fri, 01 Mar 1991 18:46
Date: Fri, 01 Mar 1991 18:46
21 lines
1474 bytes
1474 bytes
In message <BAGCHI.91Feb28153811@snarf.eecs.umich.edu> Ranjan Bagchi writes:
> I've built epoch 3.2, applied the first patch, and then
> proceeded to modify the directory structure and placement of the lisp
> code and such. ...
I use gnuemacs lisp code by having added the appropriate search paths to
PATH_LOADSEARCH in src/paths.h. Thus epoch first searches locally, then
chez gnuemacs. You can then thin out whichever directories you choose,
right?
BTW, if you modify paths.h by hand, keep it from being "made" in Makefile:
all: src/paths.h ${SUBDIR}
can be changed to:
all: ${SUBDIR}
--------------------------------------------------------------------
Chris Weikart (weikart@prl.dec.com) DEC Paris Research Lab (PRL)
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads