blob: f578d32a64baa936dda6859b9879b10e9cbcb4fe (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
[[!meta title="CLEDE the Common Lisp Emacs Development Environment."]]
[[!meta copyright="Copyright © 2021 Fermin MF"]]
[[!inline pages="internal(2021/info/clede-nav)" raw="yes"]]
<!-- You can manually edit this file to update the abstract, add links, etc. --->
# CLEDE the Common Lisp Emacs Development Environment.
Fermin MF
[[!inline pages="internal(2021/info/clede-schedule)" raw="yes"]]
I've been developing a package that helps with the development of
Common Lisp's software,
it's uses the internal semantic framework, it has a custom reader
and integration for
common Emacs packages (like Sly and the internal inferior-lisp-mode).
The idea is to supply features that other language with and static
analyzer have,
like refactoring and code generation.
For more details: <https://gitlab.com/sasanidas/clede>
- 20 minutes:
It seems like not too much people knows about semantic, so I can
summarize some of it in 10 minutes
and then An explanation on how to use the package, how to extend it
and the future of it.
# Discussion
Pad:
- Q1: You mentioned clede-start - is there also some kind of clede-stop? (I often get frustrated with functionality that I cannot disable / revert)
- A: There is no stop, you should never stop doing common lisp :)
- Q2: Is writing common lisp a big context switch between elisp?
- A: In some regards, it is, Ithink even more when you work Common Lisp professionally.
[[!inline pages="internal(2021/captions/clede)" raw="yes"]]
[[!inline pages="internal(2021/info/clede-nav)" raw="yes"]]
|
