Jamie-BitFlight

bash-53-features

Bash 5.3 release features and improvements with practical examples. Use when working with Bash 5.3 features, new command substitution, GLOBSORT, loadable builtins, or when user asks about Bash 5.3 changes, new features, or version-specific capabilities.

Jamie-BitFlight 50 9 Updated 3mo ago
GitHub

Install

npx skillscat add jamie-bitflight/claude-skills/bash-53-features

Install via the SkillsCat registry.

SKILL.md

Bash 5.3 Features and Improvements

Released in July 2025, Bash 5.3 introduces significant enhancements including revolutionary command substitution syntax, new variables, loadable builtins, and improved C standard conformance.

Revolutionary Command Substitution

Efficient In-Shell Execution: ${ command; }

Execute commands without forking, dramatically improving performance:

# Traditional command substitution (creates subshell)
result=$(echo "Hello, World")

# NEW: In-shell command substitution (no fork!)
# Note: a space (or tab/newline/|) is required after the opening '{'
result=${ echo "Hello, World"; }

# Practical example: Fast variable assignment
config_value=${ grep "^timeout=" config.txt | cut -d= -f2; }

# Performance comparison function
benchmark_substitution() {
    local i
    local start end

    echo "Testing traditional substitution..."
    start="${EPOCHREALTIME}"
    for ((i = 0; i < 1000; i++)); do
        result=$(echo "${i}")
    done
    end="${EPOCHREALTIME}"
    printf 'Traditional: %.4f seconds\n' \
        "$(awk "BEGIN {print ${end} - ${start}}")"

    echo "Testing new in-shell substitution..."
    start="${EPOCHREALTIME}"
    for ((i = 0; i < 1000; i++)); do
        result=${ echo "${i}"; }
    done
    end="${EPOCHREALTIME}"
    printf 'In-shell: %.4f seconds\n' \
        "$(awk "BEGIN {print ${end} - ${start}}")"
}

benchmark_substitution

Benefits:

  • No subprocess creation overhead
  • Significantly faster for simple commands
  • Reduced resource usage in loops
  • Same syntax familiarity as command substitution

REPLY Variable Capture: ${| command; }

Execute commands and automatically store output in REPLY. Note: REPLY is local to the
substitution — its value is restored after completion, so capture it immediately:

# Output goes to REPLY — capture it right away
${| date +%Y-%m-%d; }
today="${REPLY}"
echo "Today is: ${today}"

# Practical example: Multiple captures
get_system_info() {
    local os kernel host

    ${| uname -s; }
    os="${REPLY}"

    ${| uname -r; }
    kernel="${REPLY}"

    ${| hostname; }
    host="${REPLY}"

    printf 'System: %s %s on %s\n' "${os}" "${kernel}" "${host}"
}

get_system_info

# Example: Processing pipeline results
process_data() {
    local error_count warning_count

    ${| grep "ERROR" logfile.txt | wc -l; }
    error_count="${REPLY}"

    ${| grep "WARNING" logfile.txt | wc -l; }
    warning_count="${REPLY}"

    printf 'Errors: %d, Warnings: %d\n' "${error_count}" "${warning_count}"
}

# Example: Conditional logic — capture REPLY before using it
check_service() {
    local service="${1}"
    local status

    ${| systemctl is-active "${service}" 2>/dev/null; }
    status="${REPLY}"

    if [[ "${status}" == "active" ]]; then
        echo "Service ${service} is running"
        return 0
    else
        echo "Service ${service} is not running"
        return 1
    fi
}

check_service "ssh"

Benefits:

  • Cleaner code without intermediate variables
  • Consistent capture mechanism
  • Reduced visual clutter
  • Perfect for rapid prototyping

Use Cases Comparison

# String manipulation - use in-shell for efficiency
filename="document.txt"
basename=${ echo "${filename%.*}"; }
extension=${ echo "${filename##*.}"; }

# Output capture - use REPLY for clarity
${| df -h / | tail -1 | awk '{print $5}'; }
disk_usage="${REPLY}"
echo "Disk usage: ${disk_usage}"

# Complex pipelines - traditional might still be clearer
result=$(cat file.txt | grep pattern | sort | uniq)

GLOBSORT Variable

Control the sorting order of filename and pathname expansion. The specifier is optionally
prefixed with + (ascending, default) or - (descending):

# Set sort order for globbing (prefix + = ascending, - = descending)
GLOBSORT="name"       # Sort by name (default, ascending)
GLOBSORT="+name"      # Explicit ascending name sort
GLOBSORT="-name"      # Descending name sort
GLOBSORT="+size"      # Sort by file size (ascending)
GLOBSORT="-size"      # Descending size sort
GLOBSORT="+mtime"     # Sort by modification time (ascending)
GLOBSORT="-mtime"     # Newest files last

# Practical example: Process largest files first
process_by_size() {
    local dir="${1}"

    GLOBSORT="-size"

    for file in "${dir}"/*; do
        [[ -f "${file}" ]] || continue

        size=$(stat -f%z "${file}" 2>/dev/null || stat -c%s "${file}" 2>/dev/null)
        printf 'Processing %s (%d bytes)\n' "${file}" "${size}"
        # Process file...
    done
}

process_by_size "/var/log"

# Example: Process newest files first
process_newest() {
    local dir="${1}"
    local -a files

    GLOBSORT="-mtime"
    files=("${dir}"/*)

    echo "Processing files from newest to oldest:"
    for file in "${files[@]}"; do
        [[ -f "${file}" ]] || continue
        echo "  ${file}"
    done
}

process_newest "/tmp"

Available sort specifiers:

  • name — Alphabetical by filename
  • size — By file size
  • mtime — By modification time
  • atime — By access time
  • ctime — By inode change time
  • blocks — By allocated block count
  • numeric — Numeric sort on leading digits in filename
  • nosort — Disable sorting (glob order)
  • Prefix: + (ascending, default) or - (descending)

Enhanced Builtins

compgen with Variable Storage

Store completions directly in a variable:

# NEW: Store completions in variable
compgen -V completions -c ba

echo "Commands starting with 'ba':"
for cmd in "${completions[@]}"; do
    echo "  ${cmd}"
done

# Practical example: Custom completion helper
get_available_commands() {
    local prefix="${1}"
    local -a commands

    compgen -V commands -c "${prefix}"

    if [[ ${#commands[@]} -eq 0 ]]; then
        echo "No commands found starting with '${prefix}'"
        return 1
    fi

    printf 'Available commands (%d):\n' "${#commands[@]}"
    printf '  - %s\n' "${commands[@]}"
}

get_available_commands "git"

read with Readline Completion (-E)

Interactive input with autocompletion:

# Enable readline completion during read
choose_file() {
    local file

    echo "Enter filename (tab for completion):"
    read -e -r -E -p "> " file

    if [[ -f "${file}" ]]; then
        echo "Selected: ${file}"
        return 0
    else
        echo "File not found: ${file}"
        return 1
    fi
}

choose_file

# Practical example: Interactive configuration
configure_app() {
    local config_file

    echo "Select configuration file:"
    read -e -r -E -p "Config: " config_file

    if [[ -f "${config_file}" ]]; then
        ${| grep -c "^[^#]" "${config_file}"; }
        local line_count="${REPLY}"
        echo "Found ${line_count} active configuration lines"
    fi
}

source with Path (-p)

Specify search path for sourced scripts:

# Traditional source
source /opt/app/lib/utils.sh

# NEW: Source with custom path
source -p "/opt/app/lib:/usr/local/lib" utils.sh

# Practical example: Library loader
load_library() {
    local lib_name="${1}"
    local -a search_paths=(
        "${HOME}/.local/lib"
        "/usr/local/lib"
        "/opt/lib"
    )

    local search_path
    search_path=$(IFS=:; echo "${search_paths[*]}")

    if source -p "${search_path}" "${lib_name}" 2>/dev/null; then
        echo "Loaded library: ${lib_name}"
        return 0
    else
        echo "Failed to load library: ${lib_name}" >&2
        return 1
    fi
}

load_library "common.sh"

printf Enhancements

New options for multibyte strings and representations:

# Enhanced printf options
printf '%q\n' "string with spaces"  # Shell-quoted output

# NEW: Multibyte string support improvements
text="Hello, 世界"
printf 'Length: %d bytes\n' "${#text}"

# Practical example: Safe command construction
build_command() {
    local -a args=("$@")
    local arg cmd=""

    for arg in "${args[@]}"; do
        cmd+=$(printf '%q ' "${arg}")
    done

    echo "Safe command: ${cmd}"
}

build_command ls "-l" "file with spaces.txt"

New Loadable Builtins

kv - Key-Value Arrays

Create associative arrays from key-value data. Note: The kv builtin existence is
confirmed in Bash 5.3; the exact interface shown below is illustrative — verify with
help kv after loading:

# Enable kv builtin (if not already loaded)
enable -f /usr/local/lib/bash/kv kv 2>/dev/null || true

# Create associative array from key=value pairs
declare -A config
kv config <<EOF
database_host=localhost
database_port=5432
database_name=myapp
api_key=secret123
debug_mode=true
EOF

# Access values
echo "Database: ${config[database_host]}:${config[database_port]}"
echo "Debug: ${config[debug_mode]}"

# Practical example: Parse environment-style config
load_env_config() {
    local config_file="${1}"
    declare -gA APP_CONFIG

    while IFS='=' read -r key value; do
        # Skip comments and empty lines
        [[ "${key}" =~ ^[[:space:]]*# ]] && continue
        [[ -z "${key}" ]] && continue

        # Trim whitespace
        key="${key#"${key%%[![:space:]]*}"}"
        value="${value#"${value%%[![:space:]]*}"}"

        APP_CONFIG["${key}"]="${value}"
    done < "${config_file}"
}

strptime - Date Parsing

Parse textual dates into Unix timestamps. Note: The strptime builtin existence is
confirmed in Bash 5.3; the exact interface shown below is illustrative — verify with
help strptime after loading:

# Enable strptime builtin
enable -f /usr/local/lib/bash/strptime strptime 2>/dev/null || true

# Parse date string to timestamp
date_string="2025-07-15 14:30:00"
timestamp=$(strptime "%Y-%m-%d %H:%M:%S" "${date_string}")

echo "Timestamp: ${timestamp}"
echo "Date: $(date -d "@${timestamp}" '+%Y-%m-%d %H:%M:%S')"

# Practical example: Log timestamp parsing
parse_log_timestamp() {
    local log_line="${1}"
    local timestamp_str date_format timestamp

    # Extract timestamp from log line
    timestamp_str="${log_line%% *}"

    # Parse different date formats
    if [[ "${timestamp_str}" =~ ^[0-9]{4}-[0-9]{2}-[0-9]{2}$ ]]; then
        date_format="%Y-%m-%d"
    elif [[ "${timestamp_str}" =~ ^[0-9]{2}/[0-9]{2}/[0-9]{4}$ ]]; then
        date_format="%m/%d/%Y"
    else
        echo "Unknown date format" >&2
        return 1
    fi

    timestamp=$(strptime "${date_format}" "${timestamp_str}")
    echo "${timestamp}"
}

parse_log_timestamp "2025-07-15 Application started"

fltexpr - Floating-Point Calculations

Perform floating-point arithmetic without external tools:

# Enable fltexpr builtin
enable -f /usr/local/lib/bash/fltexpr fltexpr 2>/dev/null || true

# Floating-point calculations
result=$(fltexpr "3.14159 * 2.0")
echo "Result: ${result}"

# Practical example: Performance metrics
calculate_average() {
    local -a values=("$@")
    local sum=0.0
    local count=${#values[@]}

    for value in "${values[@]}"; do
        sum=$(fltexpr "${sum} + ${value}")
    done

    local average
    average=$(fltexpr "${sum} / ${count}")
    echo "${average}"
}

response_times=(0.123 0.456 0.234 0.567 0.321)
avg=$(calculate_average "${response_times[@]}")
echo "Average response time: ${avg}s"

# Example: Calculate percentage
calculate_percentage() {
    local part="${1}"
    local total="${2}"
    local percentage

    percentage=$(fltexpr "(${part} / ${total}) * 100.0")
    printf '%.2f%%\n' "${percentage}"
}

calculate_percentage 75 200  # 37.50%

POSIX Mode Improvements

Enhanced POSIX compliance:

# Enable POSIX mode
set -o posix

# String comparisons now follow locale rules
[[ "ä" < "z" ]]  # Locale-dependent comparison

# Improved POSIX conformance in builtins
# test, trap, wait, bind all more strictly conformant

# Practical example: Portable script header
#!/usr/bin/env bash

if [[ "${BASH_VERSINFO[0]}" -ge 5 ]] && [[ "${BASH_VERSINFO[1]}" -ge 3 ]]; then
    # Bash 5.3+ available, use modern features
    USE_MODERN_FEATURES=1
else
    # Fall back to POSIX mode for portability
    set -o posix
    USE_MODERN_FEATURES=0
fi

Improved Error Reporting

More detailed error messages:

# Regular expression compilation errors now include details
pattern="[invalid"

if [[ "test" =~ ${pattern} ]]; then
    echo "Match"
else
    # Error message now explains what went wrong:
    # bash: regex error: brackets ([ ]) not balanced
    echo "No match" >&2
fi

# Practical example: Robust pattern validation
validate_pattern() {
    local pattern="${1}"
    local test_string="test"

    if [[ "${test_string}" =~ ${pattern} ]] 2>/dev/null; then
        echo "Pattern is valid"
        return 0
    else
        echo "Invalid regex pattern: ${pattern}" >&2
        return 1
    fi
}

validate_pattern "[a-z]+"  # Valid
validate_pattern "[a-z"    # Invalid

C Standard Conformance Improvements

Bash 5.3 improves conformance to modern C standards (the build minimum remains C90):

  • No longer compiles with K&R C compilers
  • Modernized codebase for better conformance
  • Better optimization opportunities
  • Improved type safety

Note: This primarily affects developers compiling Bash from source, not end users.

Performance Improvements

  • Command substitution without forking (${ cmd; }) dramatically reduces overhead
  • Optimized globbing with GLOBSORT
  • Faster builtin operations
  • Reduced memory usage in various operations
# Benchmark: Traditional vs new substitution
benchmark() {
    local iterations=10000
    local i start end

    start="${EPOCHREALTIME}"
    for ((i = 0; i < iterations; i++)); do
        result=$(echo test)
    done
    end="${EPOCHREALTIME}"
    printf 'Traditional: %.4f seconds\n' \
        "$(awk "BEGIN {print ${end} - ${start}}")"

    start="${EPOCHREALTIME}"
    for ((i = 0; i < iterations; i++)); do
        result=${echo test;}
    done
    end="${EPOCHREALTIME}"
    printf 'In-shell: %.4f seconds\n' \
        "$(awk "BEGIN {print ${end} - ${start}}")"
}

benchmark

Migration Guide

From Bash 5.2 to 5.3

Most scripts compatible, but consider:

# Take advantage of new command substitution for performance
# OLD:
for file in *; do
    size=$(stat -f%z "${file}" 2>/dev/null)
done

# NEW (faster):
for file in *; do
    ${| stat -f%z "${file}" 2>/dev/null; }
    size="${REPLY}"
done

# Use GLOBSORT for better file processing
GLOBSORT="-mtime"
for file in *.log; do
    process_recent_log "${file}"
done

# Leverage new builtins where appropriate
# Instead of: awk calculation
# Use: fltexpr for floating-point math

Version Detection

# Check for Bash 5.3 features
if [[ "${BASH_VERSINFO[0]}" -ge 5 ]] && [[ "${BASH_VERSINFO[1]}" -ge 3 ]]; then
    echo "Bash 5.3+ features available"
    CAN_USE_INSITU_SUBSTITUTION=1
    CAN_USE_GLOBSORT=1
else
    echo "Bash version: ${BASH_VERSION}"
    CAN_USE_INSITU_SUBSTITUTION=0
    CAN_USE_GLOBSORT=0
fi

References

Additional Resources

For broader Bash development patterns and best practices, see: