<!-- more -->
should work too. Also
<!--
more
-->
<!-- more -->
should work too. Also
<!--
more
-->
I, too, would like this. Iāve had some issues with slightly malformed more
; I believe normal HTML is a little flexible, too?
For sure. It is sad it is not supported from the beginning. I had spent a few hours in the past because of this.
Maybe you could look for a similar issue on GitHub with your feature request. Thatās the usual way to place an idea into the long pipeline of development issues. If you canāt find it there, you could start one yourself.
@Georg I did that when I first got involved with Hugo, but was asked by the maintainers to start by posting here. GitHub issues are for approved things. I did search GH issues for a similar idea.
Edit: Word
There are a few objectives behind this encouragementā¦
1) To prevent people from logging ābugsā when they donāt understand something or havenāt read the documentation.
2) To prevent people from logging ābugsā where the problem/behavior is poorly defined. āFeature xxx doesnāt work.ā is not a bug; itās the beginning of a conversation, and that should occur (for the most part) hereātroubleshooting.
3) To prevent people from creating proposals for features/capabilities that already exist.
4) To prevent people from creating proposals for features/capabilities that are poorly defined.
Something like <!--more-->
vs. <!-- more -->
doesnāt fall into any of these categories, so you should create a proposal on GitHub.
For the record, Iāve made the <!-- more -->
mistake myself a couple of times.
FYI ā this is not a trivial change.