summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2024-10-11Fix ganv dependency fallbackDavid Robillard1-0/+1
2024-10-11Simplify missing UI file exceptionDavid Robillard1-5/+1
2024-10-11Fix function shadowingDavid Robillard2-8/+7
2024-10-11Avoid virtual calls in destructorsDavid Robillard5-11/+15
2024-10-11Remove redundant return statementDavid Robillard2-2/+0
2024-10-11Add missing const qualifiersDavid Robillard5-12/+8
2024-10-11Return larger values from accessors by const referenceDavid Robillard3-3/+2
2024-10-11Add cpplint testDavid Robillard3-0/+35
2024-10-11Remove redundant default values for meson optionsDavid Robillard1-4/+4
2024-07-17Remove unnecessary includesDavid Robillard2-2/+0
According to include-what-you-use 0.22 on LLVM 18, anyway.
2024-07-17Strengthen clang-tidy configurationDavid Robillard1-6/+0
Some of these suppress warnings in fmt, but meson's clang-tidy driver isn't smart enough to avoid checking that and wasn't clean anyway. So, just ignore this and use a stronger configuration that reflects the state of Patchage's own code.
2024-07-17Avoid use of rand()David Robillard3-5/+6
2024-07-17Avoid C-style castsDavid Robillard5-7/+10
2024-07-17Make member function staticDavid Robillard4-5/+4
2024-07-17Avoid signed bitwise operationsDavid Robillard4-13/+13
2024-07-17Fix narrowing conversionsDavid Robillard4-12/+14
2024-07-17Use uppercase integer literal suffixesDavid Robillard6-33/+37
2024-07-17Remove redundant inline specifierDavid Robillard2-2/+1
2024-07-17Remove redundant member initializerDavid Robillard2-4/+3
2024-07-17Remove unused local variableDavid Robillard2-2/+0
2024-07-17Suppress new warnings in clang and clang-tidy 18David Robillard2-0/+6
2024-07-17Use enums and constants over macrosDavid Robillard1-21/+19
2024-07-17Clean up includesDavid Robillard1-3/+12
2024-07-17Add missing const qualifierDavid Robillard1-2/+2
2024-07-13Add missing includesDavid Robillard9-0/+9
According to include-what-you-use, anyway. Most of these seem questionable/unnecessary, but since the whole point here is to avoid wasting time doing manually what machines can do, just do what the tool says to keep the checks clean even if it's suboptimal.
2024-06-04Suppress new warnings in clang-tidy 17David Robillard1-1/+2
2024-06-04Add missing includeDavid Robillard1-0/+1
2024-06-04Avoid std::endlDavid Robillard3-26/+24
2023-12-11Update required ganv dependency versionDavid Robillard1-2/+1
2023-12-11Explicitly disable sprung layout menu item by defaultDavid Robillard2-1/+3
2023-09-23Format meson.build files with muonDavid Robillard3-30/+44
The less time wasted with manual code formatting, the better.
2023-09-22Use anonymous namespacesDavid Robillard4-140/+145
2023-09-22Fix new warnings with clang-tidy 16David Robillard1-1/+3
2023-09-22Clean up includes and forward declarationsDavid Robillard13-26/+30
2023-09-21Fix new warnings with clang 16David Robillard1-0/+2
2023-05-12Fix use of reserved macro nameDavid Robillard5-15/+12
2023-05-12Replace macro with typed constantDavid Robillard2-12/+9
2023-05-02Replace strict option with new meson warning levelDavid Robillard4-201/+17
2023-05-02Simplify configuration headerDavid Robillard1-36/+33
2023-05-02Remove redundant license metadataDavid Robillard3-6/+5
2023-02-03Suppress/fix new warnings in clang-tidy 15David Robillard8-21/+28
2022-12-10Bump version and update NEWS fileDavid Robillard4-3/+9
2022-12-10Update patchage.desktop.inJunghee1-1/+1
2022-11-30Convert man page to mdocDavid Robillard1-29/+43
2022-11-15Add missing includesDavid Robillard2-0/+2
2022-09-09Patchage 1.0.10David Robillard7-8/+8
2022-09-08Use 0BSD for trivial "public domain intent" thingsDavid Robillard15-136/+27
Fedora takes issue with CC0. Although it doesn't really matter for this stuff (dual licensed anyway, questionably "software", certainly not patentable, and so on), this is simpler and more consistent with the ISC license used for the actual software anyway.
2022-08-24Add French translationOlivier Humbert2-1/+155
2022-08-23Fix REUSE testDavid Robillard1-1/+1
2022-08-23Use a consistent style for .po file headersDavid Robillard1-2/+3
Since these usually come from tools, it doesn't seem realistic to maintain a different header. That's just another thing for meson/xgettext to constantly smash. Having spent so much time and effort to get precise about copyright and licensing with REUSE, the somewhat fuzzy and haphazard way all this works irks me a bit, but I have better hills to die on.