sailfishos-chum / main

Documentation and issue tracker for the SailfishOS:Chum community repository
https://build.merproject.org/project/show/sailfishos:chum
MIT License
26 stars 4 forks source link

README: Fix typo and insert line-breaks #51

Closed Olf0 closed 2 years ago

Olf0 commented 2 years ago

… where deemed acceptable.

Background: Looking at the README as rendered at the sailfishos-chum/main frontpage now, made me wish to re-insert forced line-breaks at least at the locations where @rinigus indicated that they are acceptable for him: For avoiding the central web-link to run across a line end and to visually separate the FAQ questions from their answers. Thus, when I spotted a typo, I took the chance.

piggz commented 2 years ago

I wonder if any of these work and might be preferable? https://stackoverflow.com/questions/26626256/how-to-insert-a-line-break-br-in-markdown?rq=1

rinigus commented 2 years ago

Thank you very much! Merging :)

rinigus commented 2 years ago

@piggz - looks like we cross-posted. Saw your post later as "notification".

Olf0 commented 2 years ago

I wonder if any of these work and might be preferable? https://stackoverflow.com/questions/26626256/how-to-insert-a-line-break-br-in-markdown?rq=1

This adds another, orthogonal dimension to the partial disagreement between rinigus and me concerning forced line-breaks: the syntax! Actually that was not at all my point, and the way I understood rinigus, it also was not his concern. But the specific syntax suggested there is evil IMO: Two trailing, "invisible" space characters (which will be automatically wiped away by any proper linter) or a trailing backslash, which means exactly the opposite (the forced concatenation of lines) in many programming languages (shell etc.)!

Hence I rather stick to the explicit and specified syntax <br /> (while <br> and <br/> also work) and respect the demarcation line drawn with rinigus. :wink:

piggz commented 2 years ago

Fair enough, i wont loose sleep over it :D