-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find in the hotkeys popup #3970
base: master
Are you sure you want to change the base?
Conversation
lib/awful/hotkeys_popup/widget.lua
Outdated
@@ -371,6 +427,22 @@ function widget.new(args) | |||
beautiful.hotkeys_description_font or "Monospace 8" | |||
self.group_margin = args.group_margin or | |||
beautiful.hotkeys_group_margin or dpi(6) | |||
self.highlight_bg = args.highlight_bg or | |||
beautiful.hotkeys_highlight_bg or "#ffff00" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please default to other beautiful.*
variables which are for sure defined in the default theme.lua instead of falling back to hardcoded colors
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this bright yellow, because the point is to easily see highlighted text. For example firefox uses #ff00ff
, also bright.
What about beautiful.bg_urgent
(red)? I haven't found any other beautiful colors that fit it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup, just choose any placeholder from beautiful, that bg_urgent is fine by me.
people who care more would set the right theme key anyway
thanks for submitting, i found small issue right from the description (and left a separate comment), i'll start reviewing the code itself later on in upcoming days or mb even hours |
and also the test is failing:
|
regarding keygrabber question, i'll need first to understand:
|
also, mb add a bool option to args for closing hotkeys on a any keypress (the current behavior), so the users who used to that, could restore that old default behavior |
i think |
Because I use Actually, I need to check if the prompt is stopped gracefully. Right now I just call
I added
I don't know. What are the odds that you want multiple prompts for different hotkey popups? It's just a simple text "find: ", nothing more so I thought was easier for user to set it once in the theme. |
it wasn't a point about having multiple different prompts, but about untying translation and style - and as you can see from our existing themes (and defined theme variables in the awful/wibox/etc builtin libraries), it's indeed not a used practice storing such sort of info there
thanks 👍
ok i'll try to dive into |
style checking is failing in the CI btw |
self.highlight_fg = args.highlight_fg or | ||
beautiful.hotkeys_highlight_fg or beautiful.fg_urgent | ||
self.find_prompt = args.find_prompt or | ||
beautiful.hotkeys_find_prompt or "<b>Find: </b>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as i mentioned in previous comment this shouldn't be defined in beautiful, as its role defining theme, not translation/labels
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
⬆️
Implements #3963
awful.prompt.run
show_help()
does not returnawful.keygrabber
(breaking change?)Theme variables
highlight_bg
"#ffff00"
highlight_fg
"#000000"
find_fg_cursor
find_bg_cursor
find_ul_cursor
find_prompt
"<b>Find: </b>"
find_font
font
find_margin
group_margin