It's refreshing to see differences hashed out and solved in a productive manner. Props to both OBS and the Fedora Flatpak team!
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Can someone explain the purpose and perceived value of color coding certain words and phrases? I assume this is some new fad along the lines of "As ______, I want to _______ with ________” in writing user stories and requirements.
I think this has been put in a code block and this Lemmy thinks it is code hence why it is highlighting specific words to make it easier to read if it was actual code.
The OP should have used the Markdown for quote instead of code.
Quote Rendered:
this is a quote
Quote Markdown:
> this is a quote
Multiple Paragraph Quote Rendered:
this is a quote
with multiple paragraphs
Multiple Paragraph Quote Markdown:
>this is a quote
>
>with multiple paragraphs
Inline Code Rendered:
this is an inline code
example
Inline Code Markdown:
this is an `inline code`
example
Code Block Rendered:
this
is a
code
block
Code Block Markdown:
```
this
is a
code
block
```
Text-defined Code Block Rendered:
this
is a
text-defined
code
block
Text-defined Code Block Markdown:
```text
this
is a
text-defined
code
block
```
TIL you can actually specify the language of a code block. I didn't know you could do that, and figured the syntax highlighting was therefore useless.
int foo(int bar, char* baz):
printf("here's some C code in a 'c' code block\n");
return 0;
}
def foo(bar, baz):
print "here's some Python code in a 'python' code block"
I do think it's stupid to have syntax highlighting by default without a language specified, though -- the behavior you label 'text-defined' should be the default. What language is the default highlighting even for, anyway?
That’s a very good question. So good, I didn’t feel right just posting:
code
The original text is formatted as a code block for some reason. Depending on what lemmy front-end (specifically which Markdown renderer) you use, code blocks can be rendered with syntax highlighting as if they were programming language snippets. Check the source of this comment to see the difference:
This code block uses the default syntax highlighting on the Lemmy web front-end. It might look different in other clients.
This code block doesn't use highlighting at all because it is defined as a "text" code block.
What color coding do you mean?
This is what it looks like for me in Voyager:
As several people have already mentioned, it's because when they posted it, they used a code block instead of a quote block, so the client is rendering it like it was source code.
Not certain what you mean by "colour coding certain words and phrases", the gitlabs bullet points translated into "code" in lemmy markdown when I copy pasted the linked comment. I decided that it was good enough and didn't bother editing.
The good thing about code is that it won't linebreak unexpectedly and allow you to format a code snippet correctly when needed.
#Code snippet with four leading spaces
Using Voyager App on Android, it appears that the syntax highlighting defaults to SQL for code blocks without a specified language?
Strange
I don't see anything, I guess the app you're using is doing it