Lots of output at terminal
See original GitHub issueIf I just enter faker
at the terminal and hit enter, is it supposed to produce nearly 50mb of output? The text flew by so fast, I piped it into a text file, and it was something like 46mb of text. I’m fairly confident this isn’t intended, but I obviously can’t say for sure, since I’m not the one who wrote it. If this isn’t intended, I can provide more details.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
How to produce constant output in a Terminal window?
This will usually generate a lot of output on the console. You could also generate huge directory listings $ ls -lRt. or find...
Read more >How to get and copy a too long output completely in terminal?
In Gnome-Terminal and Konsole I have this problem. In xterm there's not such problem but I cannot copy the output in xterm. How...
Read more >See Everything In The Terminal/Command Prompt After Long ...
Everytime I run this command it outputs like 600 lines of data that I need to analyze. But when I try to scroll...
Read more >How can I see more output lines in terminal? - Super User
If I give a command that has a lot of output lines in terminal, about 400, I can only see the last ~200...
Read more >There are lots of extra spaces in terminal output (caused by ...
Since pure uses a newline in it's pre-prompt this is a non-issue and the spaces are a nuisance when copying text from the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m sorta fairly knowledgeable with argparse, if you’d like me to see what I can do. But in the meantime, I think just displaying the normal argparse error would be the best solution for now, and then maybe relocating this text to a “example” subcommand, which could possibly write it to a file? At least until it gets explored more in depth. Or I can just report back with a more elaborate proposal?
I’ll still explore it, see what it looks like.
I think a simple message like this would be sufficient:
i.e. the same output you get when running e.g.
grep
without arguments.