not directly kotlin related but maybe knows it non...

# intellij

[robstoll]

not directly kotlin related but maybe knows it nonetheless. How can I see permission changes in the diff view of a file?

[Mike]

Hmm. If this article is still valid, then Git only truly tracks the executable bit.

https://medium.com/@tahteche/how-git-treats-changes-in-file-permissions-f71874ca239d

Do you see a change using the CLI? If you do, at least it would be possible for IntelliJ to display something. But I suspect this is uncommon enough, that it hasn't been implemented in the UI. Too many other changes going on right now.

[robstoll]

I meant the executable flag

[robstoll]

I saw contributors changing this permission and could not see what they changed and how they should revert it. That's why I am asking. You can see it with git diff

[Mike]

I suspect Jetbrains hasn't added it. The file shows as changed, but you currently have to use CLI to see what has changed, as IntelliJ just shows 'no changes'. But I assume you already knew/suspected that.

[robstoll]

That's exactly what confuses the contributors. I hoped there os a configuration flag to reveal the change as such. I guess I have to open a feature request then. Thanks for your time

[Mike]

NP. But now I'm curious. How are there so many changes on executable files? Assuming JVM (does Atrium target MPP? Haven't looked in awhile as I only get to do Kotlin on pet projects these days), then usually it's just gradlew needing to be set if project was created on Windows.

[robstoll]

it was gradlew 😄

[robstoll]

someone removed the executable flag and was confused why the build failed

[Mike]

That's a tough one to handle.

One would expect a Unix based user to understand the concept of 'executable flags' and not mess with them.

And a Windows user would really have to go out of their way to do it.

But yes, I suspect it's a feature request, and unfortunately for you, likely to get very low priority.

[robstoll]

it was a mac user 🙈 😄

[Mike]

So weird, isn't it. As I think the only way to change it is the CLI, so they had to intentionally do a chmod -x.

No end to what people will manage to accomplish, and then try to blame everything, rather than one person 😉

[robstoll]

indeed, I can only guess but I think this person removed gradlew, generated it somehow where the flag is missing and did not set it again. Maybe something along this line.

[Mike]

This is the problem with people not knowing there tools. If that's the scenario, then a simple git revert would have sorted them out... Or rollback in IntelliJ or...

I feel for you...