20
850
Fork
You've already forked fuzzel
83

Allow negative values for x-margin/y-margin in config file #711

Open
opened 2025年11月28日 11:39:44 +01:00 by VKint · 1 comment

Pre-checks

Do similar tools already implement this feature?

No response

Describe your feature request

Negative margins work via CLI (--y-margin=-32) but not in the config file. The config file rejects them with:

invalid integer value, or outside range 0-4294967295

This would be useful for positioning over exclusive zones - e.g., appearing at the true top of the screen instead of below a bar like waybar

### Pre-checks - [x] The [fuzzel.ini](https://codeberg.org/dnkl/fuzzel/src/branch/master/doc/fuzzel.ini.5.scd) and [fuzzel](https://codeberg.org/dnkl/fuzzel/src/branch/master/doc/fuzzel.1.scd) man pages. - [x] [Changelog](https://codeberg.org/dnkl/fuzzel/src/branch/master/CHANGELOG.md#unreleased) of newer and unreleased features ### Do similar tools already implement this feature? _No response_ ### Describe your feature request Negative margins work via CLI (--y-margin=-32) but not in the config file. The config file rejects them with: > invalid integer value, or outside range 0-4294967295 This would be useful for positioning over exclusive zones - e.g., appearing at the true top of the screen instead of below a bar like waybar
Collaborator
Copy link

Not only do negative y margins work via the CLI, it appears that they eventually wrap around, so that huge values are treated like a zero:

 echo 'test' | fuzzel --anchor=bottom --lines 1 --prompt 'Test' --dmenu --y-margin=-1000000000000000000000000

Supporting negative margins seems OK, although we should have some reasonable limit on it.

Not only do negative y margins work via the CLI, it appears that they eventually wrap around, so that huge values are treated like a zero: ``` echo 'test' | fuzzel --anchor=bottom --lines 1 --prompt 'Test' --dmenu --y-margin=-1000000000000000000000000 ``` Supporting negative margins seems OK, although we should have some reasonable limit on it.
Sign in to join this conversation.
No Branch/Tag specified
master
gnome-support
releases/1.14
issue-319-window-switching
issue-561-nord-theme-only
resvg-filtering-take-2
resvg-filtering
releases/1.13
rehanzo-dont-ignore-execute-648
keybinds-overwrite
issue-561-refresh-theme
ci-automated-testing
reenable-legacy-icons
releases/1.12
test-coverage-for-fzf-caching
releases/1.11
releases/1.10
releases/1.9
releases/1.8
releases/1.7
releases/1.6
releases/1.5
releases/1.4
releases/1.3
releases/1.2
releases/1.1
releases/1.0
1.14.1
1.14.0
1.13.1
1.13.0
1.12.0
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.2
1.8.1
1.8.0
1.7.0
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.2
1.4.1
1.4.0
1.3.0
1.2.0
1.1.0
1.0.1
1.0.0
0.9.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dnkl/fuzzel#711
Reference in a new issue
dnkl/fuzzel
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?