Pipeline · emacs / emacs

Use key-translate instead of keyboard-translate

As a consequence of the discussions in Bug#65735, move to using the
new key-translate function instead of the deprecated
keyboard-translate.

For future maintainers: ?\C-? or ?\177 do not mean "DEL" with
key-translate, you have to use "DEL".

* lisp/simple.el (normal-erase-is-backspace-mode): Use key-translate.
* lisp/term/bobcat.el (terminal-init-bobcat): Use key-translate.

2 jobs for master in 107 minutes and 52 seconds (queued for 52 seconds)

095d6457

Status	Job ID	Name
Normal
failed	#75069	test-lisp-inotify	00:04:55 Oct 05, 2023
failed	#75070	test-lisp-term-inotify	01:47:50 Oct 05, 2023

	Name	Stage	Failure
failed	test-lisp-term-inotify	Normal	There has been a timeout failure or the job got stuck. Check your timeout limits or try again
	`Uploading artifacts for failed job Uploading artifacts... WARNING: test-lisp-term-inotify-095d6457/: no matching files. Ensure that the artifact path is relative to the working directory ERROR: No files to upload Uploading artifacts... WARNING: test-lisp-term-inotify-095d6457/junit-test-report.xml: no matching files. Ensure that the artifact path is relative to the working directory ERROR: No files to upload Cleaning up project directory and file based variables ERROR: Job failed: exit code 1`
failed	test-lisp-inotify	Normal
	`$ find ${test_name} ! $ -name "*.log" -o -name ${EMACS_TEST_JUNIT_REPORT} $ -type f -delete find: test-lisp-inotify-095d6457: No such file or directory Uploading artifacts... WARNING: test-lisp-inotify-095d6457/: no matching files ERROR: No files to upload Uploading artifacts... WARNING: test-lisp-inotify-095d6457/junit-test-report.xml: no matching files ERROR: No files to upload ERROR: Job failed: exit code 1`