You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The document string uses the Windows line ending format (i.e., \r\n) for no good reason. Please convert the whole repository to only use \n for newlines.
Having such extremely long lines as for the document string makes it very hard to quickly compare changes with tools like gitk. Giving that JSON doesn't allow multi-line strings – for me this would have been a reason to not choose JSON at all – I ask to find solutions to avoid that, for example, by putting all those long strings into separate files as plain-text documents, inserting them into the final JSON structure using a post-processor like jq by calling make or something similar. [Note that I have zero experience with JSON; maybe jq isn't the right tool.]
The text was updated successfully, but these errors were encountered:
lemzwerg
changed the title
don't use Windows newlines in git repository
neither use Windows newlines nor long lines in repository
May 9, 2024
Please have a look at the current output of gitk.
There are two issues.
document
string uses the Windows line ending format (i.e.,\r\n
) for no good reason. Please convert the whole repository to only use\n
for newlines.document
string makes it very hard to quickly compare changes with tools likegitk
. Giving that JSON doesn't allow multi-line strings – for me this would have been a reason to not choose JSON at all – I ask to find solutions to avoid that, for example, by putting all those long strings into separate files as plain-text documents, inserting them into the final JSON structure using a post-processor like jq by callingmake
or something similar. [Note that I have zero experience with JSON; maybejq
isn't the right tool.]The text was updated successfully, but these errors were encountered: