|
2 | 2 | //! |
3 | 3 | //! This module provides two main functions:- |
4 | 4 | //! * The [`init_core`] function which is responsible for setting the initial state of the |
5 | | -//! Pager, do environment checks and initializing various core functions on either async |
6 | | -//! tasks or native threads depending on the feature set |
| 5 | +//! Pager, do environment checks and initializing various core functions on either async |
| 6 | +//! tasks or native threads depending on the feature set |
7 | 7 | //! |
8 | 8 | //! * The [`start_reactor`] function displays the displays the output and also polls |
9 | | -//! the [`Receiver`] held inside the [`Pager`] for events. Whenever a event is |
10 | | -//! detected, it reacts to it accordingly. |
| 9 | +//! the [`Receiver`] held inside the [`Pager`] for events. Whenever a event is |
| 10 | +//! detected, it reacts to it accordingly. |
11 | 11 | #[cfg(feature = "static_output")] |
12 | 12 | use crate::minus_core::utils::display; |
13 | 13 | use crate::{ |
@@ -52,21 +52,21 @@ use super::{utils::display::draw_for_change, CommandQueue, RUNMODE}; |
52 | 52 | /// |
53 | 53 | /// Then it checks if the minus is running in static mode and does some checks:- |
54 | 54 | /// * If standard output is not a terminal screen, that is if it is a file or block |
55 | | -/// device, minus will write all the data at once to the stdout and quit |
| 55 | +/// device, minus will write all the data at once to the stdout and quit |
56 | 56 | /// |
57 | 57 | /// * If the size of the data is less than the available number of rows in the terminal |
58 | | -/// then it displays everything on the main stdout screen at once and quits. This |
59 | | -/// behaviour can be turned off if [`Pager::set_run_no_overflow(true)`] is called |
60 | | -/// by the main application |
| 58 | +/// then it displays everything on the main stdout screen at once and quits. This |
| 59 | +/// behaviour can be turned off if [`Pager::set_run_no_overflow(true)`] is called |
| 60 | +/// by the main application |
61 | 61 | // Sorry... this behaviour would have been cool to have in async mode, just think about it!!! Many |
62 | 62 | // implementations were proposed but none were perfect |
63 | 63 | // It is because implementing this especially with line wrapping and terminal scrolling |
64 | 64 | // is a a nightmare because terminals are really naughty and more when you have to fight with it |
65 | 65 | // using your library... your only weapon |
66 | 66 | // So we just don't take any more proposals about this. It is really frustating to |
67 | 67 | // to thoroughly test each implementation and fix out all rough edges around it |
68 | | -/// Next it initializes the runtime and calls [`start_reactor`] and a [`event reader`]` which is |
69 | | -/// selected based on the enabled feature set:- |
| 68 | +/// Next it initializes the runtime and calls [`start_reactor`] and a [`event reader`]` which is |
| 69 | +/// selected based on the enabled feature set:- |
70 | 70 | /// |
71 | 71 | /// # Errors |
72 | 72 | /// |
|
0 commit comments