Mercurial > emacs
annotate etc/LEDIT @ 59384:a1edc5959dcf
* macfns.c: Include sys/param.h.
[TARGET_API_MAC_CARBON] (mac_nav_event_callback): New declaration
and function.
[TARGET_API_MAC_CARBON] (Fx_file_dialog): Use MAXPATHLEN for size
of filename string. Set event callback function when creating
dialog boxes. Add code conversions for filenames. Don't dispose
apple event descriptor record if failed to create it.
* macterm.c: Include sys/param.h.
[USE_CARBON_EVENTS] (mac_handle_window_event): Add handler for
kEventWindowUpdate.
(install_window_handler) [USE_CARBON_EVENTS]: Register it.
(do_ae_open_documents) [TARGET_API_MAC_CARBON]: Get FSRef instead
of FSSpec from apple event descriptor record.
(do_ae_open_documents) [TARGET_API_MAC_CARBON]: Use MAXPATHLEN for
size of filename string.
[TARGET_API_MAC_CARBON] (mac_do_receive_drag): Likewise.
[TARGET_API_MAC_CARBON] (mac_do_receive_drag): Return error when a
file dialog is in action.
[TARGET_API_MAC_CARBON] (mac_do_track_drag): Likewise. Reject
only when there are no filename items. Set background color
before (un)highlighting the window below the dragged items.
(XTread_socket) [!USE_CARBON_EVENTS]: Don't call do_window_update.
author | Steven Tamm <steventamm@mac.com> |
---|---|
date | Thu, 06 Jan 2005 02:53:39 +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 |