#Chawan - a web browser for your terminal

Project page

#What is this?

A text-mode web browser. It displays websites in your terminal and allows you to navigate on them.

It can also be used as a terminal pager.

#Compiling

Note: a POSIX-compliant operating system is required.

1. Clone the Chawan repository:
   git clone https://git.sr.ht/~bptato/chawan && cd chawan
2. Install the Nim compiler: https://nim-lang.org/install.html
   • Please use 1.6.14 or newer, ideally 2.2.0. Versions older than 1.6.14 will not work. (You can check your Nim compiler's version using nim -v.)
3. Install the following dependencies:
   • libcurl
   • OpenSSL (or LibreSSL)
   • libssh2
   • pkg-config, pkgconf, or similar (must be found as "pkg-config" in your $PATH)
   • GNU make
   • Recommended: a termcap library; e.g. ncurses comes with one
   • TL;DR for Debian: apt install libssh2-1-dev libcurl4-openssl-dev pkg-config make ncurses-base
4. Download parts of Chawan found in other repositories: make submodule
5. Run make (without arguments).
6. Install using make install (e.g. sudo make install).

Then, try:

$ cha -V # open in visual mode for a list of default keybindings
$ cha example.org # open your favorite website directly from the shell
$ mancha cha # read the cha(1) man page using `mancha'

#Packages

Alternatively, you can install Chawan from packages maintained by volunteers:

• AUR: https://aur.archlinux.org/packages/chawan-git
• NixOS: look for package "chawan"

#Features

Currently implemented features are:

• multi-processing, incremental loading of documents
• multi-charset, double-width aware text display (but no bi-di yet)
• HTML5 support, forms, cookies
• CSS-based layout engine: supports flow layout, table layout, flexbox layout
• user-programmable keybindings (defaults are vi(m)-like)
• basic JavaScript support in documents (disabled by default for security reasons)
• supports several protocols: HTTP(S), FTP, Gopher, Gemini, Finger, etc.
• user-defined protocols and file formats
• markdown viewer, man page viewer
• sixel/kitty image support
• mouse support
• syscall sandboxing on FreeBSD, OpenBSD and Linux (through capsicum, pledge and seccomp-bpf)

...with a lot more planned.

#Documentation

• build/compilation options: doc/build.md
• manpage: doc/cha.1
• configuration options: doc/config.md
• API description (for keybindings): doc/api.md
• mailcap: doc/mailcap.md
• mime.types: doc/mime.types.md
• urimethodmap: doc/urimethodmap.md
• local CGI: doc/localcgi.md
• protocols: doc/protocols.md
• inline images: doc/image.md
• troubleshooting: doc/troubleshooting.md

If you're interested in modifying the code:

• architecture: doc/architecture.md
• style guide, debugging tips, etc.: doc/hacking.md

#FAQ

#I have encountered a bug/technical issue while using Chawan.

Please check our troubleshooting document. If this does not help, please open a ticket or post to the mailing list.

#I'm interested in the technical details of Chawan.

Here's some:

• The browser engine (HTML parsing, rendering, etc.) has been developed from scratch in the memory-safe Nim programming language. Some of these modules are now also available as separate libraries.
• Uses QuickJS-NG for JavaScript execution and regex matching.
• Each buffer (page) is isolated in a separate process. File loading is done through dedicated loader processes.
• termcap for basic terminal capability querying, and terminal queries where possible.
• The default image decoder (PNG, JPEG, GIF, BMP) uses the stb_image library, and WebP images are decoded using the JebP library. Image codecs are handled as protocols, so users can add their own codecs (with urimethodmap).

For further details, please refer to the architecture document.

#Why write another web browser?

w3m is close to my ideal browser, but its architecture leaves a lot to be desired. So initially I just wanted a simple w3m clone with a more maintainable code base.

The project has evolved a lot since then, even including things I had not initially intended to (like CSS). Now it is mainly focused on:

• Simplicity, as much as "modern standards" permit. Chawan has very few external dependencies, and favors reduced code size over speed. This lowers the risk of supply chain attacks, and helps me understand what my browser is doing.
• Secure defaults over convenience. Like w3m, extra configuration is needed to enable dangerous features (JS, cookies, etc.) Unlike w3m, we also run buffers in separate, sandboxed processes.
• Adding the rest of missing w3m features, and improving upon those.
• Most importantly: having fun in the process :)

#Neighbors

Many other text-based web browsers exist. Here's some recommendations (not meant to be an exhaustive list):

• w3m - A text-mode browser, extensible using local CGI. Also has inline image display and very good table support. Main source of inspiration for Chawan.
• elinks - Has CSS and JavaScript support, and incremental rendering (it's pretty fast.)
• links - Precursor of elinks, but it's still being developed. Has a graphical mode.
• lynx - Doesn't need an introduction. The oldest web browser still in active development.
• edbrowse - This one looks more like ed than less or vi. Originally designed for blind users.
• telescope - A "small internet" (Gemini, Gopher, Finger) browser. Has a very cool UI.
• offpunk - An offline-first browser for Web, Gemini, Gopher, Spartan. Separates "downloading" from "browsing".
• browsh - Firefox in your terminal.
• Carbonyl - Chromium in your terminal.

#Relatives

Ferus is a separate graphical browser engine written in Nim, which uses Chawan's HTML parser.

#License

Chawan is dedicated to the public domain. See the UNLICENSE file for details.

Chawan also includes and depends on several other libraries. For further details, check the about:license page in Chawan, or read the same document here.