Mercurial > emacs
changeset 83438:dc3a189e9e3a
Fix splash screen loosing input events on Emacsclient frames.
* lisp/startup.el (fancy-splash-screens): Use `overriding-local-map'
instead of `overriding-terminal-local-map' for now; the latter doesn't
work right, it looses keypresses to another terminal.
git-archimport-id: lorentey@elte.hu--2004/emacs--multi-tty--0--patch-478
| author | Karoly Lorentey <lorentey@elte.hu> |
|---|---|
| date | Fri, 30 Dec 2005 06:15:47 +0000 |
| parents | c415fd182aef |
| children | 6359ac574acf |
| files | README.multi-tty lisp/startup.el |
| diffstat | 2 files changed, 7 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/README.multi-tty Fri Dec 30 05:30:57 2005 +0000 +++ b/README.multi-tty Fri Dec 30 06:15:47 2005 +0000 @@ -401,6 +401,12 @@ THINGS TO DO ------------ +** Let-binding `overriding-terminal-local-map' on a brand new frame + does not seem to work correctly. (See `fancy-splash-screens'.) + The keymap seems to be set up right, but events go to another + terminal. Or is it `unread-command-events' that gets Emacs + confused? Investigate. + ** `delete-frame' events are handled by `special-event-map' immediately when read by `read_char'. This is fine but it prevents higher-level keymaps from binding that event to get notified of the
--- a/lisp/startup.el Fri Dec 30 05:30:57 2005 +0000 +++ b/lisp/startup.el Fri Dec 30 06:15:47 2005 +0000 @@ -1334,7 +1334,7 @@ (catch 'stop-splashing (unwind-protect (let* ((map (make-sparse-keymap)) - (overriding-terminal-local-map map) + (overriding-local-map map) ;; Catch if our frame is deleted; the delete-frame ;; event is unreliable and is handled by ;; `special-event-map' anyway.