Thread View: comp.emacs
3 messages
3 total messages
Started by Aaron Dailey
Thu, 07 Jan 1993 22:58
minimum files to run gnu emacs
Author: Aaron Dailey
Date: Thu, 07 Jan 1993 22:58
Date: Thu, 07 Jan 1993 22:58
20 lines
1409 bytes
1409 bytes
We're setting up a portable sparc system to run standalone for trips in the field. Unfortunately, we only have a 200 MB hard drive, and need to put several tools on it. I want to put emacs on it, but I need to minimize the space it takes. Although I've used emacs for over a year, I'm realizing I don't really understand entirely what happens when you type emacs and the editor appears magically. So, what do I need? Of course, I need the executable. How 'bout the elisp files - some of them seem to be loaded dynamically (the rectangle functions come to mind), but most are already in the executable? If I need the elisp files, do I just need the .elc files, not the .el files. None of the .c or .o files, I assume, and nothing from the ./etc directory, except the executables. Thanks, -- Aaron Dailey Internet: Aaron_Dailey@stortek.com StorageTek Corporation Voice: (303) 673-4989, FAX: (303) 673-2570 Mail: MS0242, 2270 South 88th Street, Louisville, C0 80028
Re: minimum files to run gnu emacs
Author: Dietmar Braun
Date: Fri, 08 Jan 1993 14:19
Date: Fri, 08 Jan 1993 14:19
40 lines
2364 bytes
2364 bytes
In article <AAROND.93Jan7155820@xibm.StorTek.com>, aarond@xibm.StorTek.com (Aaron Dailey) writes:
|> [...]
|> So, what do I need? Of course, I need the executable. How 'bout the
|> elisp files - some of them seem to be loaded dynamically (the
|> rectangle functions come to mind), but most are already in the
|> executable? If I need the elisp files, do I just need the .elc files,
|> not the .el files. None of the .c or .o files, I assume, and nothing
|> from the ./etc directory, except the executables.
|>
|> Thanks,
|>
|> --
|> Aaron Dailey Internet: Aaron_Dailey@stortek.com
|> StorageTek Corporation Voice: (303) 673-4989, FAX: (303) 673-2570
|> Mail: MS0242, 2270 South 88th Street, Louisville, C0 80028
|>
Hello,
It works without anyting but the executable. You will miss some comfort
and emacs gives some warnings (can't find etc directory, can't find lisp ...)
before startup.
So for a comfortable setup, You might make Your own version of default.el.
You should check all commands, you want to use, and make appropriate autoload
entries default.el. Then You need *.elc versions of all those files.
elc size is about 1/3, so it's better to use .elc then .el.
(This is also faster)
At last You'll need something from lisp/term, if You want to use
arrow keys/function keys. But I don't know exactly.
Hope this gives You an idea
regards
Dietmar
--
---------------------------------------------------------------------
SMail: Dietmar Braun; Universitaet Bielefeld | __o
Technische Fakultaet AG WBS / KI | _`\<,_
Postfach 8640; W-4800 Bielefeld 1; Germany| (_)/ (_)
EMail: dietmar@techfak.uni-bielefeld.de |
---------------------------------------------------------------------
Re: minimum files to run gnu emacs
Author: Dale DePriest
Date: Mon, 11 Jan 1993 21:30
Date: Mon, 11 Jan 1993 21:30
30 lines
1285 bytes
1285 bytes
Naturally I have all of the information at home and I am at work
so I'll have to do this from memory.
In the lisp directory you will only need the .elc files for the most part.
To find out what you really need do the following:
cd /usr/local/emacs/lisp
ls -utl | more
and then
ls -utl term
look at the dates. The files are sorted by the most recent time
anyone actually used the file. Look down the list and pick a
date. Everything below the line can be deleted. You can use
some intelligence if you expect to be doing something unusual.
Now do the same thing to /usr/local/emacs/etc.
Note that the on-line help is in the file DOC-18....
You may want to take it along.
Hope this helps.
--
_ _ Dale DePriest San Jose, California
/`) _ // daled@Cadence.COM voice: (408) 428-5249
o/_/ (_(_X_(`
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