emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* What is Babel's relationship with a Lisp REPL? State or stateless?
@ 2015-02-20 12:54 Lawrence Bottorff
  2015-02-20 14:13 ` John Kitchin
  2015-02-20 16:41 ` Grant Rettke
  0 siblings, 2 replies; 3+ messages in thread
From: Lawrence Bottorff @ 2015-02-20 12:54 UTC (permalink / raw)
  To: emacs-orgmode

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]

If I'm creating an org file in a buffer which has source blocks for, say,
Lisp, then I can "run" these blocks of Lisp code and Babel will fill in the
"answer" just below in my buffer. Good. As advertised. But what is really
happening to this code? Does Babel invoke a Lisp REPL once, do the code,
print out the results my buffer and go away? Or is this invoked REPL
somehow persistent, able to remember what has happened before?

With regular Lisp and SLIME, you have a buffer where you write your code
next to a running REPL that handles the code when you ask it to. It keeps
"state" and your program grows. But this arrangement is not really literate
programming. Maybe good comments are possible, but it's not orgmode
literate programming.

But then again, if Babel doesn't support REPL "state," then what am I
gaining? Please enlighten me. . . .


LB

[-- Attachment #2: Type: text/html, Size: 987 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-02-20 16:49 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-20 12:54 What is Babel's relationship with a Lisp REPL? State or stateless? Lawrence Bottorff
2015-02-20 14:13 ` John Kitchin
2015-02-20 16:41 ` Grant Rettke

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).