The sound distributed version control system

#710 [BUG] Having problem recording changes in a json file (getting syntax errors, windows release)

Opened by RaniSharim on August 28, 2022
RaniSharim on August 28, 2022
# Syntax errors, please try again.
# Alternatively, you may delete the entire file (including this
# comment) to abort.
message = 'rem styling'
timestamp = '2022-08-28T06:24:45.964082600Z'

[[authors]]
key = '<removed>'

# Dependencies
[2] F7WS7EGUQCXX5IWWBUSDCIGP6DRIXMITFW2KKF6CQDIZWRQHNJSQC

# Hunks

1. Edit in "omnisharp.json":1 2.1 "UTF-8"
B:BD 2.1 -> 2.2:2350/2
- {
-     "FormattingOptions": {
-       "EnableEditorConfigSupport": false,
-       "OrganizeImports": true,
-       "NewLine": "\r\n",
-       "UseTabs": false,
-       "TabSize": 4,
-       "IndentationSize": 4,
-       "SpacingAfterMethodDeclarationName": false,
-       "SpaceWithinMethodDeclarationParenthesis": false,
-       "SpaceBetweenEmptyMethodDeclarationParentheses": false,
-       "SpaceAfterMethodCallName": false,
-       "SpaceWithinMethodCallParentheses": false,
-       "SpaceBetweenEmptyMethodCallParentheses": false,
-       "SpaceAfterControlFlowStatementKeyword": true,
-       "SpaceWithinExpressionParentheses": false,
-       "SpaceWithinCastParentheses": false,
-       "SpaceWithinOtherParentheses": false,
-       "SpaceAfterCast": false,
-       "SpacesIgnoreAroundVariableDeclaration": false,
-       "SpaceBeforeOpenSquareBracket": false,
-       "SpaceBetweenEmptySquareBrackets": false,
-       "SpaceWithinSquareBrackets": false,
-       "SpaceAfterColonInBaseTypeDeclaration": true,
-       "SpaceAfterComma": true,
-       "SpaceAfterDot": false,
-       "SpaceAfterSemicolonsInForStatement": true,
-       "SpaceBeforeColonInBaseTypeDeclaration": true,
-       "SpaceBeforeComma": false,
-       "SpaceBeforeDot": false,
-       "SpaceBeforeSemicolonsInForStatement": false,
-       "SpacingAroundBinaryOperator": "single",
-       "IndentBraces": false,
-       "IndentBlock": true,
-       "IndentSwitchSection": true,
-       "IndentSwitchCaseSection": true,
-       "IndentSwitchCaseSectionWhenBlock": true,
-       "LabelPositioning": "oneLess",
-       "WrappingPreserveSingleLine": true,
-       "WrappingKeepStatementsOnSingleLine": true,
-       "NewLinesForBracesInTypes": true,
-       "NewLinesForBracesInMethods": false,
-       "NewLinesForBracesInProperties": false,
-       "NewLinesForBracesInAccessors": false,
-       "NewLinesForBracesInAnonymousMethods": false,
-       "NewLinesForBracesInControlBlocks": false,
-       "NewLinesForBracesInAnonymousTypes": true,
-       "NewLinesForBracesInObjectCollectionArrayInitializers": false,
-       "NewLinesForBracesInLambdaExpressionBody": false,
-       "NewLineForElse": true,
-       "NewLineForCatch": true,
-       "NewLineForFinally": true,
-       "NewLineForMembersInObjectInit": true,
-       "NewLineForMembersInAnonymousTypes": true,
-       "NewLineForClausesInQuery": true
-     }
-   }
\
tankf33der on September 4, 2022

Can not reproduce in vim as $EDITOR.

korrat on September 5, 2022

I ran into the same issue today on Windows with VS Code. I was able to resolve it by saving the change file with LF line endings instead of the auto-detected CRLF ones.

Generally, I’ve also noticed that pijul does not handle CRLF line endings very nicely. For example, when line endings are CRLF, pijul always reports a diff, but nothing gets recorded.

rohan on September 6, 2022

You could try out my change from https://nest.pijul.com/pijul/pijul/discussions/708 and let me know if it helps with your Windows editor.