bouncepaw / mycorrhiza

🍄📑 Filesystem and git-based wiki engine for the independent web written in Go and using Mycomarkup as its primary markup language.
https://mycorrhiza.wiki
GNU Affero General Public License v3.0
305 stars 26 forks source link

Idea of a sentences separation #154

Closed danilax86 closed 2 years ago

danilax86 commented 2 years ago

I think that

input:

one line
one line

another line

out:

one line one line
another line

is better than we have now out:

one line
one line

another line

It is a pain not to separate sentences with lines if you write in some text editors. Reading the whole stuff from one edge of the screen to another is kinda exhausting

I mean

image

is better than

image

and they should be rendered the same way

You can read https://sive.rs/1s for a better understanding.

bouncepaw commented 2 years ago

Wontfix. Line breaks be line breaks. Configure your text editor to softwrap on a given column.

I believe we had the proposed line behaviour before. It wasn't good.

I could consider a trailing backslash to join lines though.

danilax86 commented 2 months ago

@bouncepaw One more thing to consider. When you edit a single (or more) word in a one-line text, the diff output is insane and shows you the whole text, not your edit. So, if there is a merge conflict it is impossible to solve it, because it is a one line. Since the mycorrhiza is built upon a git, there is no other way to work, but with separate lines.

If you disagree, read this: https://grishaev.me/strings-80/ (translated by robot)

Next - conflicts. If the paragraph is not cut into lines of 80 characters, it is impossible to correct conflicts. Please read this sentence again: it is impossible to correct conflicts. Without cutting, a paragraph is a single line, and if Vasya corrected the letter at the beginning, and Petya at the end, it's a conflict. Write claims to the creators of Git, CSV and other version control systems. Their working unit is a string, and others are not foreseen.

bouncepaw commented 2 months ago

the diff output is insane and shows you the whole text, not your edit

This is true. The proper solution is to have a better diff output though. The real solution is to ditch Git, but this is my power fantasy, it won't happen any time soon.

if there is a merge conflict it is impossible to solve it, because it is a one line

Merge conflicts are impossible to solve in Mycorrhiza already...