opentrep-searcher(1)

πŸ“¦
version 0.08.01 Β· 4 versions
, in epel 10

✨ opentrep-searcher(1) β€” the travel-request parser bestie ✨

okay so this is a page from the General Commands Manual, and the vibe is very much "tiny program, big job." welcome to opentrep-searcher πŸ¦‹


🌸 NAME 🌸

opentrep-searcher β€” a command-line utility that parses travel requests πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

opentrep-searcher [--prefix] [-v|--version] [-h|--help] [-e|--error <
spelling error>] [-d|--xapiandb <Xapian-travel-database-path>]
[-t|--sqldbtype <SQL-database-type>] [-s|--sqldbconx <SQL-database-
connection-string>] [-l|--log <path-to-output-log-file>] [-y|--type
<search-type>] [-q|--query <search-query>]

like, yes, that's a lot of brackets, but she's worth it 🫢


🌈 DESCRIPTION 🌈

opentrep-searcher is a small program that parses a travel request and searches through a Xapian index. lowkey iconic. ✨

opentrep-searcher accepts the following options:


πŸ’– OPTIONS πŸ’–

  • --prefix β€” shows the Opentrep installation prefix. that's it. that's the whole job πŸŽ€
  • -v, --version β€” prints the currently installed version of Opentrep on the standard output. version check slay πŸ’…
  • -h, --help β€” produces that message and shows usage. your friendly little map πŸ—ΊοΈ
  • -e, --error β€” the allowed spelling error distance (e.g., 3). yes bestie, typos are allowed, but only this many πŸ“
  • -d, --xapiandb <Xapian-travel-database-path> β€” path (directory) to the Xapian travel database. The indexer creates, or overwrites it when it already exists, the Xapian database. It materialises as a collection of data files within a directory usually named traveldb. ⚠️ note the word overwrites β€” she is not shy about it 😭
  • -t, --sqldbtype <SQL-database-type> β€” SQL database type, e.g., nosql (no SQL database), sqlite, mysql. pick your fighter πŸ‘‘
  • -s, --sqldbconx <SQL-database-connection-string> β€” SQL database connection string, e.g., ~/tmp/opentrep/sqlite_travel.db (for SQLite3), "db=trep_trep user=trep password=trep" (for MySQL). copy these exactly, they are load-bearing πŸ’€
  • -l, --log <path-to-output-log-file> β€” path (absolute or relative) of the output log file. so she can journal about it later πŸ““
  • -y, --type <search-type> β€” type of search request (0 = full text, 1 = coordinates). two modes, both main character energy 🌟
  • -q, --query <search-query> β€” travel query word list (e.g. sna francicso rio de janero lso anglese reykyavki), which should be located at the end of the command line (otherwise, the other options would be interpreted as part of that travel query word list). 🚨 real talk: this one goes last, fr fr, or the other flags get swallowed into your query 🫠
See the output of the opentrep-searcher --help command for the default options. the defaults live over there, go say hi πŸ’œ

πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, honestly 🌸


πŸ’Œ SUPPORT πŸ’Œ

Please report any bugs to http://github.com/trep/opentrep/issues β€” no gatekeeping, we want the bug reports πŸ›βœ¨


Copyright Β© 2009-2019 Denis Arnaud

See the COPYING file for more information on the (LGPLv2+) license, or directly on Internet: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html


and that's the whole page, bestie πŸŽ€ this was OpenTREP, Version 0.08.01, and yes the program is literally called opentrep-searcher(1) β€” iykyk πŸ’…πŸ¦‹

πŸ“¦ where this page comes from