freenode/#shirakumo - IRC Chatlog
Search
15:55:30
mood
Hmm, what seems logical: If it's always, it becomes a paragraph; if it's unescaped, it's part of the header; if it's escaped, it becomes a paragraph
15:56:31
mood
Or maybe a header can contain a newline, in which case it should maybe not ever become a paragraph? I'm not 100% sure how Markless handles this anymore
15:58:12
Shinmera
It seems to me so far that line continuing and newlining are two orthogonal things
15:58:35
Shinmera
So if you wanted to control both there would have to be control structures for both
16:06:00
gingerale
To me ## a\<RET>b would return a header that is in two lines, first a and second b.
16:08:17
Shinmera
What you seem to be suggesting is that line-mode is fixed to always and continuing is on.
16:18:06
Shinmera
Remember kids, never write in a fucking browser because it'll do everything in its might to delete it all
16:29:07
Colleen
https://plaster.tymoon.eu/v... Website (XHTML), Title: Markless Line Break Problems - Plaster
16:31:27
gingerale
I feel that in editor style it'd be a single line and in wysiwyg it'd be two lines.
16:31:43
Shinmera
Maybe I should compile a list of these kinds of problem tickets similar to the CL standards' X3J13.
16:32:05
Shinmera
gingerale: Well what you feel it would be doesn't matter. The question is, how would you ever hope to get the opposite behaviour?
16:32:25
Shinmera
As it is right now you can only ever get one of them, but both are valid things you might want to do
16:33:33
Shinmera
Markdown has this thing where two spaces at the end of a line create a new line. I absolutely hate that, but we might need two separate constructs after all.
16:35:13
Shinmera
As in, escaped-continuing escaped-noncontinuing unescaped-continuing unescaped-noncontinuing
16:36:59
Shinmera
Another way I see is to get rid of singular line directives, and only have spanning line directives
16:37:18
isoraqathedh
Either that, or just naturally pair them up. In practice it's not likely that a header really needs two explicit lines.
16:39:16
isoraqathedh
I would say that editor-style would have \ be "force newline", and wysiwyg-style have \ be "ignore newline".
16:40:35
Shinmera
That's sensible for wysiwyg, but for editor-style it doesn't make sense anymore because
16:41:51
isoraqathedh
Though singular-line directives are singular-line and shouldn't really be extended to multiple lines to begin with.
16:44:01
Shinmera
And is part of the stuff that make Markdown such a pita to parse, so it's something I've wanted to explicitly avoid.
16:46:34
isoraqathedh
Ugly solution #3: use a BS character at the beginning of the line which is to be continued from the previous one.
16:53:14
Colleen
https://github.com/Shinmera... Website (HTML), Title: markless/line breaks.mess at master · Shinmera/markless · GitHub
17:04:34
Shinmera
Here's another issue while I'm at it https://github.com/Shinmera/markless/blob/master/issues/line%20directive%20simplicity.mess
17:04:35
Colleen
https://github.com/Shinmera... Website (HTML), Title: markless/line directive simplicity.mess at master · Shinmera/markless · GitHub
17:06:29
Shinmera
it'd probably be even better (albeit also more effort) if I gave you commit access and you could just commit proposals