#cowsay #terminal #customization #fortune #fortune-cookie

app shell-toy

A "fortune | cowsay" implementation in Rust, i.e. a nice little toy to liven up your shell.

10 releases (5 breaking)

0.6.0 Oct 20, 2024
0.5.1 Sep 21, 2024
0.4.0 Sep 1, 2024
0.3.2 Aug 23, 2024
0.1.1 Aug 2, 2024

#90 in Text processing

Download history 172/week @ 2024-07-27 156/week @ 2024-08-03 18/week @ 2024-08-10 184/week @ 2024-08-17 243/week @ 2024-08-24 189/week @ 2024-08-31 74/week @ 2024-09-07 21/week @ 2024-09-14 160/week @ 2024-09-21 71/week @ 2024-09-28 4/week @ 2024-10-05 3/week @ 2024-10-12 134/week @ 2024-10-19 7/week @ 2024-10-26

141 downloads per month

MIT license

73KB
1.5K SLoC

shell-toy

A fortune | cowsay implementation in Rust.

THIS IS STILL A WIP Demo (Pardon the glitches, those are from the asciinema recording)

Installation

Currently, pre-built binaries are not provided since the project is in a state I don't consider to be "finished".

For now the best way is to use Cargo:

cargo install shell-toy

This will install shell-toy to your local path as sh-toy. You can then put it in whatever terminal startup script you want.

Cargo Features & Environment Flags

There are some compile-time features that enable shell-toy to perform certain things such as using an internal copy of fortunes embedded in the executable. This can be customized based on what you want. More details are below:

Feature Description
inline-fortune Enables inlining fortunes in the compiled sh-toy executable. See Compiling with Inline Things for more details
inline-off-fortune Also inlines Offensive fortunes. These are still blocked behind the -o flag
inline-cowsay Enables inlining cowsay files in the compiles sh-toy executable. . See Compiling with Inline Things for more details

There are also some environment variables that the build script does existence checks on which overrides build-script behavior. Unless specified, the build script will only check if the variable exists and not the value. Remove the variable instead of setting it to 0 in these cases to disable the variable's behavior.

Env Variable Description
USE_DEFAULT_RESOURCES Will ignore COW_PATH, FORTUNE_FILE, and FORTUNE_PATH variables if they exist and instead use resources extracted from the archives defined in BuildConfig.toml. This is not required if the aforementioned variables are undefined.
FORCE_DOWNLOAD Will redownload resource archives even if they exist. This has no effect if "default resources" are not being used.
COW_PATH Value is used by build script. Indicates where to find the cow files to inline in the executable if the inline-cowsay feature is enabled.
FORTUNE_FILE   FORTUNE_PATH Value is used by build script. Indicates where to find the cow files to inline in the executable if the inline-fortune feature is enabled.   Use the FILE variant if all fortunes are in a single file and there is no need to differentiate fortunes as offensive or not.

Compiling with Inline Things

The build script will look for the following IN THIS ORDER when it comes to using the fortunes:

  1. If the FORTUNE_FILE environment variable is specified, the build script will only use the contents of that file.
  2. If the FORTUNE_PATH environment variable is specified, it will embed the fortunes in that directory and subdirectory as a single file.
    1. Offensive fortunes that are in a subdirectory off are processed separately and only embedded if the inline-off feature is enabled. So if you have FORTUNE_PATH=~/.config/fortunes, place offensive fortunes in ~/.config/fortunes/off
  3. The build script will pull use the fortunes in the archive and internal archive path specified in BuildConfig.toml.

Additional Notes There is a settings block in BuildConfig.toml that allows you to specify how long fortunes can be when being processed for inlining. These are optional and by default are commented out, but you can uncomment them to enable the functionality and adjust the values for your liking.

The build script will look for the following IN THIS ORDER when it comes to using the cowsay files:

  1. If the COW_PATH environment variable is specified, it will use the cow files specified by the environment variables.
  2. The build script will pull use the fortunes in the archive and internal archive path specified in BuildConfig.toml.

Cow files are stored in a "map" which will support the explicit choice of choosing an embedded cow.

NOTE: using an inline feature will remove command-line/environment variable options to look at an override path for the specific type of thing (i.e. using inline-cowsay will remove the ability to use a COW_PATH environment variable). This is an explicit choice to simplify the binary


Usage

Help is available by running with the --help flag

 $ sh-toy.exe --help
Usage: sh-toy.exe [<message>] [-c <cow-file>] [--cow-path <cow-path>] [-l] [-b <bubble>] [-t <cow-type>] [--max-fort-width <max-fort-width>] [--max-fort-lines <max-fort-lines>] [-o]

various program options

Positional Arguments:
  message

Options:
  -c, --cow-file    path to a direct cowfile OR the name of a cow that exists in
                    the cow path
  --cow-path        path to a folder containing cows that shell-toy should use.
  -l, --list-cows   lists the cows that are embedded in the executable
  -b, --bubble      the type of bubble to create. Options are "think", "round",
                    and "cowsay"
  -t, --cow-type    changes the eyes/tounge of the outputted cow. Values allowed
                    are "default", "borg", "dead", "greedy", "paranoid",
                    "stoned", "tired", "wired", "young". "random" is also an
                    option to choose one of the aforementioned values at random.
                    This only affects cowfiles like the default cowsay cow which
                    use the $eyes and/or $toungue variable
  --max-fort-width  limits the chosen fortunes to be a maximum number of
                    characters per line
  --max-fort-lines  limits the chosen fortunes to contain less than the
                    specified number of lines
  -o, --include-offensive
                    whether to include offensive fortunes
  --help            display usage information

NOTE: Windows/Non-Linux Support

If you are on a Linux Platform which has the cowsay and fortune packages available and installed on the system, shell-toy will automatically pull from the default installation directories. Otherwise, it requires some variables or command line arguments.

  • COWPATH or COW_PATH: Folder containing cowsay cows
  • FORTUNE_FILE: Singular % delimited file for fortunes, prioritized over the PATH counterpart
  • FORTUNEPATH or FORTUNE_PATH: Folder containing fortunes. Offensive fortunes should be placed in a child drirectory called off similar to how fortune does it.

shell-toy is licensed under the MIT License.

By default, the build script for shell-toy uses resources from the following open-source projects. There is no code linkage with these projects, only the resource files are used with certain conditional compilation flags.

This project uses modified portions of code from the following projects (this is documented in the source code where it occurs)

Dependencies

~3–4.5MB
~77K SLoC