Powerlisp: Common Lisp tool for automating tasks for Unix power-users
github.com
github.com
This is basically a way to create menus and submenus for recurrent utilities. You can use a rofi or dmenu frontend. Once you bind it a key shortcut, rofi/dmenu will come up asking you what to do.
Right now I can directly access my favorite websites, open my favorite programs, do web search (and also switch web engine), all without touching the browser directly. The idea is to group a lot of things in a lightweight script, and have a keyboard-only interaction with no extra extensions or programs.
I agree that the README is a little poor right now, and screenshots/gifs would also help on this regard. I'll start working on it pretty soon.
It might be a good idea to add screenshots or a gif or something to the README, and I see they've realized that.
https://github.com/40ants/cl-bitbar
It is a library to write plugins for https://getbitbar.com
I'd also love to see terminal Emacs as the default shell editor for this shell.
https://github.com/oilshell/oil/wiki/ExternalResources#inter...
I thought that was called emacs...{ducks}
/...though seriously...
In general I have dreamed for ages of one language could enough to do everything I want to do with a computer. And I am pretty imaginative as to what is in that set.
But I'm not sure where to start automating this. It would be great to have some examples.
I plan to migrate this to a more flexible Roswell script in a near future.
NB: I read SICP cover to cover twenty years ago, did many private projects with DrScheme (Racket) and was influenced by it's paradigms early on. I do appreciate Lispy topics, but why front page of HN?
I think Common Lisp specifically is enjoying a bit of a spike in popularity (at least on HN, I've noticed a lot more front page stories over the last some years than previously) especially as more people realize it's out of the box way more powerful than what you find in SICP's Scheme. (A few offhand things one finds: type declarations with compile-time error checking in the most popular implementation + type info used to produced optimized assembly you can immediately inspect, non-braindead OOP, non-braindead error system, multi-million line software project existence proofs, long history of useful old code that still works like an inline arithmetic reader macro...)