Re: parallel bootstrap failure; _prompt_? during bootstrap build

[Eli Zaretskii <eliz@gnu.org>]

> From: Andreas Schwab <schwab@suse.de>
> Cc: emacs-devel@gnu.org
> Date: Sun, 18 Nov 2007 20:57:46 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > On many X installations, keyboard input does not need encoded-kb, it
> > uses X keysyms (as I'm sure you know).
> 
> Please read the comment in set-locale-environment.

Really, Andreas, you should try be friendlier with your responses some
day.  It's not a crime to not know something about the latest changes
to Emacs which turn upside down long established memories.

To everybody else who are not in the know: It's the multi-tty change
strikes again: it turns out set-locale-environment was modified to
_always_ set the keyboard encoding:

	  ;; Set the `keyboard-coding-system' if appropriate (tty
	  ;; only).  At least X and MS Windows can generate
	  ;; multilingual input.
	  ;; XXX This was disabled unless `window-system', but that
	  ;; leads to buggy behaviour when a tty frame is opened
	  ;; later.  Setting the keyboard coding system has no adverse
	  ;; effect on X, so let's do it anyway. -- Lorentey
	  (let ((kcs (or coding-system
			 (car (get-language-info language-name
						 'coding-system)))))
	    (if kcs (set-keyboard-coding-system kcs frame)))

So now I'm quite convinced we should preload encoded-kb (unless we
undo this change).