Timmy Jose timmyjose

Testimonies

CL's compiler

The thing in CL I miss most doing Clojure as my day job? CL's compiler. I like having a compiler tell me at compile time about the mistakes I've made. Bogus arguments. Unreachable code because of unhandled exceptions, and so on. CL saves me round after round of bugs that in clojure aren't found until you run the code. If you test well, it's found when testing, if you don't it's found in production. "Clojure compiler" almost demands air quotes.

CL's optional but oh-so-useful model of type declarations is also infinitely more useful (to me) than Clojure's use of "spec", and instrumentation that happens only at test time because of the cost. Depending on the OPTIMIZE declarations, other type defs are a floor wax and dessert topping. Want checks for argument types? Lower optimizations. Want most efficient machine code? High optimizations.

/u/Decweb, March 2023 https://www.reddit.com/r/lisp/comments/11ttnxk/the_rise_fall_of_lisp_too_good_for_the_rest_of/jczpysp/

Published Chapters

Program Analysis Resources

(draft; work in progress)

How to Setup Verified Commits

Quick guide on how to setup git signing. Information is aggregated from following sources:

So you’d like to contribute to Clojure, great! Let’s talk about what that involves.

The first thing you’ll want to make sure is that your idea is valid, and that you won’t spend a ton of time working on something that won’t make into master. To do this, you should create a JIRA ticket. For example, let’s say we want to improve how core.async handles channel closing propagation. It’s not a super complex problem, but there are some design questions about which of the various semantics currently in place should be the default, and if some semantics should be configurable.

So start by making a JIRA ticket and stating what the problem is you’re trying to solve, what the possible options for solving the problem. Now hit save and wait for the ticket to be triaged. Alex Miller will take a look when he can, and that can take a few days to a few weeks, depending on the time of the year (he has other responsibilities). Alex may out-right reject the idea if he knows Rich would never approve the ticket, but otherwise h

Sometimes, we have to access git repositories over SSL and the server only provides a self-signed certificate 🙈. Although there are ways to increase the trust level for the self-signed certificate (https://confluence.atlassian.com/fishkb/unable-to-clone-git-repository-due-to-self-signed-certificate-376838977.html, https://confluence.atlassian.com/bitbucketserverkb/resolving-ssl-self-signed-certificate-errors-806029899.html), my recommendation is to just ignore SSL verification alltogether.

Prepend GIT_SSL_NO_VERIFY=true before every git command run to skip SSL verification. This is particularly useful if you haven't checked out the repository yet.

Run git config http.sslVerify false to disable SSL verification if you're working with a checked out repository already.

	; https://z0ltan.wordpress.com/2018/08/04/simple-expression-evaluator-comparison-between-haskell-rust-and-common-lisp/

	; this version: 2018, Rainer Joswig, [email protected]

	; we create a bunch of structures for the expression types
	; each structure defines a constructor of the same name
	; each expression knows the corresponding Lisp function

	(defstruct (val (:constructor val (e))) e)
	(defstruct (bop :conc-name) e1 e2 op)

	# Set the control character to Ctrl+Spacebar (instead of Ctrl+B)
	set -g prefix C-space
	unbind-key C-b
	bind-key C-space send-prefix

	# Set new panes to open in current directory
	bind c new-window -c "#{pane_current_path}"
	bind '"' split-window -c "#{pane_current_path}"
	bind % split-window -h -c "#{pane_current_path}"

	# Generate a new pgp key: (better to use gpg2 instead of gpg in all below commands)
	gpg --gen-key
	# maybe you need some random work in your OS to generate a key. so run this command: `find ./* /home/username -type d \| xargs grep some_random_string > /dev/null`

	# check current keys:
	gpg --list-secret-keys --keyid-format LONG

	# See your gpg public key:
	gpg --armor --export YOUR_KEY_ID
	# YOUR_KEY_ID is the hash in front of `sec` in previous command. (for example sec 4096R/234FAA343232333 => key id is: 234FAA343232333)

	$ tmux --version
	tmux: illegal option -- -
	usage: tmux [-2CluvV] [-c shell-command] [-f file] [-L socket-name]
	[-S socket-path] [command [flags]]

	$ tmux --help
	tmux: illegal option -- -
	usage: tmux [-2CluvV] [-c shell-command] [-f file] [-L socket-name]
	[-S socket-path] [command [flags]]