LEECHCRAFT(1)

πŸ“¦ version 0.6.70+git.17739.g0d7a960ef4, in opensuse-leap 16.0

πŸ’– LEECHCRAFT(1) β€” the leechcraft manual page, bestie edition πŸ¦‹

okay so. hi. welcome to the General Commands Manual entry for LeechCraft, and honestly? she's a whole vibe. buckle up πŸŽ€


✨ NAME ✨

LeechCraft β€” an extensible, modular internet-client. that's the whole pitch and honestly it ate πŸ’…


🌸 SYNOPSIS 🌸

leechcraft-qt6 [options] [entity]

πŸ¦‹ DESCRIPTION πŸ¦‹

so LeechCraft is an extensible, cross-platform, modular internet-client ✨ and "modular" here literally means it's plugin-based β€” every single task is handled by its own separate plugin. like, one job, one plugin, main character energy for each of them πŸ‘‘

right now the plugin lineup includes (but is not limited to, periodt) the following:

  • Aggregator β€” an RSS/Atom feed reader πŸ“°
  • Azoth β€” a multiprotocol IM client, currently supporting XMPP/IRC and lots of other stuff πŸ’¬
  • BitTorrent β€” well… a BitTorrent client πŸ΄β€β˜ οΈ
  • LackMan β€” a userspace package manager for easy installation of iconsets, emoticons, themes, scripting plugins and other similar things πŸ“¦
  • LMP β€” a feature-rich collection-oriented audio player 🎧
  • Monocle β€” a modular document viewer πŸ“„
  • Poshuku β€” a WebKit-based web browser 🌐

πŸ’… OPTIONS πŸ’…

πŸŽ€ Common Qt Options

  • -style style, -style=style β€” tells Qt which widget style to use. examples given: plastique, cleanlooks. pick your aesthetic bestie πŸ’–
  • -stylesheet stylesheet, -stylesheet=stylesheet β€” sets the user stylesheet to use when rendering widgets. yes you can dress her up ✨
  • -reverse β€” flips the application's layout direction to right-to-left. mirror mirror πŸͺž

πŸ”₯ Options Specific to LeechCraft

  • entity β€” the entity for LeechCraft to handle. this could be, like, a torrent file name or an URL. no cap 🧚
  • -v [ --version ] β€” prints the LeechCraft version and dips. exit stage left πŸšͺ
  • --automatic β€” says "don't consider this entity to be added as a result of user's action." this way LeechCraft tries to minimize the number of dialogs with the user. suitable for adding entities from cron or some other sources, where the user could be AFK 😴
lowkey this only makes sense if an entity has been specified. fr fr.
  • -H [ --handle ] β€” the item must be handled, not downloaded. useful when setting LeechCraft as your default browser: this way it won't ask if the item should be opened in Poshuku or downloaded πŸ™…β€β™€οΈ
again β€” only makes sense if an entity has been specified.
  • -D [ --download ] β€” the item must be downloaded only, not handled. this is similar to the -H option, but does the reverse πŸ”„
once more for the people in the back: only makes sense if an entity has been specified.
  • -T [ --type ] arg β€” defines the type of the passed entity. it could be one of:
    • url β€” for URLs that come from user input πŸ”—
    • url_encoded β€” for percent-encoded URLs πŸ”‘
    • file β€” for local file paths πŸ“

by default, url is assumed. and yup β€” this only makes sense if an entity has been specified πŸ’«

  • -P [ --plugin ] path β€” ⚠️ use this option only if you know what you are doing. seriously.

loads only a plugin from the given path. specifying this option effectively disables loading plugins from standard places, so only the given plugin would be loaded. moreover, the given plugin's dependencies aren't evaluated, so you should load them by hand, specifying multiple -P options 🫢

and like β€” as already said β€” multiple -P options can be specified, resulting in multiple plugins being loaded.

also: if this option is specified, LeechCraft doesn't check if it's already running, it just starts up and loads the given plugin(s). so be careful with this option: you could either end up with lots of LeechCraft instances running, or have your data corrupt if the specified plugin doesn't support sharing data between multiple running instances. that's not a vibe πŸ’€
  • --nolog β€” disables the custom logger that writes logs to ~/.leechcraft/{debug,warning,critical}.log and prints everything to stdout/stderr instead πŸ—’οΈ
  • --bt β€” prints a backtrace along with warning-level log entries. helps trace where the warning entries come from πŸ”
  • --clrsckt β€” clears the stalled local socket. useful when LeechCraft doesn't start up and you know that no other instances are running 🧹
  • --no-app-catch β€” disables catching all the exceptions in QApplication::notify(). useful for debugging purposes only and shouldn't be used for live setups πŸ™ˆ
  • --autorestart β€” automatically restarts if closed. this is done via Session Manager, so it won't work everywhere πŸŒ€
  • --help β€” prints a short help message. classic 🫑

🌈 FILES 🌈

LeechCraft stores user-specific stuff in two places:

  • ~/.config/Deviant β€” for settings βš™οΈ
  • ~/.leechcraft β€” for more "heavy" data, like RSS reader databases πŸ—ƒοΈ

the XDG spec is not followed for the latter, and the reason is, and i quote, "for hysterical raisins" πŸ‡ (iconic honestly).

caches are stored in $XDG_CACHE_HOME/Deviant/leechcraft πŸ’Ύ

plug-ins are loaded from:

  • /usr/local/lib/leechcraft-qt6/plugins
  • /usr/lib/leechcraft-qt6/plugins

πŸ’€ BUGS πŸ’€

there are many of them. 😭 please report bugs to https://dev.leechcraft.org/projects/leechcraft/issues or via the Dolozhu plugin right from LeechCraft πŸ›


πŸ‘‘ AUTHOR πŸ‘‘

the authors of LeechCraft are listed in its About dialog, as well as on this web page: https://leechcraft.org/our-team 🫢

this manual page was written by Georg Rudoy <0xd34df00d@gmail.com>.

permission is granted to copy, distribute and/or modify this document under the terms of the Boost Software License, Version 1.0. Boost Software License - Version 1.0 - August 17th, 2003 πŸ“œ

on Debian systems, the complete text of the Boost Software License can be found in /usr/share/common-licenses/BSL.


and that's the whole page bestie πŸ’œ this manual page is from Apr 2013, and the source/version on the footer is LEECHCRAFT(1) β€” General Commands Manual. go forth and modularize βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from