Re: getting the "real" command-name in the `pre-command-hook'?!

Klaus> You see that i get never the name of the command `info' in Klaus> the pre-command-hook, Ah. Unfortunately, `info' is _not a command_ in this context, it's a function. That is (I assume) it is being called via 'funcall' or `apply', not via `call-interactively'. The last seems wrong, though, you'll just go around the circle again, I bet. Here are my current guesses: Having minibuffer-complete-and-exit setq this-command is useless; last-command is normally going to be self-insert-command, as your trace demonstrates. Note that Info-exit's last-command is in fact "info". So probably what needs to be done is for execute-extended-command to explicitly run the pre-command-hook. I'm sorry, this is going to be hard, and I'm not sure what to do. The problem is that this is a pretty major change in the behavior of pre-command-hook. I _think_ it's harmless to existing apps (who needs to know what the last command read in the minibuffer was?) but I'm not entirely sure. I assume that GNU Emacs does what you want it to do? -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.