Support whitespace in <!--more-->

feature
1

<!-- more --> should work too. Also

<!--
more
-->
4 Likes
2

I, too, would like this. Iā€™ve had some issues with slightly malformed more; I believe normal HTML is a little flexible, too?

2 Likes
3

For sure. It is sad it is not supported from the beginning. I had spent a few hours in the past because of this.

1 Like
4

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.

5

@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

6

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.

2 Likes
7

Created Support whitespace in <!--more--> Ā· Issue #10708 Ā· gohugoio/hugo Ā· GitHub.

1 Like
8

FYI ā€“ this is not a trivial change.