ainsleymcgrath / epoch-echo

A salve for timesmiths 🧴🕰️

epoch-echo

A minimal command line alternative to tools like this.

Copypasta your machine-flavored datetimes from the db or whatever into the ee and ahhhh 😌 a nice human date right there for you in 0 clicks 🌚. Pass a whole long list of some ridiculous mixture of epoch timestamps and readable datetimes and witness 🙀 the grand switcharoo 🎠

Built with ✨and typer.

About

Born from the grumblings of a crunchy shell-dweller, ee-cli is designed to fit nicely in a terminal-heavy workflow with tools like tmux, hub, fzf, etc. Those tools and their peers inspired ee greatly.

ee stands for "epoch echo" because that's sort of what the tool does.

ee takes any arbitrary combination of epoch timestamps, datetimes, times, dates, etc, and prints them back as the opposite. ee uses pendulum for these conversions.

By default, ee supports input from the same datetime formats as pendulum.parse, plus the conveniences of "now," "tomorrow," "today," and "yeterday."

More input formats can be used by setting the EXTRA_DATETIME_INPUT_FORMATS environment variable to a json array of these tokens in pendulum

Installation

This is a Python project, so you install it from pip.

pip install ee-cli

The executable is ee

ee  # display help and list commands

Usage

Basic: Convert a list of datetimes, output it to the clipboard.

Interactive: Use the repl to curate a list of converted datetimes, view help, send to clipboard, and more!

Images generated with termtosvg.

See USAGE.md for more.

epoch-echo's Issues

support for millisecond epochs

when parsing epochs with millisecond resolutions, I get a couldn't parse error. not sure how hard it would be to handle both. I noticed in the code there are explicit references to removing milliseconds from epochs. is there a philosophical reason for not supporting this or can I submit a PR that parses them?