thats because X is an event model layered ontop of STDIN and STDout which
amazingly are everywhere in UNIX. and IN X it actually intercepts these that
is why you have 2 keybinding places.. because if you are focused on an xterm
then the keybindings go there and always to X, and if you are on a GUI
window they are mapped to whatever the library system for that GUI does...
So yes it is a pain in the ARSE... I would think that the whole event model
should be reorganized in another application layer so that new code base can
deal with it in a organized fashion and not by hit and miss or my gosh I am
not focused right and I press Xyz and deleted that... SHIT... not good...
I would vote for some type of visual or bell feedback so that if you are
doing something you get a hint that all is well before you rm -rf the root
drive with a key binding short cut....
On Thu, Apr 06, 2006 at 11:38:30AM +0200, Anselm R. Garbe wrote:
> Hi,
>
> On Thu, Apr 06, 2006 at 11:22:43AM +0200, wmii-owner_AT_wmii.de wrote:
> > On Thu, 6 Apr 2006 08:41:14 +0200, "Anselm R. Garbe" <garbeam_AT_wmii.de> said:
> > > On Wed, Apr 05, 2006 at 12:01:49PM -0700, Suraj N. Kurapati wrote:
> > >> # SHORTCUTS
> > >> +
> > >> +# wmii +shortcut_reloadConfig=$MODKEY-Control-w,y
> > >> +shortcut_quit=$MODKEY-Control-q,y
> >
> > > Sorry, this looks much more cumbersome to me. In the old way I see
> > > exactly what happens if a specific shortcut is reported by /event in
> > > wmiirc, with this approach wether I trust the variable name or I
> > > have to recheck... you have much overhead in maintaining this in my
> > > eyes...
> >
> > Hint: SPOT-rule (Single point of truth)
> >
> > I know at least three people who looked at the wmiirc and said it is
> > shit. And -as it is very likely lots of people will look at the
> > scripts-, we should try to make every effort to keep them clean and
> > consistent.
> >
> > So please consider a way to have keycodes/shurtcuts without having to
> > define them on two distinct places.
>
> If someone presents a nice idea which works with sh, maybe in
> conjunction with awk, I'm open to do it. Otherwise blame X that
> it needs to grab shortcuts and there is no portable way to get
> keyboard events in any other way.
>
> Regards,
> --
> Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361
>
> _______________________________________________
> wmii_AT_wmii.de mailing list
> http://wmii.de/cgi-bin/mailman/listinfo/wmii
Received on Sat Apr 08 2006 - 02:04:18 UTC
This archive was generated by hypermail 2.2.0 : Sun Jul 13 2008 - 16:02:04 UTC