-
Notifications
You must be signed in to change notification settings - Fork 169
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issues in Markdown doc files #1333
Comments
Enable commands-show-output from markdownlint globally, and disable it for the problematic code blocks in r.fuzzy.system. See also OSGeo#1333 and OSGeo#1334.
Missing here:
|
Vaclav, what kinds of changes are needed for r.landscape.evol markdown to
come into compliance? I can do this with a little guidance if necessary.
~Isaac
|
I am not sure either, it is compliant with with setting in the markdown linter. So maybe some of the subheadings could be more semantically correct, e.g. you could remove the numbering from the subheadings and then things like "a) GIS Implementation:" could be "#### GIS Implementation" |
Ok, thanks Anna! I will make some time to work on this...
~Isaac
…On Wed, Mar 12, 2025 at 7:04 AM Anna Petrasova ***@***.***> wrote:
Vaclav, what kinds of changes are needed for r.landscape.evol markdown to
come into compliance? I can do this with a little guidance if necessary.
~Isaac
I am not sure either, it is compliant with with setting in the markdown
linter. So maybe some of the subheadings could be more semantically
correct, e.g. you could remove the numbering from the subheadings and then
things like "a) GIS Implementation:" could be "#### GIS Implementation"
—
Reply to this email directly, view it on GitHub
<#1333 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACDYS5DLJ5KBWO7CMZMVPP32UA5GXAVCNFSM6AAAAABXRQRQ2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJXHE4TGOJQGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: petrasovaa]*petrasovaa* left a comment (OSGeo/grass-addons#1333)
<#1333 (comment)>
Vaclav, what kinds of changes are needed for r.landscape.evol markdown to
come into compliance? I can do this with a little guidance if necessary.
~Isaac
I am not sure either, it is compliant with with setting in the markdown
linter. So maybe some of the subheadings could be more semantically
correct, e.g. you could remove the numbering from the subheadings and then
things like "a) GIS Implementation:" could be "#### GIS Implementation"
—
Reply to this email directly, view it on GitHub
<#1333 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACDYS5DLJ5KBWO7CMZMVPP32UA5GXAVCNFSM6AAAAABXRQRQ2SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMJXHE4TGOJQGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
___________________________________________________________________________
Isaac I. Ullah, PhD
*Recent papers:*
Laborscapes and Archaeologies of Sustainability:
http://dx.doi.org/10.1558/jma.39327
Water, dust, and loess: co-evolution of landscapes, farming, and human
society: https://doi.org/10.1016/j.jaa.2019.101067
Modeling feedbacks between human and natural processes in the land system:
https://doi.org/10.5194/esd-9-895-2018
<https://doi.org/10.5194/esd-9-895-2018>
<https://doi.org/10.5194/esd-9-895-2018>
|
Enable commands-show-output from markdownlint globally, and disable it for the problematic code blocks in r.fuzzy.system. See also OSGeo#1333 and OSGeo#1334.
@isaacullah I removed the r.landscape.evol issue from here and moved it to a separate issue. I'm closing this as completed as all individual todos are now completed. |
Essential:
Transition-related:
Optional:
$
sign in a Bash example). Replaced by local disable checks: Enable markdownlint commands-show-output #1356.Originally listed here, but later identified as out of scope:
The text was updated successfully, but these errors were encountered: