Fork me on GitHub
#calva
<
2021-12-08
>
emccue01:12:46

On 227 with parinfer and strict mode on. I cannot seem to make a defrecord for the life of me

pez15:12:59

I can’t fully follow what happens (or not) in the GIF. But anyway, are you saying it works with strict mode off?

emccue20:12:09

i can do the same flow with my onscreen keyboard visible. in hindsight that would have made more sense

pez20:12:11

Please also describe in words where things do not go as expected.

emccue21:12:41

when i try to add a new protocol method it auto indents the protocol name and existing methods into the field declarations

JR01:12:35

Is there a VS Code spellchecker that works with Calva? I tried Code Spell Checker but it doesn’t seem to work (I’m new to VS Code though)

JR01:12:27

Doh! Clojure wasn’t enabled in the preferences. Just click on Clojure in the spell check preferences and it works

metal 1
pez17:12:05

There’s a parinfer take 3 PR now. FYI. Here’s the latest VSIX. https://16495-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.229-pez-253-parinfer-take-3-e4f3d075.vsix It’s like Calva v2.0.227 with a 229 changes and with a change of autoindent that might fix https://github.com/BetterThanTomorrow/calva/issues/1411, Can you test it, @brandon.ringe?

bringe17:12:40

Just installed it. Will do my work with it.

bringe18:12:46

Just noticed this red rectangle in the output window when I jacked in to a shadow project.

bringe18:12:34

Oh, notice the off coloring of “evaluate” too

bringe18:12:28

When I try to create a new line after a function arg vector in this example code, the cursor goes all the way to the left:

(ns honestdeed.test)

(defn hello []
)
Then when I hit tab I get a warning: command 'calva-fmt.formatCurrentForm' not found .

bringe18:12:17

Also, backspace stops working

bringe18:12:01

I’ll install the latest release again so I can work, but hopefully that gives you some clues for where to look for the issues.

bringe18:12:57

These settings are at the bottom of my user settings file and may have been added by this vsix version (though I’m not sure):

"[clojure]": {
        "editor.autoClosingBrackets": "always",
        "editor.autoClosingOvertype": "always",
        "editor.formatOnPaste": true
    },

seancorfield18:12:33

As a sanity check, I'm on 228 and my settings has these:

"[clojure]": {

        "editor.wordSeparators": "\t ()\"':,;~@#$%^&{}[]`",
        "editor.autoClosingBrackets": "always",
        "editor.autoClosingQuotes": "always",
        "editor.formatOnType": true,
        "editor.autoIndent": "advanced",
        "editor.formatOnPaste": true,
        "editor.matchBrackets": "near",
        "files.trimTrailingWhitespace": true,
        "files.trimFinalNewlines": true,
        "editor.autoClosingOvertype": "always"
    },

🙏 1
pez20:12:03

Thanks! It was those red rectangles that got me to revert 227, so it is kinda good that you have it, @brandon.ringe. I already feel we are closer to solve the problem, even if right now I am a bit too tired to make any sense out of anything.

👍 1
pez07:12:53

Checking. In that shadow project, @brandon.ringe, was the output window in CRLF mode?

pez07:12:48

I can reproduce it that way….

bringe16:12:41

I have good news and bad news. The good news: I reinstalled the vsix on (I’m pretty sure) the same project and I’m not having any of the issues mentioned above now. The bad news: I don’t know what happened before, so there could be some issue lurking that will pop up later.

bringe16:12:03

And as for CRLF, I’m pretty sure it was LF, since I’m on MacOS and didn’t change it, but I suppose I can’t be certain. I don’t know what would have caused the file to be in CRLF mode, though.

Stefan07:12:26

@U0ETXRFEW Do you have a PR in progress for this where I can easily take the latest build from, like last time?

pez07:12:15

Yes, I hesitated to promote it because I have not added any description to it yet, but here it is: https://github.com/BetterThanTomorrow/calva/pull/1429

👍 1