define
define copied to clipboard
Rican7
A command-line dictionary (thesaurus) app, with access to multiple sources, written in Go.
Currently, **define** uses all remote (online) sources. A local, expandable dictionary is available on macOS, which would be a great source if it was accessible. Unfortunately, it seems that the...
Currently getting (for any input) ```cmd > define Oxford The source returned an empty result for word: "Oxford" > define --print-config { "IndentationSize": 2, "MerriamWebsterDictionary": { "AppKey": "" }, "OxfordDictionary":...
Oxford Dictionaries is moving to v2 of their API and shutting down the v1 endpoints on 30 June 2019. Reference: https://developer.oxforddictionaries.com/version2
If using Merriam Webster only, the default source will be Oxford, requiring a command line argument or config file to set the preferred source to Merriam Webster. Can support be...
The `define` app would benefit from documentation beyond the simple `--help` flag output, especially with some of its configuration. To keep with typical standards and expectations, the `define` app/command should...
## Feature request Colorized output. ### Why Colourized output would make skimming definitions easier. ### Problem A word that returns many results can produce a "wall of text" output which...
When trying to define a word, running into a invalid respond error. ``` ➜ ~ define invalid The source returned an invalid response ```
There exists a standard protocol for accessing remote dictionary services. While it's quite old in design, it was purposefully designed for clients/applications such as **define**. A generic DICT protocol "source"/provider...