Kitten now has a lovely new multi-page Settings screen and… drumroll… a new 🐢 interactive shell (REPL) for you to play with the running state of your Small Web site/app/place and debug your app, inspect/manipulate its database, etc.
I plan on recording demos of each of them tomorrow but you can play with them now.
And here’s a little tutorial to get you started with the shell:
One of the issues with the #REPL (and #emacs which is just a great big text-oriented repl) is that it is additive in nature; it usually takes major effort or a restart to REMOVE things once they've been added (thinking on plugins which modify app state). #Clojure
When SwiftUI was first released, one of the great features that piqued my interest was the instant preview function. This feature empowers developers to
Don't even know where to start. I'm working with "integrant" in #clojure project and every bit of state is managed, I can start/stop/suspend/resume, #repl experience and testing is fantastic.
Is such technique unique and happens only in clojure?
and lastly, maybe emacs macros could benefit from some interactive refinement editor, many times you need to run it a few times to realize you missed a state. It would be cool to be able to prototype them live.
i don't know if i shared this here already, i almost forgot about this:
"OCellator is a work-in-progress #lisp-like #synth language, combined with a web-based structural editor. Build small audio programs and hear how it changes the sound as you type!"
Did you know that you can set an initialization file for the #Python#REPL (aka "interactive mode")?
I use this to auto-import "os" and "sys" in every interactive Python, as well as the rich library (if installed) to provide pretty-printed and syntax-highlighted output for expression results.
Basically, just set the environment variable PYTHONSTARTUP to the path to your initialization file.
It's one of my favorite things to be able to piece together the flow of a program function by function, block by block, and tweak things on the fly without any compilation or interruption.
#Clojure does this well with multiple IDE's which all support REPL directly fed with source code files, usually displayed in another window.
And honestly? Having used it for years when, for whatever reason, I had nothing else on a job site? #Powershell ISE works great.
Until now I seriously underestimated #eshell in #emacs. Wow, the integration it has is amazing, I get nice autocompletion and, of course, integration with Elisp. The only problem is that I have to adapt to the Eshell way of doing things (i.e. stuff like eval "$(ssh-agent -s)" don't quite work) and it's a dumb terminal (quite literally, so I have vterm as a backup), but FWIW it is underrated, don't scoff at it.
@stalecu I recently got into #eshell myself and have been doing as much as I can with it while using #vterm as a fallback. It's pretty sweet, and I no longer need the #Python#REPL as a calculator. I can use #elisp REPL instead when I want to see how badly I got screwed by working unpaid overtime.
It's possible to run FactoryBot and Rspec straight from IRB/Pry with:
require 'rspec/expectations'
include RSpec::Matchers # use RSpec matches and expectations
require 'factory_bot'
# For usage in Rails console
# require 'factory_bot_rails'
FactoryBot.find_definitions # load factories
include FactoryBot::Syntax::Methods # loads FB methods like #create and #build