-
I'm using What I'm seeing
Here is an email address to autolink: tituswormer@example.com $ remark -u gfm input.md -o output.md
input.md > output.md: written
$ cat output.md
Here is an email address to autolink: <tituswormer@example.com>
$ remark -u preset-lint-recommended input.md
Here is an email address to autolink: tituswormer@example.com
input.md: no issues found
$ remark -u preset-lint-recommended output.md
Here is an email address to autolink: <tituswormer@example.com>
output.md
1:39-1:64 warning All automatic links must start with a protocol no-auto-link-without-protocol remark-lint
⚠ 1 warning
$ What I want to happen insteadI would like for
What I could do to make this happenThese seem like things that will work, but are (to me, at least) not as ideal as what is suggested in the previous section.
One thing that's puzzling me
This needs a mailto protocol: <tituswormer@example.com> $ remark -u lint-no-auto-link-without-protocol input.md -o output.md
input.md > output.md
1:31-1:56 warning All automatic links must start with a protocol no-auto-link-without-protocol remark-lint
⚠ 1 warning
$ cat output.md
This needs a mailto protocol: <tituswormer@example.com>
$ Maybe I need to pass a setting with |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
I believe historically there was a lot of difference between how “pedantic” markdown (Gruber-style), old GFM (from before CM), and CM, parsed these. a@b.c
<a@b.c>
<mailto:a@b.c>
[a@b.c](mailto:a@b.c) |
Beta Was this translation helpful? Give feedback.
I believe historically there was a lot of difference between how “pedantic” markdown (Gruber-style), old GFM (from before CM), and CM, parsed these.
I think the lint rule being weird is a remnant of that, which can be revisited:
a@b.c
a@b.c
mailto:a@b.c
a@b.c