Dull Men's Club
An unofficial chapter of the popular Dull Men's Club.
1. Relevant commentary on your own dull life. Posts should be about your own dull, lived experience. This is our most important rule. Direct questions, random thoughts, comment baiting, advice seeking, many uses of "discuss" rarely comply with this rule.
2. Original, Fresh, Meaningful Content.
3. Avoid repetitive topics.
4. This is not a search engine
Use a search engine, a tradesperson, Reddit, friends, a specialist Facebook group, apps, Wikipedia, an AI chat, a reverse image search etc. to answer simple questions or identify objects. Also see rule 1, “comment baiting”.
There are a number of content specific communities with subject matter experts who can help you.
Some other communities to consider before posting:
5. Keep it dull. If it puts us to sleep, it’s on the right track. Examples of likely not dull: jokes, gross stuff (including toes), politics, religion, royalty, illness or injury, killing things for fun, or promotional content. Feel free to post these elsewhere.
6. No hate speech, sexism, or bullying No sexism, hate speech, degrading or excessively foul language, or other harmful language. No othering or dehumanizing of anyone or negativity towards any gender identity.
7. Proofread before posting. Use good grammar and punctuation. Avoid useless phrases. Some examples: - starting a post with "So" - starting a post with pointless phrases, like "I hope this is allowed" or “this is my first post” Only share good quality, cropped images. Do not share screenshots of images; share the original image.
.
view the rest of the comments
I have worked on projects that get run through automatic formatting when committed to repos
Perhaps you need something like that and you can auto format the way you want on the way out
Git has post-checkout and pre-commit hooks that can easily do this.
Means your local copy is in your style, but you commit in the repo style.
Insane thing to do, but nobody's stopping you...
Or people could do the logical thing and just use tabs.
edit: remove extra space.
My text editor will use spaces if it is in the liter file or how it auto detects in yaml files etc
The experience is no different when using tab / shift+tab
The experience of entering the text isn't the part to which I object.
Claiming that spaces as indentation are functionally equivalent to tabs is what inspires my objection.
I don’t think you gave an example in your original post as how tabs would have solved your problem, and dealing with yaml a lot myself I can’t imagine exactly what may have happened besides incorrect indentation
I get rich errors with yaml language server and I configure it with spec files for kubernetes manifests so it tells me exactly where my issues are
Automatic code formatting, and failing a PR due to an automatic formatter is lazy and wrong. Code formatting should be a (strong) set of guidelines, but never a hard and fast rule. Every code base ends up with some section that is visually easier to understand but breaks the formatting check.