PolytreeDE/polybar
1
0
Fork 0
mirror of https://github.com/polybar/polybar.git synced 2024-10-27 05:23:39 -04:00
Code Releases Activity
polybar/.clang-tidy

49 lines
1.7 KiB
Text
Raw Normal View History

git: Add .clang-tidy rules
2016-10-28 06:31:35 -04:00
---
refactor(clang-tidy): Clean up .clang-tidy
2018-05-01 11:50:25 -04:00
Checks: '
-*,
performance-*,
readability-*,
clang-analyzer-alpha.core*,
clang-analyzer-alpha.security*,
clang-analyzer-alpha.unix.cstring*,
clang-analyzer-core.uninitialized*,
clang-analyzer-cplusplus.*,
clang-analyzer-nullability*,
clang-analyzer-unix*,
cppcoreguidelines*,
modernize-use-*,
modernize-*,
-modernize-raw-string-literal,
-modernize-use-bool-literals,
Disable modernize-use-trailing-return-type warning
2020-08-11 19:00:05 -04:00
-modernize-use-trailing-return-type,
Make the event loop return shared_ptrs (#2842) * Return shared_ptr from eventloop * Add -Wdeprecated-copy-dtor warning Produces a warning if classes don't have explicit copy operations if they have a user-defined constructor. This helps us stick to the rule of 5 (kinda, no warnings for missing move operators). * Clean up eventloop * Fix compiler warnings * Fix fs_event_handle_t name
2022-10-15 17:21:40 -04:00
-readability-identifier-length,
refactor(clang-tidy): Clean up .clang-tidy
2018-05-01 11:50:25 -04:00
-readability-implicit-bool-cast,
-readability-else-after-return,
-readability-named-parameter,
-readability-implicit-bool-conversion,
-cppcoreguidelines-pro-bounds-pointer-arithmetic,
-cppcoreguidelines-pro-bounds-array-to-pointer-decay,
-cppcoreguidelines-pro-type-vararg,
-cppcoreguidelines-pro-type-reinterpret-cast,
-cppcoreguidelines-pro-type-union-access,
-cppcoreguidelines-pro-type-cstyle-cast,
Make the event loop return shared_ptrs (#2842) * Return shared_ptr from eventloop * Add -Wdeprecated-copy-dtor warning Produces a warning if classes don't have explicit copy operations if they have a user-defined constructor. This helps us stick to the rule of 5 (kinda, no warnings for missing move operators). * Clean up eventloop * Fix compiler warnings * Fix fs_event_handle_t name
2022-10-15 17:21:40 -04:00
-cppcoreguidelines-pro-bounds-constant-array-index,
-cppcoreguidelines-owning-memory,
refactor(clang-tidy): Clean up .clang-tidy
2018-05-01 11:50:25 -04:00
'
fix(cmake): Tidy and format commands
2016-11-25 05:49:37 -05:00
CheckOptions:
fix(i3): Properly render non-full-width windows Without override-redirect, i3 will not allow you to have a non-full-width bar. But polybar simply ignores that request and continues to render the user-requested width instead of the width i3 has configured the window to be. With the 3.7 release, we started setting the window's backing pixmap to the rendering pixmap. In the case above, the pixmap would only be allocted for the smaller width and when i3 maps the window, it repeats the backing pixmap to fill the entire window. At the point where i3 maps the window, the pixmap contains an initial render of the bar without module content and that render is then duplicated. Reverting back to the old approach of simply copying over the pixmap after each render does not have that problem and the remainder of the bar is black (or fully transparent with a compositor). Ideally, polybar would respect the width i3 configures for it, but that would break many existing setups that rely on non-full-width bars in i3 Fixes #3060
2024-02-11 17:03:31 -05:00
cppcoreguidelines-avoid-do-while.IgnoreMacros: true
modernize-loop-convert.NamingStyle: lower_case
readability-identifier-naming.ClassCase: lower_case
readability-identifier-naming.ClassConstantCase: UPPER_CASE
readability-identifier-naming.ClassMethodCase: lower_case
readability-identifier-naming.MemberCase: lower_case
readability-identifier-naming.ProtectedMemberPrefix: 'm_'
readability-identifier-naming.PrivateMemberPrefix: 'm_'
fix(render): Deal with incomplete wallpapers If the root pixmap does not fully cover the bar window, some pseudo-transparent areas were filled with unitialized data, causing pixelation or other rendering artifacts. Now, ovserved background slices are first filled with black to make sure this does not happen and they print an error if not the full pixmap can be filled. Fixes #3041
2024-02-18 13:05:02 -05:00
readability-simplify-boolean-expr.SimplifyDeMorgan: false
fix(i3): Properly render non-full-width windows Without override-redirect, i3 will not allow you to have a non-full-width bar. But polybar simply ignores that request and continues to render the user-requested width instead of the width i3 has configured the window to be. With the 3.7 release, we started setting the window's backing pixmap to the rendering pixmap. In the case above, the pixmap would only be allocted for the smaller width and when i3 maps the window, it repeats the backing pixmap to fill the entire window. At the point where i3 maps the window, the pixmap contains an initial render of the bar without module content and that render is then duplicated. Reverting back to the old approach of simply copying over the pixmap after each render does not have that problem and the remainder of the bar is black (or fully transparent with a compositor). Ideally, polybar would respect the width i3 configures for it, but that would break many existing setups that rely on non-full-width bars in i3 Fixes #3060
2024-02-11 17:03:31 -05:00
git: Add .clang-tidy rules
2016-10-28 06:31:35 -04:00
HeaderFilterRegex: ''
fix(cmake): Tidy and format commands
2016-11-25 05:49:37 -05:00
WarningsAsErrors: ''
git: Add .clang-tidy rules
2016-10-28 06:31:35 -04:00
AnalyzeTemporaryDtors: false
...
Copy permalink