How do I print bash scripts with syntax highlighting?

Paste your shell script into Codeprint and select Shell/Bash as the language. Variables, functions, and control structures are highlighted. Export via Print or PDF.

Does it support zsh and fish syntax?

Codeprint uses bash highlighting which covers most POSIX shell and zsh syntax. Fish-specific syntax may not be fully highlighted.

Can I print Dockerfiles?

Dockerfiles use shell-like syntax. Select Shell/Bash for reasonable highlighting of RUN commands, ENV variables, and other directives.

How does it handle heredocs in scripts?

Bash heredocs (<<EOF) are highlighted as string blocks with the delimiter recognized. Variable expansion within heredocs is also colorized.

Turn Shell/Bash code into a PDF worth printing.

Keep Shell/Bash syntax colors, line numbers, and the layout you choose. Preview every page and export the PDF without uploading your code.

Paste your Shell/Bash code

script.shEDITOR MODE

Code input

Filename

Language

#!/bin/bash
set -euo pipefail

# Configuration
readonly APP_NAME="myapp"
readonly LOG_DIR="/var/log/${APP_NAME}"
readonly BACKUP_DIR="/backups/${APP_NAME}"

log() {
    echo "[$(date '+%Y-%m-%d %H:%M:%S')] $*" | tee -a "${LOG_DIR}/deploy.log"
}

check_dependencies() {
    local deps=("docker" "docker-compose" "jq" "curl")

for dep in "${deps[@]}"; do
        if ! command -v "$dep" &>/dev/null; then
            log "ERROR: $dep is not installed"
            exit 1
        fi
    done
    log "All dependencies satisfied"
}

deploy() {
    local version="${1:?Version required}"
    local environment="${2:-staging}"

log "Deploying ${APP_NAME} v${version} to ${environment}"

# Backup current state
    mkdir -p "${BACKUP_DIR}"
    docker-compose config > "${BACKUP_DIR}/docker-compose.$(date +%s).yml"

# Pull and deploy
    docker-compose pull
    docker-compose up -d --remove-orphans

# Health check
    for i in {1..30}; do
        if curl -sf "http://localhost:8080/health" > /dev/null; then
            log "Deployment successful: health check passed"
            return 0
        fi
        sleep 2
    done

log "ERROR: Health check failed after 60 seconds"
    return 1
}

check_dependencies
deploy "$@"

Preview

Loading preview...

Paste code. See it formatted. Export as PDF.

Bash Syntax Highlighting

Full support for variables, functions, pipes, redirects, heredocs, arrays, and control structures.

PDF Export

Export shell scripts as PDF for operations runbooks and deployment documentation.

Customizable Layout

Adjust font and layout for scripts with long pipe chains or complex variable expansions.

Line Numbers

Line numbers are essential for shell scripts where specific lines may be referenced in logs.

When you’d print Shell/Bash

Operations Runbooks

Print deployment scripts for operations runbooks. Include formatted scripts in incident response docs.

Security Audits

Print shell scripts for security review. Check for injection vulnerabilities and unsafe practices.

CI/CD Documentation

Print CI pipeline scripts for documentation. Format GitHub Actions, Jenkins, and GitLab CI scripts.

Teaching Shell

Create handouts for shell scripting workshops. Colorized pipes and redirects aid comprehension.

How it works

Step 1

Paste Your Code

Paste your Shell/Bash code into the editor or type directly. The language is auto-detected from the file extension.

Step 2

Customize Settings

Adjust font size, line numbers, columns, page orientation, and page size to match your needs.

Step 3

Print or Export PDF

Click Print to send to your printer, or PDF to download a formatted document with syntax highlighting preserved.

Why print Shell/Bash?

Shell/Bash source is easier to review when its structure survives the move from editor to page. Full support for variables, functions, pipes, redirects, heredocs, arrays, and control structures. Codeprint keeps indentation and line breaks intact, then applies a restrained syntax palette so keywords, strings, comments, and identifiers remain distinguishable in print.

A paper review creates a different reading rhythm from an IDE. You can see more of the file at once, mark a questionable branch, compare related expressions, and refer back to a precise line without opening the same toolchain. Line numbers are essential for shell scripts where specific lines may be referenced in logs.

Export shell scripts as PDF for operations runbooks and deployment documentation. Page size, orientation, columns, and type size remain under your control, which matters when the source contains long expressions or dense blocks. It is a practical fit for operations runbooks, security audits, and technical documentation. Your source stays in your browser throughout the process.

Questions

Other languages

Python JavaScript TypeScript HTML CSS Java C C++C#Go Rust PHP Ruby Swift Kotlin SQL JSON R Dart Scala