-- ...
awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
-- ...
If if isn't there add it to the globalkeys array.
]]>Does this problem occur if you use the default (non-modified) awesome rc.lua?
Does it change anything if you place the mouse cursor over the awesome bar before typing the command?
I copied the rc.lua from /etc/xdg/awesome, as per the ArchWiki's page on AwesomeWM. I've made only one change since noticing this problem (changing the wallpaper), but the problem was there from the start.
Nothing changes if I place the mouse cursor over the bar at any point.
I forgot to mention in the OP that the escape key doesn't close the prompt when I open it a second time (after entering something). I can, however, press Mod+x to change it to a lua code prompt, but that behaves the exact same way.
]]>Does it change anything if you place the mouse cursor over the awesome bar before typing the command?
]]>When I use mod+r to start firefox, for example, nothing happens after I press enter. Then if I try to press mod+r again and start firefox, I cannot input anything in the run prompt at the top of the screen. If I have a terminal open, the input goes into the terminal rather than the run prompt (it's the other way around on the first attempt)
The lua code prompt is the same.
edit: Sorry wrong section, you can ignore this. I'll ask in the right place.
edit2: Nevermind, the post in the right section was deleted. Don't ignore this.