Every placeholder in the Statusbar Template may also specify width, e. g. `%3l`. Width is the minimum number of characters to be shown. If the value is shorter than width, the result is left-padded with spaces, or right-padded in case of negative width. The value is not truncated even if the result is larger. You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3221
-- Commit Summary --
* Statusbar Template enhancement: width specifier. * Style fix. * Debug code dropped.
-- File Changes --
M doc/geany.txt (26) M src/ui_utils.c (71)
-- Patch Links --
https://github.com/geany/geany/pull/3221.patch https://github.com/geany/geany/pull/3221.diff
@van-de-bugger pushed 1 commit.
d1718f1a0b539869b822cf0fab652122c82b58e2 Attempt to fix mingw build.
@elextr commented on this pull request.
``%Y`` The Scintilla style number at the caret position. This is
useful if you're debugging color schemes or related code. ============ ===========================================================
+Every placeholder may also specify width, e. g. ``%3l``. Width is the minimum +number of characters to be shown. If the value is shorter than width, the +result is left-padded with spaces, or right-padded in case of negative width. +The value is not truncated even if the result is larger. +
Document limit of +/- 100
Looks ok by quick inspection.
@van-de-bugger pushed 1 commit.
1b3d77c54d1ef5e49cbb440869ddd28f423aa8fc Allowed width range is extended to [-300..300] (status bar on the
@van-de-bugger commented on this pull request.
``%Y`` The Scintilla style number at the caret position. This is
useful if you're debugging color schemes or related code. ============ ===========================================================
+Every placeholder may also specify width, e. g. ``%3l``. Width is the minimum +number of characters to be shown. If the value is shorter than width, the +result is left-padded with spaces, or right-padded in case of negative width. +The value is not truncated even if the result is larger. +
Limit is expanded to [-300..300] and documented.
It there any chances the patch will eventually be applied? The patch will celebrate a birthday in two weeks...
Well, "somebody" (other than the OP) needs to review and test it, there is no need for that to be someone from the project team who are limited in available time due to "real life". The tester can just post here. This will minimise the time required of the core team, and likely indicates there is interest in the change. To anybody watching the repository, this applies to _all_ PRs.
github-comments@lists.geany.org