feat: Remove command line option --no-xinclude

[kesara]

Command line option --no-xinclude has no effect since the move to xml2rfc from rfctools-common.

[larseggert]

This breaks @martinthomson's i-d-template, because that uses -X. Please coordinate such changes more widely? (Or alternatively, keep removed options but make them no-ops?)

[larseggert]

It would be good to add some test cases, one of which should be the rendering of an I-D with i-d-template.

[martinthomson]

It's @cabo's kramdown-rfc that uses -X, I believe.

https://github.com/cabo/kramdown-rfc/blob/d8b1aa56200b0763321ecbbbaebd28f631df41f6/lib/kramdown-rfc2629.rb#L563

[cabo]

keep removed options but make them no-ops?)

This.

[kesara]

I have a PR reintroduce this with a warning because it's no-ops: #35
The warning message will be suppressed for kramdow-rfc users because it already uses --quiet option.

[cabo]

Ping?

[rjsparks]

This is done and released isn't it?
https://github.com/ietf-tools/svgcheck/releases/tag/v0.7.1

[cabo]

Well, svgcheck still fails, but this seems to be because it can't read from stdin.

[cabo]

kramdown-rfc 1.6.24 now working around the stdin issue.

[cabo]

Apologies for thinking we hadn't fixed this yet -- the new regression was reported to me on the same github issue the X was on. I still think that tools like this shouldn't change their CLI willy-nilly, neither losing an option (and then erroring out on it), nor losing the ability to read stdin.
But there is no need for action on the latter now (from a kramdown-rfc perspective), which is why I won't raise an issue.

[kesara]

Sorry, It was an unintentional mistake to remove STDIN functionality.
I have created #36 to restore that.
Since kramdown-rfc has moved on I think it's a lesser priority issue now.