markdown-lint | Linting for markdown files | Code Analyzer library

by appmattus Kotlin Version: 0.6.0 License: Apache-2.0

X-Ray Key Features Code Snippets(1)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | markdown-lint Summary

markdown-lint is a Kotlin library typically used in Code Quality, Code Analyzer applications. markdown-lint has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Linting for markdown files

Support

Quality

Security

License

Reuse

Support

markdown-lint has a low active ecosystem.

It has 13 star(s) with 3 fork(s). There are no watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 7 have been closed. On average issues are closed in 22 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of markdown-lint is 0.6.0

Quality

markdown-lint has no bugs reported.

Security

markdown-lint has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

markdown-lint is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

markdown-lint releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of markdown-lint

Get all kandi verified functions for this library.

markdown-lint Key Features

No Key Features are available at this moment for markdown-lint.

markdown-lint Examples and Code Snippets

markdown-lint for Gradle projects,Getting started

Kotlin

Lines of Code : 51

License : Permissive (Apache-2.0)

Copy

plugins {
  id("com.appmattus.markdown") version ""
}

./gradlew markdownlint

tasks.named("check") {
    dependsOn(tasks.named("markdownlint"))
}

import com.appmattus.markdown.rules.config.HeaderStyle
import com.appmattus.markdown.rules.ConsistentH

Community Discussions

Trending Discussions on markdown-lint

Coc.nvim how to disable auto complete suggestions in markdown files?

How to see what the red squiggly error marking indicates

QUESTION

Coc.nvim how to disable auto complete suggestions in markdown files?

Asked 2020-Jun-24 at 09:55

I am trying to setup Neovim with Coc for writing markdown. I have Coc working with javascript and other file types.

What I am trying to do is disable the autocomplete suggestions only for markdown files. I have found that if I run :CocDisable that more or less gets the job done but I would like to keep markdown-lint enabled.

Is there a way to disable autocomplete suggestions in Coc only for markdown files?

A picture of the autocomplete suggestions popping up in markdown

...

ANSWER

Answered 2020-Jun-18 at 00:54

You could write something like autocmd FileType markdown :call CocDisable() in your .vimrc

Source https://stackoverflow.com/questions/62435926

QUESTION

How to see what the red squiggly error marking indicates

Asked 2019-Dec-17 at 14:15

I'm editing a markdown file and see a few red squigglies in my document. I have flycheck working with markdown-lint, and ispell doing some other work to detect typos, repeated words, etc. But I can't immediately figure out why certain words are squiggled.

I've discovered that

C-c ! n will take me to the next squiggly flycheck error
C-, will take me to the next flyspell error
M-$ will invoke ispell to help

So I've got everything working that's really needed. But it's a bit annoying that red squigglies represent different things, so I have to use different commands to get to things that look the same, and so it's impossible to tell which binding to use to jump to the next squiggly. And I'd like to know if there's a way, when point is on a squiggled thing, to know why it is squiggled. (I realize flycheck does a good job of showing reasons in minibuffer, but I don't think flyspell/ispell do).

I fear this is going to get worse as I try to add more tooling like WriteGood mode and possibly others.

...

ANSWER

Answered 2019-Dec-17 at 14:15

I don't think there is a simple built-in way of doing it, but here is a little function that tries to tell what the squiggle at point represents:

Source https://stackoverflow.com/questions/59366253

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install markdown-lint

Apply the plugin in your build.gradle.kts script. Further instructions on the plugin page.

Support

Please fork this repository and contribute back using pull requests. All contributions, large or small, major features, bug fixes, additional language translations, unit/integration tests are welcomed.

Find more information at: