farolero
bash-modules
farolero | bash-modules | |
---|---|---|
16 | 7 | |
362 | 122 | |
- | - | |
2.4 | 0.0 | |
about 1 month ago | about 2 years ago | |
Clojure | Shell | |
Eclipse Public License 1.0 | GNU Lesser General Public License v3.0 only |
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.
farolero
-
clojure from common lisp
You can use this library to get CL-style conditions and restarts in Clojure: https://github.com/IGJoshua/farolero
-
Val on Programming: What makes a good REPL?
True, the CL REPL is more useful than the Clojure REPL, but CL has a 20-30 year head start in development. Plus, Clojure was developed as a hosted language, and runs on .NET, Javascript, JVM, and even Dart (in-progress).
Since exceptions are quite deeply integrated into those platforms (as opposed to conditions), it has "bled through" to the Clojure APIs, and, in turn, REPL.
Folks have written a CL-style condition/restart library for Clojure (https://github.com/IGJoshua/farolero) too.
- IGJoshua/farolero: Thread-safe Common Lisp style conditions and restarts for Clojure(Script).
- Opinions of "brothers and sisters"...
-
How to handle errors or failed computations in clojure?
conditions/restarts are also a possibility https://github.com/IGJoshua/farolero
-
ClojureRS – Clojure interpreter implemented in Rust
Someone added conditions/restarts to Clojure: https://github.com/IGJoshua/farolero
It does allow errors to be caught by the Repl and just.hkw to handle them.
-
What are the advantages of Hy/Hissp over python bindings for CL/Clojure?
farolero
-
Clojure REPL vs. CLI: IDE Wars
This is interesting tool[1] that allows much the same with Clojure
[1]: https://github.com/IGJoshua/farolero
-
Do we have good use case based examples of usage of derive based hierarchies and multi-methods?
https://github.com/IGJoshua/farolero This uses derive hierarchies to enable general error handling.
- Show HN: Farolero – Common Lisp style-conditions and restarts for Clojure
bash-modules
-
Write Posix Shell
Bash is turing-complete, so it's possible to write automated test cases in bash. Example: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...
-
Shell Script Best Practices, from a decade of scripting things
Template in article is awful. It's better to use this one, which is a real CLI tool: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...
-
Show HN: A plain-text file format for todos and check lists
IMHO, you are mixing TODO lists and task management/planning software. No, I don't know a good task manager or business process manager for command line. Instead, I created a simpler TODO list manager, called `td`[0], which supports flat TODO lists only, and use directories and command-line generators to manage todo's. `td` prints top item only, by default, leaving little room for procrastination. I'm keeping one `TODO.md` file per project instead of one large TODO file for all todo's.
[0]: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...
-
bash-modules 4.0.1
Documentation: http://vlisivka.github.io/bash-modules/ Project home page: https://github.com/vlisivka/bash-modules
- Bash-Modules 4.0
-
Bash function names can be almost anything
I'm preparing to release bash-modules 4.0 [0]. Can you give me feedback, please? I'm a non-native English speaker, so I need someone to help fix spelling mistakes, at least.
https://github.com/vlisivka/bash-modules
-
Clojure REPL vs. CLI: IDE Wars
It works in my shell. :-/ It looks like you forgot to insert `false` command.
You are pointing to the problem with -e not working in subshell/deep functions, because of POSIX. Right? It's described in bash documentation: http://www.gnu.org/software/bash/manual/html_node/The-Set-Bu...
> I think just defining a die() function and using it after any command that must succeed is more verbose, but less error prone:
Yep. It's the style I developed 12 years ago, when working at Bazaarvoice, when I was lead of devops team. I created the whole library for bash, to use this pattern consistently. See https://github.com/vlisivka/bash-modules#error-handling
What are some alternatives?
cloroutine - Coroutine support for clojure
dotfiles - Bootstrap neovim/zsh/tmux environment for Ruby on Rails development
ex - In which we deal with exceptions the clojure way
mg.sh - Mitigram's shell library of reusable script snippets
wingman - Restartable exception handling for Clojure, allowing you to recover from exceptions without unwinding the stack.
xit - A plain-text file format for todos and check lists
clojure-scheme - Clojure to Scheme to C to the bare metal.
murex - A smarter shell and scripting environment with advanced features designed for usability, safety and productivity (eg smarter DevOps tooling)
cloture - Clojure in Common Lisp
ShellCheck - ShellCheck, a static analysis tool for shell scripts
py4cl2 - Call python from Common Lisp
music-explorer - A music scraper, navigator, archiver, and cataloger for people looking for new sounds.