如何在Bash中用getopts处理任意顺序的长短选项（不使用getopt）

Great question! Since getopts only natively supports single-character short options, we can work around this by first manually parsing your long-style flags (--add, --del, --update) before passing the remaining arguments to getopts for handling the short options (-f, -a, -d). Here's a practical, maintainable approach that fits your exact use case:

Example Script Implementation #

#!/bin/bash

# Initialize variables to store input values
action=""
emp_name=""
firstname=""
age=""
detail=""

# First pass: manually process long options
while [[ $# -gt 0 ]]; do
    case "$1" in
        --add)
            action="add"
            shift
            # Capture the required employee name
            if [[ $# -gt 0 ]]; then
                emp_name="$1"
                shift
            else
                echo "Error: --add requires an employee name" >&2
                exit 1
            fi
            ;;
        --del)
            action="del"
            shift
            if [[ $# -gt 0 ]]; then
                emp_name="$1"
                shift
            else
                echo "Error: --del requires an employee name" >&2
                exit 1
            fi
            ;;
        --update)
            action="update"
            shift
            if [[ $# -gt 0 ]]; then
                emp_name="$1"
                shift
            else
                echo "Error: --update requires an employee name" >&2
                exit 1
            fi
            ;;
        *)
            # Stop looping once we hit non-long-option arguments
            break
            ;;
    esac
done

# Second pass: use getopts for short options
while getopts "f:a:d:" opt; do
    case "$opt" in
        f) firstname="$OPTARG" ;;
        a) age="$OPTARG" ;;
        d) detail="$OPTARG" ;;
        \?) echo "Invalid option: -$OPTARG" >&2; exit 1 ;;
        :) echo "Option -$OPTARG requires an argument." >&2; exit 1 ;;
    esac
done

# Validate that an action was specified
if [[ -z "$action" ]]; then
    echo "Error: You must specify one of --add, --del, or --update" >&2
    exit 1
fi

# Execute logic based on the selected action
case "$action" in
    add)
        echo "=== Adding Employee ==="
        echo "Name: $emp_name"
        [[ -n "$firstname" ]] && echo "First Name: $firstname"
        [[ -n "$age" ]] && echo "Age: $age"
        [[ -n "$detail" ]] && echo "Details: $detail"
        # Replace with your actual add logic here
        ;;
    del)
        echo "=== Deleting Employee ==="
        echo "Name: $emp_name"
        # Replace with your actual delete logic here
        ;;
    update)
        echo "=== Updating Employee ==="
        echo "Name: $emp_name"
        [[ -n "$firstname" ]] && echo "New First Name: $firstname"
        [[ -n "$age" ]] && echo "New Age: $age"
        [[ -n "$detail" ]] && echo "New Details: $detail"
        # Replace with your actual update logic here
        ;;
esac

How This Works #

1. Long Option Parsing: We start with a manual loop to catch the --add, --del, and --update flags. For each, we set an action variable, capture the required employee name, and shift those arguments out of the parameter list so getopts doesn't see them.
2. Short Option Handling: Once the long options are processed, we use getopts to parse the remaining short options (-f, -a, -d) and their values. This keeps the clean, familiar getopts syntax for optional parameters.
3. Action Execution: Finally, we run the appropriate logic based on the captured action, using all the variables populated from both parsing steps.

Why This Fits Your Needs #

• It works with all the example command invocations you listed, regardless of the order of short options.
• No need for getopt (which has inconsistent behavior across macOS and Linux).
• Easy to maintain: the manual long option parsing is straightforward, and getopts handles all the edge cases for short options (like missing arguments or invalid flags).

内容的提问来源于stack exchange，提问作者prabhakaran