# Define Headings endings

**URL:** <https://talk.commonmark.org/t/define-headings-endings/4698>\
**Category:** Spec\
**Created:** [July 9, 2024, 11:24pm UTC](https://talk.commonmark.org/t/define-headings-endings/4698 "2024-07-09T23:24:10Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Crissov](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/crissov/32/1455_2.png) [@Crissov](https://talk.commonmark.org/u/Crissov)\
**Post date:** [July 10, 2024, 4:48pm UTC](https://talk.commonmark.org/t/define-headings-endings/4698/3 "2024-07-10T16:48:36Z")

</div>

My latest conclusion was this:

> [@Horizontal rules as (hierarchical) section breaks etc](https://talk.commonmark.org/t/horizontal-rules-as-hierarchical-section-breaks-etc/1241/3):
>
> - `----`: empty heading `section` break – continue in new anonymous sibling section
> - ` **** `: structural `section` break – continue in parent section afterwards
> - ` ____ `: visual `hr` break

I don’t know if anyone ever wrote an extension for a CM parser to implement this. I doubt it would ever be included as part of the core syntax.

---

_[View the full topic](https://talk.commonmark.org/t/define-headings-endings/4698)._