Hi Thomas,
This should have been sent to f...@fvwm.org -- please don't ask me questions
about FVWM off-list. As such, I'm adding fvwm@ back in to this discussion.
- I did it first, but I get email back with subject Stalled post to fvwm on
both addresses (f...@fvwm.org and fvwm@lists.math.uh.edu)
of curiosity, I picked up the latest main branch head
snapshot (fvwm-snap-20110724) thinking that perhaps it might also have this
fix, but it evidently does not (fvwm.c is identical to 2.6.1). This makes me
wonder: Roughly how often are branch-2_6 updates being merged into the main
branch?
of curiosity, I picked up the latest main branch head
snapshot (fvwm-snap-20110724) thinking that perhaps it might also have this
fix, but it evidently does not (fvwm.c is identical to 2.6.1). This makes me
wonder: Roughly how often are branch-2_6 updates being merged into the main
branch?
They're
In fvwm 2.6.1: If several menu items are associated with a particular hotkey,
then typing that key repeatedly cycles thru those items, hilighting each in
turn; then you hit cr (or space) to invoke the one you want. But if there's
only one item is associated with a given hotkey, then hitting that
Hello --
On Sun, Jul 24, 2011 at 11:31:56AM -0600, Glenn Golden wrote:
In fvwm 2.6.1: If several menu items are associated with a particular hotkey,
then typing that key repeatedly cycles thru those items, hilighting each in
turn; then you hit cr (or space) to invoke the one you want. But if
Thomas Adam writes:
Does the attached patch unconditionally define the behaviour you're after
though?
Indeed it does.
If so, I'll embelish it with options, and commit to CVS.
Way cool dudeski, thanks!
Certainly can't complain about the response time on this list... :)
Glenn
Thomas Adam writes:
On Sun, Jul 24, 2011 at 02:52:56PM -0600, Glenn Golden wrote:
I'm not implying there's anything wrong with this; just pointing it out,
because it confused me a little when I was testing it and toggling back
and forth between the two modes. It's entirely consistent with
On Sun, Jul 24, 2011 at 09:07:37PM -0600, Glenn Golden wrote:
My suggestion would be to rename the option to something along the lines of
HotkeyActivatesImmediate, or perhaps UniqueHotkeyActivatesImmediate, and
That's fine; I can change the name.
then document it something like this:
