slime
fructure
Our great sponsors
slime | fructure | |
---|---|---|
14 | 8 | |
1,851 | 443 | |
1.8% | - | |
8.2 | 3.7 | |
2 days ago | 3 months ago | |
Common Lisp | Racket | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
slime
- Emacs 28 can not run Slime
-
Anyone know why newlines get randomly inserted when printing a list with format on emacs + slime?
Try https://github.com/slime/slime/commit/e6a71c725c8e13d7d4c40e6a6fa7b696575a8d01
-
So i wanna learn Common Lisp
With emacs your two choices are either SLIME or SLY. Slime is a good place to start - it's rock solid. Once you get moving you can make a judgement call on whether or not SLY has features you'd like over what SLIME has available.
-
Common Lisp vs Racket
To provide a bit more context, most of SLIME is just Common Lisp code (https://github.com/slime/slime), with a bunch of Emacs Lisp code alongside to support interfacing with Emacs. But you don't need that Emacs Lisp code to take advantage of almost all of the functionality SLIME provides. For instance, if you want to know who-calls a function, there's some command in emacs to do it, but all that command is doing is just a bit of elisp code which sends a message to Swank (a server running inside Common Lisp) and Swank invokes some native CL code to figure that out and return the results, then finally a bit of elisp code presents the results in some way. Vim can do the same thing just fine with vimscript/python (what the Slimv plugin uses) or otherwise, the bulk of the work in figuring out the list of callers of some function is done by the CL code (and CL implementation itself).
-
What does your workflow look like on Linux?
SLIME or SLY for Common Lisp (if you want to work with it), Geiser for various Schemes
-
slime-pop-find-definition-stack not working
That's rather new, https://github.com/slime/slime/commit/789584a7acb15747678fa62a8fcfc8d1187be867 is probably about that.
- Offline Hyperspec? html, texinfo, org, something?
-
Slime
With that headline on HN, I was expecting this: https://common-lisp.net/project/slime/
-
Python REPL-driven development in Emacs
SLIME or Sly for Common Lisp, Geiser for most Scheme implementations, or racket-mode for Racket?
-
Is there a possibility to have a master stack in bspwm like in dwm?
For example, some people that are Common Lisp programmers, but don't use GNU Emacs, may decide to use GNU Emacs because of the slime-mode workflow.
fructure
-
Racket: The Lisp for the Modern Day
Even the racket teachpack libraries designed for education are very capable; I was able to make this structured editor with only using teachpack content without external deps: https://github.com/disconcision/fructure
-
Common Lisp vs Racket
Right, it's fine, and is a pretty basic macro. Doubly linked lists are pretty basic data structures too, even the Rust versions once you figure it out. I like your sibling comment making it look like the CL version. I still want to know in more detail though why you think that doing things this way instead of the CL way is less likely to be "fragile and break down" for the complicated stuff, it would help to have a specific complicated example to showcase. Perhaps the linked https://github.com/disconcision/fructure in another comment would be a good study? The author there claimed they might not have been able to manage with defmacro, maybe someone familiar with both could articulate the challenges in detail. Is it just an issue of some things benefit a lot from pattern matching, and if so, does using CL's Trivia system mitigate that at all (in the same way that using gensym+packages+Lisp-2ness can mitigate hygiene issues)?
- Fructure: A structured interaction engine in Racket
-
graph-based UI for Lisp/Scheme
see also: fructure
- Why text only.
- An Intuition for Lisp Syntax
What are some alternatives?
sly - Sylvester the Cat's Common Lisp IDE
LIBUCL - Universal configuration library parser
portacle - A portable common lisp development environment
vlime - A Common Lisp dev environment for Vim (and Neovim)
paip-lisp - Lisp code for the textbook "Paradigms of Artificial Intelligence Programming"
cmu-infix - Updated infix.cl of the CMU AI repository, originally written by Mark Kantrowitz
hebigo - 蛇語(HEH-bee-go): An indentation-based skin for Hissp.
coherence - Oracle Coherence Community Edition
bsp-layout - Manage layouts in bspwm (tall and wide)
slimv - Official mirror of Slimv versions released on vim.org
common-lisp-jupyter - A Common Lisp kernel for Jupyter along with a library for building Jupyter kernels.
racket-binfmt - A binary format parser generator DSL with support for limited context-sensitivity.