Repository navigation
suggestion: --force-(component) to force component displaying #32
Description
Activity
But how should you handle it if the terminal isnt big enough to show the component?
based on terminal size.
There are three different layouts
gitfetch/src/gitfetch/display.py
Line 197 in ac109ff
based on the terminals height and width I try to guess best option - however its not always great.
I will be creating docs regarding the auto layout, its limitations and hardcoded values.
I really like the auto layouting however some edge cases are annoying (that's why --no- and --force- are helpful)but if you --force-(insert every component here) and the terminal is too small what will happen?
overflow, however it give you ability to force when it thinks there is an overflow but actually there is space.
--force and --no of course cannot be called together on the same component
Reacted by Zevvi
same way that --no-(component) force hides, --force-(component) should force render.
I think these two working together can give lots of power to the user - especially when there is automatic layouting based on terminal size.