ulterno

Are we talking about the same Chuck Norris?

No, we are not.

I am talking about an internet meme
You are talking about a real person, who is probably old by now.

Nah, with Chuck Norris, it's usually the missiles that do the dodging.

Making it a sort of a museum would be a pretty good idea.

Are the books really that bad? (Sorry, I mostly lived on NCERT)

's' for serious

But but snarky comments are fun

So now you can't use your voice to convey speech out of class, if you are under 16?
Because Air is a medium which can be used to socialise.

But! But! Wikipedia is not a reliable source! Uwaaan! /s

Docker is not running on client machine.

Did you not know?
You can simply select all files you want to commit, in the File Manager, Ctrl+C, then paste in the terminal and it will automatically add all those file names (full paths) separated with spaces at the cursor. At least in KDE: Dolphin -> zsh + Konsole it does.

And sure, it might look like 2 extra steps, but you will still be clicking around a lot in case of a GUI anyway.

I tend to just type partial filenames and use tab completions, which are also pretty configurable. And the only dissatisfaction I have rn, is that I don't have zsh module for completions with pascal case and snake case.

That's definitely how it is seen.
If I were to see "Discard Changes" anywhere in a dialogue, I would assume it will discard whatever changes I made in that dialogue. In this case, probably some source control related changes. If it were to say "Warning: This will Discard ALL changes!!!", I might do a double take, but had I never used git CLI before, I would still assume that at most it would discard "ALL" changes made in the current session.

For me personally, I would consider it more useful for it to say:

This action will delete the following files:
- followed
- by
- a
- list
- of
- files
- that
- would
- be
- deleted
Continue?

Which neither has to look like a warning, acting like you might be doing something you don't want to and also is much more useful for someone like me who wants to double check what exactly I am deleting.

Also, I have used git CLI before and apart from being able to see blame in the editor itself and maybe a better representation of tree, I don't feel the need to use any git GUI tool. Even when I tried, I realised it was slower and more finicky to use. So, it would stand to reason that it should be targetted towards people who don't use CLI (and might have never used git CLI).

Yes, e.g. I got the 're in blue and everything else light grey.