Everyone: Python is weird, main starts with:
if __name__=="__main__":
main(sys.argv[1:])

Me, side-eye:
(unless (member (program-name) '("chez" "petit" "scheme")) ;; is REPL
(main (command-line-arguments))
)

#scheme #repl

(I also sometimes use (member "--run" (command-line-arguments)) or the like, but program-name is clearer.
Some Schemes call main if you use it as a command-line program, not with load or include, but Chez leaves that up to you. RnRS specs are silent on the issue.)

#ReleaseWednesday — Extracted & extended the LISP-like DSL from an existing #ThingUmbrella example[1] as new small package for better/direct re-use in other projects:

https://thi.ng/lispy

The core language is kept intentionally minimal, aimed at simple sandboxed data transformations/derivations, small code snippets/expressions in GUIs or config settings. However, the language is very easy to extend/customize with new functions or control flow constructs etc. Currently, the language is interpreted and has the following builtins (see screenshots). There's no macro support so far (and not sure if that's even desired here)...

[1] The original #HowToThing example browser REPL this was extracted from (and which has now been updated to use the new package):

https://demo.thi.ng/umbrella/lispy-repl/

#ThingUmbrella #Lisp #DSL #FunctionalProgramming #REPL

Eric Normand on REPL-driven development in Lisp and other languages:

The REPL accelerates learning by increasing the speed and information richness of feedback.

[...]

Fast, rich feedback is essential to achieving a flow state.

https://ericnormand.substack.com/p/repl-driven-development-and-learning

Who in the world though it a good idea putting their custom readtables into libraries intended for outside use? I don't want your hash table syntax, I want MINE. Don't pollute the readtable and other aspects of someone else's image if you're providing a library. The library you're making should be portable and clean #CommonLisp, not some unreadable #DSL you use in your #REPL. It's fine in the REPL, but not in libraries. Keep it clean. Simple courtesy.

Not pointing fingers, but everyone doing that shall be ashamed.

I just discovered Jshell, a Java REPL shell. It's like Python's interactive shell , but in Java ;-)

It's not new. Jshell was introduced in ... Java 9. Shame to me I only learn about it in Java 23!

https://asciinema.org/a/nKxwuTgFPEeHgLfBakhcpomSO

Schemesh: A Unix shell and Lisp REPL, fused together

https://github.com/cosmos72/schemesh

Your web server having an interactive shell (REPL) where you can live update entries in your site/app’s database is pretty neat (if I do say so myself) :)

https://kitten.small-web.org/reference/#kitten-s-interactive-shell-repl

(I’m porting the Small Technology Foundation site¹ from Site.js² – and hence from being a static site generated via Site.js’s integrated Hugo³ – to Kitten⁴. In the process, I’m creating an admin panel⁵ for the news, events, and videos sections, which will make them easier to update, and storing the data in Kitten’s internal JavaScript Database⁶.)

¹ https://small-tech.org
² https://sitejs.org
³ https://gohugo.io/
⁴ https://kitten.small-web.org
⁵ It’s trivial to create authenticated routes in Kitten. You just add a lock emoji () to the end of your route’s name. e.g., admin.page.js or /admin/index.page.js (see https://kitten.small-web.org/reference/#sessions-and-authentication).
⁶ https://codeberg.org/small-tech/jsdb

#GodotEngine #REPL #GDScript

Is there a (core) repl in godot yet?

So my question is, what's an intuitive way to use dropping-in- #fortran from the #lisp #repl ?
Reading a .f file ~ into a let* form which I'm currently doing seems kind of bland. #f( this(1) = is(2) + a / fortran * line) seems kind of uninspiring (who would want to express themselves like this). Maybe Enter "fortran mode" and read lines of fortran from *standard-input* with normal interactive evaluation hacked in?

The fortran becomes #series expressions in lisp.

This is a really impressive demo of very interactive development environment: https://albertzak.com/run-build-grow/

It's far beyond of what Emacs or usual lisp IDE can do.

https://github.com/albertzak/open

Why is there no #neovim command to open a #lua #REPL to interact with the neovim lua API?

Despite ample evidence to the contrary, #Ilive (hmm, if I were also #evil, that would be a pallindrome as well as a visual collision)
Fascinating (if I do say so) #lispgames #gamejam #gamedev #retrospective on #itch_io
https://lispy-gopher-show.itch.io/lispmoo2/devlog/834615/princess-revisited
I am enormously happy with the
{ verb [ dobj [ prep iobj ] ] } x
language dynamic, and how it shares your #lisp #repl, and their concerns are just... Different so they don't collide.
I guess I get my #languageDesign friends a little better now.
Thoughts?

I your Europython live coding #MIDI demo talk!

I have always found working with a #REPL
and iteratively building interestingly dynamic systems to be one of the most under-sold aspects of modern computing!

https://www.youtube.com/watch?v=dK6HGcSb60Y

ce serait quoi selon vous la pile technique la plus économe en outils pour faire un simple #REPL sur une page html ?

A side of #guile: The Guile #REPL and investigating #guix packages
https://www.futurile.net/2023/12/04/guile-repl-with-guix-package-repl-queries/

by @futurile

Just added basic server/process stats to Kitten’s interactive shell (REPL).

Use the new `.stats` command to see them.

Also, documented the shell better in the Kitten Reference:

https://kitten.small-web.org/reference/#kitten-s-interactive-shell-repl

Łukasz Langa is giving the closing keynote of the EuroPython 2024 conference, entitled "Live coding music with PyREPL in Python 3.13" in Prague

Info
https://ep2024.europython.eu/session/live-coding-music-with-pyrepl-in-python-3-13

#EuroPython #EuroPython2024 #Python #REPL #Music

CC @europython @ambv

Another #pandoc #Lua #REPL tip: write the below Lua code to a file `panglob.lua` and call pandoc with
pandoc lua -l panglob -i
to make turn all pandoc functions into global variables. This allows to type `Pandoc('hi')` instead of `pandoc.Pandoc('hi')`.

for k, v in pairs(pandoc) do
_G[k] = v
end

Move `panglob.lua` to a directory in your LUA_PATH to make it accessible from everywhere.

There is a conference on Live Programming. It sound like a perfect fit for sharing our results on Guile Scheme IDE, which is more than 100% about live/interactive programming in Scheme language. Moreover, this event is not too academic, so I don't need to write a full-blown paper.

The only concern is that my USA visa is expired and getting a new one can take too much time :/

https://liveprog.org

My genuine thoughts: fuck those visas.