You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was curious why this tool did not sensibly pad output, at least for the help command, rather than terminating abruptly without anything separating it from the terminal below.
It was then that I fell down the rabbit hole of #741, #832, #853, and related issues...
[REDACTED]
Note: @shadowspawn edited this comment to remove content that was unacceptable.
The text was updated successfully, but these errors were encountered:
This comment is unacceptable. You may disagree with an opinion or a decision, but you may not attack a person.
Cool down. I suggest you edit your post to remove the angry and unfounded comments, or the unsuccessful attempt at humorous hyperbole. (Update: I edited comment.) I recommend you post an apology.
There was discussion on whitespace in the help with useful research and comments and contributions by @mojavelinux and others. The maintainers of this project at the time accepted the changes proposed.
If you wish to propose changes, make your case in a more civil manner.
Thank-you for your contributions to this project @mojavelinux
shadowspawn
changed the title
Proposal: Readd whitespace to output, do the opposite of whatever @mojavelinux says
Proposal: Readd whitespace to output
Nov 8, 2022
I was curious why this tool did not sensibly pad output, at least for the help command, rather than terminating abruptly without anything separating it from the terminal below.
It was then that I fell down the rabbit hole of #741, #832, #853, and related issues...
[REDACTED]
Note: @shadowspawn edited this comment to remove content that was unacceptable.
The text was updated successfully, but these errors were encountered: