| Summary: | Sensitive word is misspelled in the config and source code | ||
|---|---|---|---|
| Product: | [Applications] krusader | Reporter: | Toni Asensi Esteve <toni.asensi> |
| Component: | general | Assignee: | Krusader Bugs Distribution List <krusader-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | dufferzafar0, krusader-bugs-null, nikita+kde |
| Priority: | LO | Keywords: | reproducible, triaged |
| Version: | 2.7.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
Several places where the word "sensative" is used
The option "case sensitive sorting" that the user can check but that later is written incorrectly in the "krusaderrc" file An option that is badly written in the "krusaderrc" file |
||
Created attachment 114136 [details]
Several places where the word "sensative" is used
Created attachment 114137 [details]
The option "case sensitive sorting" that the user can check but that later is written incorrectly in the "krusaderrc" file
Created attachment 114138 [details]
An option that is badly written in the "krusaderrc" file
Is the fix as simple as just "s/sensative/sensitive" across the entire codebase? Will this correctly read already existing "krusaderrc" config files that have "Case Sensative Sorting" written into them? > Is the fix as simple as just "s/sensative/sensitive" across the entire codebase? It seems that the most important part will be solved this way :-), although someone should try it :-) > Will this correctly read already existing "krusaderrc" config files that have > "Case Sensative Sorting" written into them? No :-) , and there comes the "EXTRA" section in the bug report, maybe someone will have an idea to solve that, and if he doesn't, it's not a big problem (because "users would be able to enable that preference again"). Replaced all occurrences of "sensative": https://phabricator.kde.org/D14416 |
In the source code the word "sensative" is seen in several places, it's better if it's replaced with the word "sensitive" because that word is a correct one. I'll attach some screenshots to give additional information. EXTRA: In the case of the users (they aren't many) that are already using that preference: [Look&Feel] Case Sensative Sort=true then some additional actions might be done (although those users would be able to enable that preference again and then their problem would be solved).