Welcome to GRASS Discussions!

[NikosAlexandris]

👋 Hello! 💚

📢 Following on #1826, GitHub Discussions is put on trial as a place to connect with other members of the GRASS community. You are welcome to share the Discussions link 🔗.

Discussions is not a replacement for but an addition to the forums for developers and users, but it provides an additional way to ask questions and discuss right on GitHub.

---

You are warmly welcome to

• Ask questions ☝️

  There is no such thing as a dumb question.

  — Carl Sagan

• Share your curious ideas 🤔 💡

  Be less curious about people and more curious about ideas.

  — Marie Curie

• Engage with other members 🤝 💚

---

Remember,

• Submit bug reports and/or feature requests at https://github.com/OSGeo/grass/issues 🐛

• We Are The Community 👐

  We are respectful toward others in accordance with our Code of Conduct.

---

Feel free to introduce yourself and share what you do with GRASS 💚

[NikosAlexandris]

Great start in the Discussions section in the last 3 days!

I would like to remind all of us (@CarlosGrohmann @veroandreo @YannChemin), though it is by no means a must, that we can make our posts more readable with simple Markdown syntax (please see www.markdownguide.org) or simply using the basic text formatting buttons available in the header of the text editing box.

For example, enclosing a filename or a module name in backticks ` is easy and will make it easier to read through a message (e.e. i.landsat.import).
Thank you, Nikos

ps- I am yet to try sending a normal e-mail with Markdown syntax as a reply/comment in a Discussion and see whether the syntax is considered or not.

[wenzeslaus]

About the names and backticks, it is also a common paractice to make names emphasized/cursive and use backticks for pieces of code as in "note usage of ls in ls -la".

[CarlosGrohmann]

@ZenithFlux, wouldn't this be a new discussion topic? I feel it won't get the necessary attention here, as a reply to Nikos post

[NikosAlexandris]

(If I could, I would remove this post, as there is already one in the corresponding issue. Please @ZenithFlux consider removing it.)

[NikosAlexandris]

Thank you @ZenithFlux