💾 Archived View for gemi.dev › gemini-mailing-list › 001024.gmi captured on 2023-11-04 at 13:16:31. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Hi! I was going to send a long and passionate defence for the inclusion of the horizontal rule (or "The Thematic Break" according to mozilla web docs) when a line started with three hyphens. But on the last paragraph I just realize I had to check the mailing list archive before, and it turns out it had been already proposed, and not only that, but I can't find a counter argument: => https://lists.orbitalfox.eu/archives/gemini/2020/000375.html I'm wondering now: why wasn't it accepted? Was it just forgotten? Thanks for your time! --- Draco Metallium
On Wed, Sep 22, 2021, at 8:58 PM, Draco Metallium(Rodrigo S. Ca?ibano) wrote: > Hi! > > I was going to send a long and passionate defence for the inclusion of > the horizontal rule (or "The Thematic Break" according to mozilla web > docs) when a line started with three hyphens. But on the last > paragraph I just realize I had to check the mailing list archive > before, and it turns out it had been already proposed, and not only > that, but I can't find a counter argument: There's nothing to stop you from using three hyphens on a line to suggest a horizontal rule/thematic break. It's just not in the Gemini spec so whether or not a client supports it depends entirely on the client's developer. Likewise with asterisks for Markdown-style italics and bold, but a line that begins with an asterisk will still be rendered as an item in an unordered list even if there's a terminating asterisk in that line, because using * for unordered lists /is/ in the spec. -- Matthew Graybosch https://starbreaker.org "The lies you tell yourself are the lies that define you." #include <disclaimer.h>
Heading aren't sufficient to make thematic break? ??????? Original Message ??????? On Thursday, September 23rd, 2021 at 02:58, Draco Metallium <draco.kun at gmail.com> wrote: > Hi! > > I was going to send a long and passionate defence for the inclusion of > > the horizontal rule (or "The Thematic Break" according to mozilla web > > docs) when a line started with three hyphens. But on the last > > paragraph I just realize I had to check the mailing list archive > > before, and it turns out it had been already proposed, and not only > > that, but I can't find a counter argument: > > => https://lists.orbitalfox.eu/archives/gemini/2020/000375.html > > I'm wondering now: why wasn't it accepted? Was it just forgotten? > > Thanks for your time! > ------------------------------------------------------------------------- ----------------- > > Draco Metallium
Draco Metallium(Rodrigo S. Ca?ibano) <draco.kun at gmail.com> writes: > Hi! > > I was going to send a long and passionate defence for the inclusion of > the horizontal rule (or "The Thematic Break" according to mozilla web > docs) when a line started with three hyphens. But on the last > paragraph I just realize I had to check the mailing list archive > before, and it turns out it had been already proposed, and not only > that, but I can't find a counter argument: > > => https://lists.orbitalfox.eu/archives/gemini/2020/000375.html > > I'm wondering now: why wasn't it accepted? Was it just forgotten? > > Thanks for your time! > --- > Draco Metallium I can agree that having a horizontal rule would be nice. On the geminispace there are pages that uses either ---- or ``` --- ``` which I personally dislike. Some time ago I experimented with this a little. The proposal/break-page branch of telescope has some code which renders ^L (form feed, used to separate "pages") with a nice separator. (I went with ^L to avoid false positive with lines starting with `---' or similar) But then I left that branch rotting. I guess that part of the reason something like this wasn't included before is because of the saying "perfection is when you can't remove anything" (or something similar, but the gist is that.) Horizontal rule can be avoided by properly using paragraphs and headings in most cases. Cheers, Omar Polo
Hi Omar, I recognised the use of the form feed ^L (ASCII 12) from Emacs. I was wondering about that too. I checked the perspective from Xah Lee, who has evaluated its applicability: => http://ergoemacs.org/emacs/modernization_formfeed.html He highlights technical limitations of form feed's reliance on ^L: ``` # Cygwin Bash Cygwin Bash will generate this error if your shell script contains the Form Feed char that's not in comment. bash: