| Summary: | Kate ignores the "Remove trailing spaces" being "On Modified Lines" when an .editorconfig is present | ||
|---|---|---|---|
| Product: | [Applications] kate | Reporter: | Nikos Chantziaras <realnc> |
| Component: | application | Assignee: | KWrite Developers <kwrite-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | wishlist | CC: | christoph, waqar.17a |
| Priority: | NOR | ||
| Version First Reported In: | 21.12.0 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Nikos Chantziaras
2021-12-18 00:29:08 UTC
Hi, I think this is working as intended. We have to respect the editorconfig and do exactly what it says otherwise there is no point in having the editorconfig file. To resolve this, the editorconfig must add another option to "Remove trailing spaces on modified lines only" (In reply to Waqar Ahmed from comment #1) > We have to respect the editorconfig and do exactly what it says otherwise > there is no point in having the editorconfig file. I believe it's up to me whether or not I want to respect the editorconfig file. I mean, I'm the one writing the code, the decision is up to me :P My only options right now is to either drive myself insane with all these changed lines and then jump off a bridge when I can't take it anymore, or use another editor, which would really suck because Kate is great. > To resolve this, the editorconfig must add another option to "Remove > trailing spaces on modified lines only" I don't think there is such an option? You have another option. As you said it's up to you, you can remove that setting from the editorconfig and then Kate will respect your settings. In practice there shouldn't be any spaces in the first place or not a setting in the config if you want spaces to be preserved. The only way spaces would end up in files would be that someone used an editor which didn't respect editorconfig which again defeats the point of having that config. Also I closed the issue because there is no way forward with this. We cannot not respect editorconfig. Reopening doesn't change that. (In reply to Waqar Ahmed from comment #3) > You have another option. As you said it's up to you, you can remove that > setting from the editorconfig and then Kate will respect your settings. It' not my project. I just contribute to it. I didn't put the editorconfig in it. > In practice there shouldn't be any spaces in the first place or not a > setting in the config if you want spaces to be preserved. The only way > spaces would end up in files would be that someone used an editor which > didn't respect editorconfig which again defeats the point of having that > config. Yeah. So I would like to ignore it. > Also I closed the issue because there is no way forward with this. We cannot > not respect editorconfig. Reopening doesn't change that. Why can you not not respect editorconfig? I don't get it. Is it a law and you have to respect it? Would you get sued if you had an option to either ignore it, or leave the interpretation of "clean spaces" up to the user? First I must say: no, respecting the file is correct. If you don't want that style either edit it or argue with the people that want that style in that project, if it is not the style you would like. Beside this, perhaps it would make sense to have some option to disable the loading of both .editorconfig and .kateconfig files. But that is nothing high up in my priority list. For alternate solutions mentioned by Christoph, feel free to open a new bug report. Right now its working as intended. |