Mercurial > emacs
annotate etc/LEDIT @ 57051:59091995520c
(msdos.o): Depend on buffer.h, commands.h, and
blockinput.h.
(dosfns.o): Depend on blockinput.h, window.h, dispextern.h,
charset.h, and coding.h
(w16select.o): Depend on buffer.h, charset.h, coding.h, and
composite.h.
(term.o): Depend on window.h and keymap.h.
(abbrev.o): Depend on syntax.h.
(callint.o): Depend on keymap.h.
(casefiddle.o): Depend on charset.h and keymap.h.
(category.o): Depend on keymap.h.
(coding.o): Depend on dispextern.h.
(cmds.o): Depend on keyboard.h and keymap.h.
(dispnew.o): Depend on indent.h and intervals.h.
(doc.o): Depend on keymap.h.
(editfns.o): Depend on frame.h.
(emacs.o): Depend on dispextern.h.
(fileio.o): Don't depend on ccl.h.
(filelock.o): Depend on charset.h and coding.h.
(frame.o): Depend on w32term.h and macterm.h.
(insdel.o): Depend on region-cache.h.
(keyboard.o): Depend on keymap.h, w32term.h, and macterm.h.
(minibuf.o): Depend on $(INTERVALS_SRC) and keymap.h.
(search.o): Depend on $(INTERVALS_SRC).
(syntax.o): Depend on keymap.h, regex.h, and $(INTERVALS_SRC).
(window.o): Depend on keymap.h, blockinput.h, $(INTERVALS_SRC),
xterm.h, w32term.h, and macterm.h.
(xdisp.o): Depend on keyboard.h, $(INTERVALS_SRC), xterm.h,
w32term.h, and macterm.h.
(xfaces.o): Depend on keyboard.h, $(INTERVALS_SRC),
region-cache.h, xterm.h, w32term.h, and macterm.h.
(bytecode.o): Depend on dispextern.h, frame.h, and xterm.h.
(data.o): Depend on frame.h.
(fns.o): Depend on keymap.h, xterm.h, and blockinput.h.
(print.o): Depend on termchar.h and $(INTERVALS_SRC).
(lread.o): Depend on $(INTERVALS_SRC), termhooks.h, and coding.h.
(intervals.o): Depend on keymap.h.
author | Eli Zaretskii <eliz@gnu.org> |
---|---|
date | Fri, 10 Sep 2004 18:16:57 +0000 |
parents | 23a1cea22d13 |
children |
rev | line source |
---|---|
25928 | 1 Date: 17 Apr 85 15:45:42 EST (Wed) |
2 From: Martin David Connor <mdc@MIT-HTVAX.ARPA> | |
3 | |
4 Date: Sat, 13 Apr 85 16:28:15 est | |
5 From: Richard M. Stallman <rms@mit-prep> | |
6 | |
7 Can you help this person? Also, can you give me the rest of ledit | |
8 to distribute, plus some info on how to use it? | |
9 | |
10 I have put the files "ledit.l" and "leditcfns.c" on prep:~mdc. | |
11 Much to my disgust ledit.l relied on some bogus little package of | |
12 functions on HT, so I had to massage it a bit. | |
13 | |
14 To get it to work, one must: | |
15 | |
16 - Compile leditcfns.c with something like: | |
17 | |
18 cc leditcfns.c | |
19 | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
25928
diff
changeset
|
20 - Edit ledit.l, changing the line beginning "(cfasl" to |
25928 | 21 have the right pathname for the cfns file you compiled in |
22 the last step. | |
23 | |
24 - Compile ledit.l with: | |
25 | |
26 liszt ledit.l | |
27 | |
28 Then put the following lines in your .lisprc file: | |
29 | |
30 ;load in functions for emacs interface | |
31 (load "//src//mdc//ledit//ledit") ; Location of Ledit library | |
32 (set-proc-str "%gnumacs") ; Name of editor | |
33 | |
34 Then you can use ^E <RETURN> to get from LISP back to gnumacs. | |
35 | |
36 Here is the part of my .emacs file that pertains to ledit. | |
37 | |
38 ;;; Set up ledit mode | |
39 (setq ledit-go-to-lisp-string "%lisp") | |
40 (setq lisp-mode-hook 'ledit-from-lisp-mode) | |
41 | |
42 Date: Sat, 13 Apr 85 11:26:32 cst | |
43 From: neves@wisc-ai.arpa (David Neves) | |
44 | |
45 This is a documentation question. | |
46 I cannot figure out how to use Ledit. I suspect I need some | |
47 function on the Franz Lisp end of things to go to Emacs and read in | |
48 the temporary file. Is this true? Is the Lisp job started within | |
49 Emacs or outside of emacs? I'm just plain confused. Perhaps a couple | |
50 of words from someone in the know would help. | |
51 | |
52 A related question. I have been using a shell buffer when interacting | |
53 with Lisp (ie. put a definition in the kill buffer and then yank it | |
54 into the shell buffer to redefine it). This is nice but tends to fill | |
55 up the shell buffer with lots of code (I'd rather keep calls to functions | |
56 in the shell and not the functions themselves). | |
57 My question: Is using the shell buffer "better" than ledit? Am I using | |
58 it in the best way (i.e. copying definitions from an edit buffer to the | |
59 shell buffer)? -Thanks, David Neves | |
60 | |
61 I have found that ledit works well for doing programming development | |
62 when you are changing lots of little pieces of a file and don't wish | |
63 to recompile the whole file. Of course M-X Compile is very nice for | |
64 calling up a liszt on a buffer and watching it in the another window. | |
65 Of course the interface of something like NIL is even better because | |
66 you can compile your function directly into your lisp. But since NIL | |
67 doesn't run under Unix, this is probably the next best thing. | |
68 | |
69 I have tried the 2 window method (shell in lower window, lisp code in | |
70 upper), and have found it a little awkward. It does have certain | |
71 advantages, but most of the time, I get be fine using M-C-D to save a | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
25928
diff
changeset
|
72 defun for lisp, and C-X Z to jump back to LISP. C-E RETURN from lisp |
25928 | 73 is also mnemonic for getting back to gnumacs. |
74 | |
75 I hope this helps somewhat. | |
76 | |
77 |