Matthias Endler

Ah, you got it. Thanks for the explanation. Yes, SPAs will be tricky for now. We might not be able to check these. Let's start with the simple use-case of...

Perfect. Great analysis! Maybe you want to start a new crate (anchorfy?) which allows you to create the fragment from different flavors? ```rust assert_eq!(anchorfy::Github("## Many spaces"), "many----------spaces".to_string()); assert_eq!(anchorfy::Gitlab("## Many spaces"),...

I'd assume >90% of all Markdown files we check are on GitHub. If we make it configurable, we should keep it simple. Maybe we just introduce a `--fragment-format` option at...

Sorry, I don't quite get it. If we find a fragment link in a document, we have to check if that fragment exists. Say we find "#helloworld" and there is...

Ah, I understand now. Not sure how to find the right balance between simplicity and flexibility here. Open for suggestions for the configuration format.

https://github.com/lycheeverse/lychee/pull/987 fixes `--max-redirects` behavior. For example ``` echo 'https://httpstat.us/301' | lychee --max-redirects 0 - ``` fails now as expected (with a build from `master`, not with a released version yet)....

@tooomm, I assume this is fixed now and the fix got released with lychee 0.12.0. If this is not the case, feel free to reopen.

I am thinking about disabling `email-check` by default. Email addresses lead to a lot of false positives at the moment (see https://github.com/lycheeverse/lychee/issues/1111). If people need the feature, they would have...

Sweet. I've [added some more examples](https://lychee.cli.rs/#/recipes/excluding-paths) to the docs to help you get started. Feel free to add a comment here if you run into an issue.

Are you mixing up regex with glob, maybe? Instead of `models*`, can you try `models.*`?