Kind of tools I wish I had a use case for.
TTE: Terminal Text Effects
31–40 of 279 posts
Re: TTE: Terminal Text Effects
#32Re: TTE: Terminal Text Effects
#33Earlier quoted context omitted.
Why not?
Imagine that the CLI tool you use most often every day - a compiler, a package manager, like that - adds animations like these in common operations. Now you have to wait for the animation to finish before you can continue your work. How do you feel about that?
Also, I don't want to even imagine how it would look on a SSH connection.
Re: TTE: Terminal Text Effects
#34I'm glad to see we all take the same approach to these sorts of things ^_^ self.move_cursor_to_top() sys.stdout.write(output_string) sys.stdout.flush()
Would there be a more canonical way do do this?
Re: TTE: Terminal Text Effects
#35This is amazing! Please never ever use it in production.
I was thinking about how fun it would be to add this my Python CLI [0] I made for launching Fedora CoreOS locally with QEMU for testing ignition, but with a flag that is turned off by default. Using the burn effect in TTE when launching a VM with my CLI would be so cool.
This instantly reminded me about Ansible and how it annoyed me that ANSIBLE_NOCOWS had to be enabled to disable the default output of Ansible with cowsay [1].
Re: TTE: Terminal Text Effects
#36This is amazing! Please never ever use it in production.
Idk I wouldn’t mind one or two of these as loading screens or something.
What CLI tools have a slow enough boot to require a loading screen? I'm sure there are some but...
The only one that comes to mine for me is FileBot[0] - and if the loading screen made it take ANY additional time, I'd be annoyed.
Re: TTE: Terminal Text Effects
#37Re: TTE: Terminal Text Effects
#38Re: TTE: Terminal Text Effects
#39This is amazing! Please never ever use it in production.
Please use this to reboot Trade Wars 2002.
Re: TTE: Terminal Text Effects
#40There's a bit of lag on my VT420.