Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea of a sentences separation #154

Closed
danilax86 opened this issue Jul 2, 2022 · 3 comments
Closed

Idea of a sentences separation #154

danilax86 opened this issue Jul 2, 2022 · 3 comments

Comments

@danilax86
Copy link
Contributor

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
Copy link
Owner

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
Copy link
Contributor Author

@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
Copy link
Owner

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants