#Releases · FPtje/GLuaFixer
1 messages · Page 1 of 1 (latest)
It doesn't do it on my laptop but im not sure what I did to make that happen ☠️
time to download 6 month old glualint
1.24.6 is the last version to not do the weird @mild thorn
Thanks, I have it too and it's a huge turn off
ugh i dont wanna downgrade
You either get used to it or just remove every time this occurrence happens
Both sucks imo
gonna remove multiline changes in a fork ✅
I was going to ask for that to be fixed, read the PR and I was like "huuum it's what it is"
@inner lotus ^ you might care about the conversation above
It's been like that for a couple of versions
The thing is that the style with mixed multiline is great, but hard to program
stuff like this makes it kinda unusable for me
Fun fact, it's the default style for Python
I can look into it, but I expect to hit barriers
poor python users
I generally like the multiline style with longer parameters, like creating convars for instance
But for <5 char params it's simply worse
what about this #1190400384213192705 message
send that fork if you do it 🙂
it might work I don’t know Haskell 🫡
I think I had it done hours ago
never pushed to remote though
too tired to even try to build it but here u go https://github.com/Yogpod/GLuaFixer
After many complaints and begs I started experimenting on this branch: https://github.com/FPtje/GLuaFixer/commit/fe4563438bf4b27fdb66a2af63052b4a8bac5d8c
No promises
The above code is probably buggy, in that there's a good chance that it causes bugs like "omg reformatting causes syntax errors" when it puts the ) after a comment for example
Maybe I’m confused… I downloaded an older version of glualinter that has this already. I couldn’t find anything in the update logs saying why function arguments were moved to new lines now or any options to turn it off
Talking about the pretty print options that is
There was a bug regarding printing comments. It was particularly nasty to fix. I ended up restructuring a big part of the code. I ended up with the format it has now. @spark mesa
I have regression tests now, though, so I should be able to mess around without breaking too much
We all here use your linter as we use Billy's extension, everyday you're part of our code fptje 
Thanks!
What's Billy's extension?
Vscode extension, your glitter and Billy's it's a must have
https://github.com/FPtje/GLuaFixer/pull/176#issuecomment-1872959205
There's a test version here. For those who replied to this thread, could you test this?
There are some executables in there and some test instructions. Please download those and use them on your projects. I'd like to know what you think
For now everything it's going great
That's great to hear!
compared to before, 👍
Cool!
Nice work 
Made a new release here, with the changed formatter: #tool-releases message
For those who tried out the test version yesterday, there is a difference with 1.28.0, specifically in how -- format: multiline is handled. In the test version, this woul have no effect. In version 1.28.0, this causes all arguments to be printed on a new line

