I'm a bit concerned that with a main.rs and a lib.rs, this package
might accidentally have made both a binary and a library crate,
which (as and when I publish it) might cause people to try to use the
library as if it had a stable and committed API.
In fact all the library modules in this source base are considered
internal to the application, and the interfaces between them are
intended to vary however this application finds convenient. So I
shouldn't accidentally imply otherwise.
+++ /dev/null
-pub mod activity_stack;
-pub mod auth;
-pub mod client;
-pub mod coloured_string;
-pub mod config;
-pub mod editor;
-pub mod file;
-pub mod html;
-pub mod login;
-pub mod menu;
-pub mod options;
-pub mod posting;
-pub mod scan_re;
-pub mod text;
-pub mod top_level_error;
-pub mod tui;
-pub mod types;
use clap::Parser;
use std::process::ExitCode;
-use mastodonochrome::config::ConfigLocation;
-use mastodonochrome::tui::Tui;
-use mastodonochrome::top_level_error::TopLevelError;
+pub mod activity_stack;
+pub mod auth;
+pub mod client;
+pub mod coloured_string;
+pub mod config;
+pub mod editor;
+pub mod file;
+pub mod html;
+pub mod login;
+pub mod menu;
+pub mod options;
+pub mod posting;
+pub mod scan_re;
+pub mod text;
+pub mod top_level_error;
+pub mod tui;
+pub mod types;
+
+use crate::config::ConfigLocation;
+use crate::tui::Tui;
+use crate::top_level_error::TopLevelError;
#[derive(Parser, Debug)]
struct Args {