Question 1

How do I set up SBLint with a git pre-commit hook?

Accepted Answer

Copy the provided shell script to .git/hooks/pre-commit, ensure SBLint is installed via Roswell, and it will automatically run before commits, blocking those with lint errors based on the error count.

Question 2

SBLint or flycheck for Common Lisp linting in Emacs?

Accepted Answer

SBLint is a standalone linter focused on SBCL and ASD files, offering project-wide automation, while flycheck is an Emacs plugin that integrates various linters for real-time feedback. Choose SBLint for automated workflows, but flycheck for editor-centric use.

Question 3

Can SBLint be used without Roswell?

Accepted Answer

Installation is primarily through Roswell for dependency management, as per the README. While manual installation might be possible, Roswell is recommended to handle SBCL and SBLint dependencies seamlessly.

Question 4

What types of errors does SBLint catch?

Accepted Answer

SBLint leverages SBCL's compiler to analyze code, detecting issues like type mismatches, undefined functions, and common style warnings specific to the SBCL environment, based on its integration with ASD files.

Question 5

Is SBLint compatible with Quicklisp projects?

Accepted Answer

Yes, since Quicklisp often uses ASD files, SBLint can lint Quicklisp-based projects by loading their ASD files, as indicated in the usage for directory-based linting.

Question 6

How to integrate SBLint with GitHub Actions?

Accepted Answer

Use the reviewdog integration; set up a GitHub Actions workflow that runs SBLint and pipes output to reviewdog using the provided error format, enabling automated PR comments and code reviews.

sblint

Overview

Use Cases

Not Ideal For

Pros & Cons

Pros

Related Projects

Found a gem we're missing?

Cons

Frequently Asked Questions