Bash – The shell’s “delete word” shortcut deletes too many characters

When trying to use similar window managers (xwem, ratpoison) for the first time, I first also tried to follow the setup instructions involving xmodmap to get a modifiier key for the window manager, but then I felt that using xmodmap in my system causes some mess, because in my system (an ALTLinux distro) attention has always been paid to multilingual keyboard configuration via XKB, rather than via xmodmap.

So, I found an XKB option to label the key I wanted as "Hyper", and then used the "Hyper" modifier in the configuration for xwem or ratpoison.

In my case, the option to setxkbmap is:

 -option altwin:hyper_win

and here is the comment I've saved on the occasion of adding it to my setup:

xemacs-xwem uses Hyper, so I found this predefined XKB map (in xkb/symbols/altwin), which uses the WIN keys.

Perhaps later I'll make up another XKB map for me, say, using the right Control as Hyper (that will force my hand to use the right Control--now my hand just ignores it).

I thought it's a more clean way to get myself a Hyper key through XKB rather than through xmodmap (as described in XWEM docs), because:

1. xmodmap configuration of modifier keys seems not to be nice w.r.t. the way it forces one to present one's intentions: one must say something about arbitrarily numbered modifier bits, but I don't want to think about these technical things: I need merely a "Hyper" modifier, not some obscure manipulations with the internals! In xmodmap, I'd need to give 2 or even 3 obscure statements to achieve the result, although logically this is a single wish and operation. (One xmodmap statement would not be enough, cf. XEmacs' warnings (FIXME: insert!) if you map Control_R to a modN; there are some technical constraints.)

2. one is told stories that XKB and xmodmap don't play well together, so that not all X programs will work nicely and coherently if you mix them (I must give a link here, FIXME).

Here is the relevant definition from /usr/share/X11/xkb/symbols/altwin, if someone is interested:

partial modifier_keys 
xkb_symbols "hyper_win" {
    key <LWIN> {    [   Hyper_L         ]   };
    key <RWIN> {    [   Hyper_R         ]   };
    modifier_map Mod4   { Hyper_L, Hyper_R };
};

What makes Ctrl-Z different from kill -STOP, and how can I get the behavior of the former in a shell script?

CTRL-Z usually sends SIGTSTP (which can be blocked), and - apart from other things - shells often reset tty to a previously saved state on these occasions. More importantly however, the controlling terminal process group is set to the shell's PID (and then again to a PID of a job resumed with fg).

Back to your original problem: using a temperature dependent frequency scaling like e.g. Cpufreqd might be actually a better hammer for your nail.