wishlist

Explore SSH servers listed in your ~/.ssh/config file (local mode)

$ wishlist

$ wishlist [[s|serve]]

$ wishlist [[-c|--config]] [path/to/config.yaml]

$ wishlist --zeroconf.enabled

$ wishlist --srv.domain [example.com]

$ wishlist --tailscale.net=[tailnet_name] --tailscale.key=[tskey-api-abc123]

wishlist command [OPTIONS] [ITEM...]
wishlist list [OPTIONS]

add ITEM...
    Adds one or more items to the wishlist. Items can be quoted if they contain spaces.

list
    Displays all items currently in the wishlist, optionally with details.

remove ID|ITEM...
    Removes items by their numerical ID or by matching text from the wishlist.

clear
    Removes all items from the wishlist. Requires confirmation.

mark ID|ITEM
    Marks an item (e.g., as 'purchased' or 'obtained').

-f, --file PATH
    Specify an alternative file to store the wishlist data.

-p, --priority LEVEL
    Assigns a priority level (e.g., 1-5) to an item upon addition.

-s, --show-marked
    When listing, also show items that have been marked (e.g., as purchased).

-h, --help
    Displays help information for the command.

The command wishlist is NOT a standard Linux utility. This analysis describes a hypothetical command that would provide a simple, text-based interface for maintaining a list of desired items or tasks. Users could add new items, view existing ones, remove completed or unwanted entries, and perhaps prioritize or categorize them. This conceptual command would likely store its data in a plain text file, adhering to the Unix philosophy of simple, composable tools. While not a standard utility, the concept facilitates personal organization directly from the terminal, leveraging common command-line patterns for list manipulation and aiming for quick interaction without requiring complex GUI applications.

The command wishlist is NOT a standard Linux command or utility. The information provided here describes a conceptual command based on common CLI patterns for managing lists. Users typically implement such functionality using shell scripts, aliases, or by leveraging existing text manipulation tools.

A hypothetical wishlist command would typically store its data in a plain text file (e.g., ~/.wishlist). Each line might represent an item, optionally prefixed with a status or ID. Basic operations like adding would involve appending to the file, while removing or marking would involve reading, modifying, and rewriting the file, often using temporary files for atomic updates.

Beyond basic add/list/remove, a robust wishlist tool could incorporate features like due dates, categories, links to online stores, or even integration with external services. These extensions would likely be implemented through additional command options, specific data formatting within the wishlist file, or by piping output to other commands.

As a standalone, standard Linux command, wishlist has no official history or development. However, the concept of maintaining personal wish lists or to-do lists using simple text files and command-line tools is as old as the Unix philosophy itself. Many users create custom shell scripts or leverage existing utilities to manage such lists, predating the rise of dedicated GUI applications for personal organization. The idea reflects a common need for lightweight, scriptable personal data management.

grep(1), sed(1), awk(1), sort(1), uniq(1), nano(1), vim(1), todo.txt-cli