bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

1. make clean and make distclean
2. ./configure ---x-toolkit=lucid <RET>
3. make <RET>
4. src/emacs -Q <RET>
5. Remove menu-bar by eval (menu-bar-mode -1) <RET>
6. <F10>
7. popup menu appears
8. popup menu navigable via mouse but not via arrow keys.
9. End





In GNU Emacs 28.0.50 (build 1, i686-pc-linux-gnu, X toolkit, cairo version 1.14.8, Xaw3d scroll bars)
 of 2021-03-07 built on bluestar
Repository revision: 8558ecd65fc1c87345353f6352299df04280e729
Repository branch: master
System Description: Debian GNU/Linux 9 (stretch)

Configured using:
 'configure --with-x-toolkit=lucid'

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ
JPEG LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD LIBXML2 M17N_FLT MODULES
NOTIFY INOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
X11 XAW3D XDBE XIM XPM LUCID ZLIB

Important settings:
  value of $LANG: en_GB.utf8
  locale-coding-system: utf-8

Major mode: Summary

Minor modes in effect:
  gnus-mailing-list-mode: t
  recentf-mode: t
  auto-insert-mode: t
  global-emojify-mode: t
  emojify-mode: t
  xclip-mode: t
  shell-dirtrack-mode: t
  savehist-mode: t
  xterm-mouse-mode: t
  display-time-mode: t
  show-paren-mode: t
  global-eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  buffer-read-only: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
/home/redknight/git/emacs-w3m/w3m-session hides /home/redknight/.emacs.d/lisp/w3m-session
/home/redknight/.emacs.d/lisp/wc-mode hides /home/redknight/.emacs.d/lisp/misc/wc-mode
/home/redknight/.emacs.d/lisp/so-long hides /home/redknight/git/emacs/lisp/so-long
/home/redknight/git/org-mode/lisp/org-id hides /home/redknight/git/emacs/lisp/org/org-id
/home/redknight/git/org-mode/lisp/ob-gnuplot hides /home/redknight/git/emacs/lisp/org/ob-gnuplot
/home/redknight/git/org-mode/lisp/ob-eval hides /home/redknight/git/emacs/lisp/org/ob-eval
/home/redknight/git/org-mode/lisp/ol-bibtex hides /home/redknight/git/emacs/lisp/org/ol-bibtex
/home/redknight/git/org-mode/lisp/ox-latex hides /home/redknight/git/emacs/lisp/org/ox-latex
/home/redknight/git/org-mode/lisp/ob-fortran hides /home/redknight/git/emacs/lisp/org/ob-fortran
/home/redknight/git/org-mode/lisp/ob-forth hides /home/redknight/git/emacs/lisp/org/ob-forth
/home/redknight/git/org-mode/lisp/ob-ruby hides /home/redknight/git/emacs/lisp/org/ob-ruby
/home/redknight/git/org-mode/lisp/ob-stan hides /home/redknight/git/emacs/lisp/org/ob-stan
/home/redknight/git/org-mode/lisp/ob hides /home/redknight/git/emacs/lisp/org/ob
/home/redknight/git/org-mode/lisp/ob-python hides /home/redknight/git/emacs/lisp/org/ob-python
/home/redknight/git/org-mode/lisp/ol-gnus hides /home/redknight/git/emacs/lisp/org/ol-gnus
/home/redknight/git/org-mode/lisp/ob-js hides /home/redknight/git/emacs/lisp/org/ob-js
/home/redknight/git/org-mode/lisp/ob-plantuml hides /home/redknight/git/emacs/lisp/org/ob-plantuml
/home/redknight/git/org-mode/lisp/ob-vala hides /home/redknight/git/emacs/lisp/org/ob-vala
/home/redknight/git/org-mode/lisp/org-capture hides /home/redknight/git/emacs/lisp/org/org-capture
/home/redknight/git/org-mode/lisp/ox-texinfo hides /home/redknight/git/emacs/lisp/org/ox-texinfo
/home/redknight/git/org-mode/lisp/ox-odt hides /home/redknight/git/emacs/lisp/org/ox-odt
/home/redknight/git/org-mode/lisp/ob-R hides /home/redknight/git/emacs/lisp/org/ob-R
/home/redknight/git/org-mode/lisp/org-mobile hides /home/redknight/git/emacs/lisp/org/org-mobile
/home/redknight/git/org-mode/lisp/ob-calc hides /home/redknight/git/emacs/lisp/org/ob-calc
/home/redknight/git/org-mode/lisp/org-plot hides /home/redknight/git/emacs/lisp/org/org-plot
/home/redknight/git/org-mode/lisp/ob-haskell hides /home/redknight/git/emacs/lisp/org/ob-haskell
/home/redknight/git/org-mode/lisp/ob-sed hides /home/redknight/git/emacs/lisp/org/ob-sed
/home/redknight/git/org-mode/lisp/ob-ocaml hides /home/redknight/git/emacs/lisp/org/ob-ocaml
/home/redknight/git/org-mode/lisp/org-keys hides /home/redknight/git/emacs/lisp/org/org-keys
/home/redknight/git/org-mode/lisp/ob-exp hides /home/redknight/git/emacs/lisp/org/ob-exp
/home/redknight/git/org-mode/lisp/ob-C hides /home/redknight/git/emacs/lisp/org/ob-C
/home/redknight/git/org-mode/lisp/ob-ebnf hides /home/redknight/git/emacs/lisp/org/ob-ebnf
/home/redknight/git/org-mode/lisp/ob-makefile hides /home/redknight/git/emacs/lisp/org/ob-makefile
/home/redknight/git/org-mode/lisp/ol-rmail hides /home/redknight/git/emacs/lisp/org/ol-rmail
/home/redknight/git/org-mode/lisp/org-attach hides /home/redknight/git/emacs/lisp/org/org-attach
/home/redknight/git/org-mode/lisp/ob-shell hides /home/redknight/git/emacs/lisp/org/ob-shell
/home/redknight/git/org-mode/lisp/ob-mscgen hides /home/redknight/git/emacs/lisp/org/ob-mscgen
/home/redknight/git/org-mode/lisp/ob-css hides /home/redknight/git/emacs/lisp/org/ob-css
/home/redknight/git/org-mode/lisp/org-macs hides /home/redknight/git/emacs/lisp/org/org-macs
/home/redknight/git/org-mode/lisp/org-macro hides /home/redknight/git/emacs/lisp/org/org-macro
/home/redknight/git/org-mode/lisp/org-colview hides /home/redknight/git/emacs/lisp/org/org-colview
/home/redknight/git/org-mode/lisp/org-archive hides /home/redknight/git/emacs/lisp/org/org-archive
/home/redknight/git/org-mode/lisp/ol-bbdb hides /home/redknight/git/emacs/lisp/org/ol-bbdb
/home/redknight/git/org-mode/lisp/ob-octave hides /home/redknight/git/emacs/lisp/org/ob-octave
/home/redknight/git/org-mode/lisp/org-list hides /home/redknight/git/emacs/lisp/org/org-list
/home/redknight/git/org-mode/lisp/org-protocol hides /home/redknight/git/emacs/lisp/org/org-protocol
/home/redknight/git/org-mode/lisp/org-duration hides /home/redknight/git/emacs/lisp/org/org-duration
/home/redknight/git/org-mode/lisp/ob-screen hides /home/redknight/git/emacs/lisp/org/ob-screen
/home/redknight/git/org-mode/lisp/ob-matlab hides /home/redknight/git/emacs/lisp/org/ob-matlab
/home/redknight/git/org-mode/lisp/ol-w3m hides /home/redknight/git/emacs/lisp/org/ol-w3m
/home/redknight/git/org-mode/lisp/ol hides /home/redknight/git/emacs/lisp/org/ol
/home/redknight/git/org-mode/lisp/ob-java hides /home/redknight/git/emacs/lisp/org/ob-java
/home/redknight/git/org-mode/lisp/ob-perl hides /home/redknight/git/emacs/lisp/org/ob-perl
/home/redknight/git/org-mode/lisp/org-tempo hides /home/redknight/git/emacs/lisp/org/org-tempo
/home/redknight/git/org-mode/lisp/org-clock hides /home/redknight/git/emacs/lisp/org/org-clock
/home/redknight/git/org-mode/lisp/org hides /home/redknight/git/emacs/lisp/org/org
/home/redknight/git/org-mode/lisp/ob-processing hides /home/redknight/git/emacs/lisp/org/ob-processing
/home/redknight/git/org-mode/lisp/ob-sass hides /home/redknight/git/emacs/lisp/org/ob-sass
/home/redknight/git/org-mode/lisp/ox-md hides /home/redknight/git/emacs/lisp/org/ox-md
/home/redknight/git/org-mode/lisp/org-lint hides /home/redknight/git/emacs/lisp/org/org-lint
/home/redknight/git/org-mode/lisp/org-goto hides /home/redknight/git/emacs/lisp/org/org-goto
/home/redknight/git/org-mode/lisp/ob-eshell hides /home/redknight/git/emacs/lisp/org/ob-eshell
/home/redknight/git/org-mode/lisp/org-pcomplete hides /home/redknight/git/emacs/lisp/org/org-pcomplete
/home/redknight/git/org-mode/lisp/ob-picolisp hides /home/redknight/git/emacs/lisp/org/ob-picolisp
/home/redknight/git/org-mode/lisp/org-habit hides /home/redknight/git/emacs/lisp/org/org-habit
/home/redknight/git/org-mode/lisp/ob-table hides /home/redknight/git/emacs/lisp/org/ob-table
/home/redknight/git/org-mode/lisp/ox-publish hides /home/redknight/git/emacs/lisp/org/ox-publish
/home/redknight/git/org-mode/lisp/ox-beamer hides /home/redknight/git/emacs/lisp/org/ox-beamer
/home/redknight/git/org-mode/lisp/org-src hides /home/redknight/git/emacs/lisp/org/org-src
/home/redknight/git/org-mode/lisp/org-table hides /home/redknight/git/emacs/lisp/org/org-table
/home/redknight/git/org-mode/lisp/ob-lilypond hides /home/redknight/git/emacs/lisp/org/ob-lilypond
/home/redknight/git/org-mode/lisp/ox-org hides /home/redknight/git/emacs/lisp/org/ox-org
/home/redknight/git/org-mode/lisp/org-indent hides /home/redknight/git/emacs/lisp/org/org-indent
/home/redknight/git/org-mode/lisp/org-feed hides /home/redknight/git/emacs/lisp/org/org-feed
/home/redknight/git/org-mode/lisp/ox-icalendar hides /home/redknight/git/emacs/lisp/org/ox-icalendar
/home/redknight/git/org-mode/lisp/ol-info hides /home/redknight/git/emacs/lisp/org/ol-info
/home/redknight/git/org-mode/lisp/org-compat hides /home/redknight/git/emacs/lisp/org/org-compat
/home/redknight/git/org-mode/lisp/org-ctags hides /home/redknight/git/emacs/lisp/org/org-ctags
/home/redknight/git/org-mode/lisp/ob-groovy hides /home/redknight/git/emacs/lisp/org/ob-groovy
/home/redknight/git/org-mode/lisp/ob-scheme hides /home/redknight/git/emacs/lisp/org/ob-scheme
/home/redknight/git/org-mode/lisp/ob-lob hides /home/redknight/git/emacs/lisp/org/ob-lob
/home/redknight/git/org-mode/lisp/org-timer hides /home/redknight/git/emacs/lisp/org/org-timer
/home/redknight/git/org-mode/lisp/ob-ref hides /home/redknight/git/emacs/lisp/org/ob-ref
/home/redknight/git/org-mode/lisp/ob-io hides /home/redknight/git/emacs/lisp/org/ob-io
/home/redknight/git/org-mode/lisp/org-crypt hides /home/redknight/git/emacs/lisp/org/org-crypt
/home/redknight/git/org-mode/lisp/ox-ascii hides /home/redknight/git/emacs/lisp/org/ox-ascii
/home/redknight/git/org-mode/lisp/org-footnote hides /home/redknight/git/emacs/lisp/org/org-footnote
/home/redknight/git/org-mode/lisp/ob-lisp hides /home/redknight/git/emacs/lisp/org/ob-lisp
/home/redknight/git/org-mode/lisp/ob-lua hides /home/redknight/git/emacs/lisp/org/ob-lua
/home/redknight/git/org-mode/lisp/org-faces hides /home/redknight/git/emacs/lisp/org/org-faces
/home/redknight/git/org-mode/lisp/org-inlinetask hides /home/redknight/git/emacs/lisp/org/org-inlinetask
/home/redknight/git/org-mode/lisp/org-num hides /home/redknight/git/emacs/lisp/org/org-num
/home/redknight/git/org-mode/lisp/ob-maxima hides /home/redknight/git/emacs/lisp/org/ob-maxima
/home/redknight/git/org-mode/lisp/ob-tangle hides /home/redknight/git/emacs/lisp/org/ob-tangle
/home/redknight/git/org-mode/lisp/org-attach-git hides /home/redknight/git/emacs/lisp/org/org-attach-git
/home/redknight/git/org-mode/lisp/ox-man hides /home/redknight/git/emacs/lisp/org/ox-man
/home/redknight/git/org-mode/lisp/ob-ditaa hides /home/redknight/git/emacs/lisp/org/ob-ditaa
/home/redknight/git/org-mode/lisp/ob-shen hides /home/redknight/git/emacs/lisp/org/ob-shen
/home/redknight/git/org-mode/lisp/org-element hides /home/redknight/git/emacs/lisp/org/org-element
/home/redknight/git/org-mode/lisp/org-version hides /home/redknight/git/emacs/lisp/org/org-version
/home/redknight/git/org-mode/lisp/org-loaddefs hides /home/redknight/git/emacs/lisp/org/org-loaddefs
/home/redknight/git/org-mode/lisp/ob-core hides /home/redknight/git/emacs/lisp/org/ob-core
/home/redknight/git/org-mode/lisp/ob-J hides /home/redknight/git/emacs/lisp/org/ob-J
/home/redknight/git/org-mode/lisp/org-datetree hides /home/redknight/git/emacs/lisp/org/org-datetree
/home/redknight/git/org-mode/lisp/org-mouse hides /home/redknight/git/emacs/lisp/org/org-mouse
/home/redknight/git/org-mode/lisp/ol-irc hides /home/redknight/git/emacs/lisp/org/ol-irc
/home/redknight/git/org-mode/lisp/ob-abc hides /home/redknight/git/emacs/lisp/org/ob-abc
/home/redknight/git/org-mode/lisp/ob-ledger hides /home/redknight/git/emacs/lisp/org/ob-ledger
/home/redknight/git/org-mode/lisp/ob-hledger hides /home/redknight/git/emacs/lisp/org/ob-hledger
/home/redknight/git/org-mode/lisp/ob-sqlite hides /home/redknight/git/emacs/lisp/org/ob-sqlite
/home/redknight/git/org-mode/lisp/ob-org hides /home/redknight/git/emacs/lisp/org/ob-org
/home/redknight/git/org-mode/lisp/ol-docview hides /home/redknight/git/emacs/lisp/org/ol-docview
/home/redknight/git/org-mode/lisp/ob-comint hides /home/redknight/git/emacs/lisp/org/ob-comint
/home/redknight/git/org-mode/lisp/ob-emacs-lisp hides /home/redknight/git/emacs/lisp/org/ob-emacs-lisp
/home/redknight/git/org-mode/lisp/ol-eww hides /home/redknight/git/emacs/lisp/org/ol-eww
/home/redknight/git/org-mode/lisp/ob-clojure hides /home/redknight/git/emacs/lisp/org/ob-clojure
/home/redknight/git/org-mode/lisp/ox-html hides /home/redknight/git/emacs/lisp/org/ox-html
/home/redknight/git/org-mode/lisp/org-install hides /home/redknight/git/emacs/lisp/org/org-install
/home/redknight/git/org-mode/lisp/org-entities hides /home/redknight/git/emacs/lisp/org/org-entities
/home/redknight/git/org-mode/lisp/ox hides /home/redknight/git/emacs/lisp/org/ox
/home/redknight/git/org-mode/lisp/ob-sql hides /home/redknight/git/emacs/lisp/org/ob-sql
/home/redknight/git/org-mode/lisp/org-agenda hides /home/redknight/git/emacs/lisp/org/org-agenda
/home/redknight/git/org-mode/lisp/ol-mhe hides /home/redknight/git/emacs/lisp/org/ol-mhe
/home/redknight/git/org-mode/lisp/ol-eshell hides /home/redknight/git/emacs/lisp/org/ol-eshell
/home/redknight/git/org-mode/lisp/ob-awk hides /home/redknight/git/emacs/lisp/org/ob-awk
/home/redknight/git/org-mode/lisp/ob-dot hides /home/redknight/git/emacs/lisp/org/ob-dot
/home/redknight/git/org-mode/lisp/ob-latex hides /home/redknight/git/emacs/lisp/org/ob-latex
/home/redknight/git/org-mode/lisp/org-refile hides /home/redknight/git/emacs/lisp/org/org-refile
/home/redknight/git/org-mode/lisp/ob-coq hides /home/redknight/git/emacs/lisp/org/ob-coq
/home/redknight/git/org-mode/lisp/ob-asymptote hides /home/redknight/git/emacs/lisp/org/ob-asymptote

Features:
(shadow mailalias emacsbug qp mule-util gnus-gravatar gravatar dns
cl-extra sort smiley gnus-cite mail-extr gnus-async gnus-bcklg gnus-ml
gnus-topic mm-archive url-http url-gw url-cache url-auth url-handlers
utf-7 nnrss mm-url nndraft nnmh nnml executable time-stamp bbdb-gnus
bbdb-message sendmail epa-file gnutls network-stream nsm gnus-agent
gnus-srvr gnus-score score-mode nnvirtual gnus-msg nntp gnus-cache
gnus-article-treat-patch diff-mode gnus-registry registry eieio-base
gnus-icalendar org-capture icalendar diary-lib diary-loaddefs gnus-art
mm-uu mml2015 mm-view mml-smime smime dig gnus-sum shr kinsoku svg dom
browse-url gnus-group gnus-undo gnus-fun gnus-start gnus-dbus dbus xml
gnus-cloud nnimap nnmail mail-source utf7 nnoo gnus-spec gnus-int
gnus-range message rmc puny rfc822 mml mml-sec epa epg epg-config
mm-decode mm-bodies mm-encode mail-parse rfc2231 gmm-utils mailheader
gnus-win gnus nnheader gnus-util rmail rmail-loaddefs rfc2047 rfc2045
ietf-drums mail-utils mm-util mail-prsvr term/xterm xterm flyspell
simple-dark-theme ibuffer ibuffer-loaddefs bookmark recentf
tree-widget autoinsert printing ps-print ps-print-loaddefs ps-def lpr
url url-proxy url-privacy url-expand url-methods url-history
url-cookie url-domsuf url-util mailcap ssh ovpn-mode netrc auto-loads
tex-site image-dired+ help-mode dired+ image-dired image-mode exif
image-file image-converter dired-x dired-aux muse-texinfo texnfo-upd
texinfo muse-latex muse-html muse-xml-common muse-publish muse-project
muse-protocols info muse-regexps muse muse-nested-tags muse-mode
page-break-lines ox-bibtex ox-texinfo reftex-cite reftex
reftex-loaddefs reftex-vars org-screenshot emojify apropos tar-mode
arc-mode archive-mode ht dash iimage ob-sqlite ob-shell ob-ruby ob-R
ob-python python tramp-sh tramp tramp-loaddefs trampver
tramp-integration files-x tramp-compat parse-time iso8601 ls-lisp
ob-plantuml ob-org ob-perl ob-lisp ob-latex ob-gnuplot ob-fortran
ob-eshell eshell esh-cmd esh-ext esh-opt esh-proc esh-io esh-arg
esh-module esh-groups esh-util ob-dot ob-ditaa ob-calc calc-store
calc-trail calc-ext calc calc-loaddefs calc-macs ob-C cc-mode cc-fonts
cc-guess cc-menus cc-cmds ob-awk org-crypt ido ox-epub ox-odt rng-loc
rng-uri rng-parse rng-match rng-dt rng-util rng-pttrn nxml-parse
nxml-ns nxml-enc xmltok nxml-util ox-latex ox-icalendar ox-html table
ox-ascii ox-publish ox org-element avl-tree org-habit org-agenda
org-refile org ob ob-tangle ob-ref ob-lob ob-table ob-exp org-macro
org-footnote org-src ob-comint org-pcomplete org-list org-faces
org-entities time-date noutline outline org-version ob-emacs-lisp
ob-core ob-eval org-table ol org-keys org-compat org-macs org-loaddefs
format-spec find-func cal-menu calendar cal-loaddefs wc-mode xclip
bbdb-mua bbdb-com crm mailabbrev bbdb bbdb-site timezone bbdb-loaddefs
insert-shebang ggtags hippie-exp edmacro kmacro easy-mmode derived
pcase etags fileloop generator xref project ewoc url-parse auth-source
cl-seq eieio eieio-core cl-macs eieio-loaddefs password-cache json
subr-x map seq byte-opt bytecomp byte-compile cconv url-vars xcscope
lusty-explorer dired dired-loaddefs htmlize cl gv multi-term term
disp-table shell pcomplete ehelp synonyms mairix ftnchek-mode compile
text-property-search fortran cus-edit pp wid-edit cc-styles cc-align
cc-engine cc-vars cc-defs cpan comint ansi-color ring savehist ispell
xt-mouse time so-long linum-ex isearch+ isearch-prop thingatpt+
thingatpt color advice heaven-and-hell paren cus-start cus-load
slime-autoloads cl-loaddefs cl-lib early-init iso-transl tooltip eldoc
electric uniquify ediff-hook vc-hooks lisp-float-type mwheel
term/x-win x-win term/common-win x-dnd tool-bar dnd fontset image
regexp-opt fringe tabulated-list replace newcomment text-mode
elisp-mode lisp-mode prog-mode register page tab-bar menu-bar
rfn-eshadow isearch easymenu timer select scroll-bar mouse jit-lock
font-lock syntax facemenu font-core term/tty-colors frame minibuffer
cl-generic cham georgian utf-8-lang misc-lang vietnamese tibetan thai
tai-viet lao korean japanese eucjp-ms cp51932 hebrew greek romanian
slovak czech european ethiopic indian cyrillic chinese composite
charscript charprop case-table epa-hook jka-cmpr-hook help simple
abbrev obarray cl-preloaded nadvice button loaddefs faces cus-face
macroexp files window text-properties overlay sha1 md5 base64 format
env code-pages mule custom widget hashtable-print-readable backquote
threads dbusbind inotify lcms2 dynamic-setting system-font-setting
font-render-setting cairo x-toolkit x multi-tty make-network-process
emacs)

Memory information:
((conses 8 540719 74183)
 (symbols 24 44927 95)
 (strings 16 237212 11449)
 (string-bytes 1 8153531)
 (vectors 8 95045)
 (vector-slots 4 3052470 73806)
 (floats 8 693 1036)
 (intervals 28 917 309)
 (buffers 564 33))

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[martin rudalics]

 > 1. make clean and make distclean
 > 2. ./configure ---x-toolkit=lucid <RET>
 > 3. make <RET>
 > 4. src/emacs -Q <RET>
 > 5. Remove menu-bar by eval (menu-bar-mode -1) <RET>
 > 6. <F10>
 > 7. popup menu appears
 > 8. popup menu navigable via mouse but not via arrow keys.
 > 9. End
 >
 >
 >
 >
 >
 > In GNU Emacs 28.0.50 (build 1, i686-pc-linux-gnu, X toolkit, cairo version 1.14.8, Xaw3d scroll bars)
 >   of 2021-03-07 built on bluestar
 > Repository revision: 8558ecd65fc1c87345353f6352299df04280e729
 > Repository branch: master
 > System Description: Debian GNU/Linux 9 (stretch)
 >
 > Configured using:
 >   'configure --with-x-toolkit=lucid'

Works here but is broken for motif.  If the breakage is recent, you will
have to bisect.

martin

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> martin rudalics <rudalics@gmx.at> writes:

    >> 1. make clean and make distclean 2. ./configure
    >> ---x-toolkit=lucid <RET> 3. make <RET> 4. src/emacs -Q <RET>
    >> 5. Remove menu-bar by eval (menu-bar-mode -1) <RET> 6. <F10>
    >> 7. popup menu appears 8. popup menu navigable via mouse but not
    >> via arrow keys.  9. End
    >> 
    >> 
    >> 
    >> 
    >> 
    >> In GNU Emacs 28.0.50 (build 1, i686-pc-linux-gnu, X toolkit,
    >> cairo version 1.14.8, Xaw3d scroll bars) of 2021-03-07 built on
    >> bluestar Repository revision:
    >> 8558ecd65fc1c87345353f6352299df04280e729 Repository branch:
    >> master System Description: Debian GNU/Linux 9 (stretch)
    >> 
    >> Configured using: 'configure --with-x-toolkit=lucid'

    > Works here but is broken for motif.  If the breakage is recent,
    > you will have to bisect.

Thanks. Rather than bisect I cloned a fresh emacs. I still get the same
issue: menu works with mouse but not arrow keys. What would a bisect do
that a fresh clone doesn't?

Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Basil L. Contovounesios]

Colin Baxter <m43cap@yandex.com> writes:

> In GNU Emacs 28.0.50 (build 1, i686-pc-linux-gnu, X toolkit, cairo version 1.14.8, Xaw3d scroll bars)
>  of 2021-03-07 built on bluestar
> Repository revision: 8558ecd65fc1c87345353f6352299df04280e729
> Repository branch: master
> System Description: Debian GNU/Linux 9 (stretch)
>
> Configured using:
>  'configure --with-x-toolkit=lucid'

Just curious: how come this doesn't list your 'Windowing system
distributor' (which in my case is X.Org 11), when your features below
include X11?  Do you need to configure '--with-x' or something?

> Configured features:
> ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ
> JPEG LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD LIBXML2 M17N_FLT MODULES
> NOTIFY INOTIFY PDUMPER PNG RSVG SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
> X11 XAW3D XDBE XIM XPM LUCID ZLIB
>
> Important settings:
>   value of $LANG: en_GB.utf8
>   locale-coding-system: utf-8

Apart from that, the only possibly significant differences I see from my
configuration of Emacs 28[1] are: I'm on x86_64, with a more recent
version of Debian and Cairo, and 'value of $XMODIFIERS: @im=ibus'.  So
I'm not sure what's going on.

[1]: https://lists.gnu.org/r/emacs-devel/2021-03/msg00359.html

-- 
Basil

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Basil L Contovounesios <contovob@tcd.ie> writes:

    > Colin Baxter <m43cap@yandex.com> writes:
    >> In GNU Emacs 28.0.50 (build 1, i686-pc-linux-gnu, X toolkit,
    >> cairo version 1.14.8, Xaw3d scroll bars) of 2021-03-07 built on
    >> bluestar Repository revision:
    >> 8558ecd65fc1c87345353f6352299df04280e729 Repository branch:
    >> master System Description: Debian GNU/Linux 9 (stretch)
    >> 
    >> Configured using: 'configure --with-x-toolkit=lucid'

    > Just curious: how come this doesn't list your 'Windowing system
    > distributor' (which in my case is X.Org 11), when your features
    > below include X11?  Do you need to configure '--with-x' or
    > something?
    
I'm tried this but get the same result.

    >> Configured features: ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS
    >> GPM GSETTINGS HARFBUZZ JPEG LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD
    >> LIBXML2 M17N_FLT MODULES NOTIFY INOTIFY PDUMPER PNG RSVG SOUND
    >> THREADS TIFF TOOLKIT_SCROLL_BARS X11 XAW3D XDBE XIM XPM LUCID
    >> ZLIB
    >> 
    >> Important settings: value of $LANG: en_GB.utf8
    >> locale-coding-system: utf-8

    > Apart from that, the only possibly significant differences I see
    > from my configuration of Emacs 28[1] are: I'm on x86_64, with a
    > more recent version of Debian and Cairo, and 'value of
    > $XMODIFIERS: @im=ibus'.  So I'm not sure what's going on.

It does look as if something changed between pretests 1, 2. Pretest 2 has
the same issue as emacs-28 - I'm not certain, but I think pretest 1
didn't. Unfortunately, I deleted pretest 1!

Perhaps the fact that I'm on 32 bits is significant. I don't have any
more time today to look at this, but I will later in the week.

Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Glenn Morris]

FWIW I can reproduce this in the emacs-27 (and master) branch on 64-bit
RHEL and Debian, but so far it disappears when bisecting.
I don't see it in installed 26.{1,2,3} or 27.1, but I do in an old
uninstalled emacs-26 branch build.
Weird.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Glenn Morris <rgm@gnu.org> writes:

    > FWIW I can reproduce this in the emacs-27 (and master) branch on
    > 64-bit RHEL and Debian, but so far it disappears when bisecting.
    > I don't see it in installed 26.{1,2,3} or 27.1, but I do in an old
    > uninstalled emacs-26 branch build.  Weird.

I have compiled my emacs-27.1 with lucid and the effect does not
occur. I can navigate menus with arrow keys and mouse.

Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> From: Colin Baxter <m43cap@yandex.com>
> Date: Wed, 10 Mar 2021 18:59:19 +0000
> Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, , 46990@debbugs.gnu.org
> 
> >>>>> Glenn Morris <rgm@gnu.org> writes:
> 
>     > FWIW I can reproduce this in the emacs-27 (and master) branch on
>     > 64-bit RHEL and Debian, but so far it disappears when bisecting.
>     > I don't see it in installed 26.{1,2,3} or 27.1, but I do in an old
>     > uninstalled emacs-26 branch build.  Weird.
> 
> I have compiled my emacs-27.1 with lucid and the effect does not
> occur. I can navigate menus with arrow keys and mouse.

Thanks.  Does that mean the problem started between 27.1 and 27.1.91?
If so, can you please bisect between these two points?

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> From: Colin Baxter <m43cap@yandex.com>
> Date: Mon, 08 Mar 2021 14:29:22 +0000
> Cc: , 46990@debbugs.gnu.org
> 
> It does look as if something changed between pretests 1, 2. Pretest 2 has
> the same issue as emacs-28 - I'm not certain, but I think pretest 1
> didn't. Unfortunately, I deleted pretest 1!
> 
> Perhaps the fact that I'm on 32 bits is significant. I don't have any
> more time today to look at this, but I will later in the week.

Can you or someone who sees the problem please bisect this?  I'm
delaying the release of Emacs 27.2 in the hope that we could fix it,
if indeed this was introduced between 27.1.90 and 27.1.91.

FWIW, I've reviewed all the commits between the 2 pretests, and
couldn't spot any change which could have any effect on how menus
work.

TIA

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

    >> From: Colin Baxter <m43cap@yandex.com> Date: Mon, 08 Mar 2021
    >> 14:29:22 +0000 Cc: , 46990@debbugs.gnu.org
    >> 
    >> It does look as if something changed between pretests 1,
    >> 2. Pretest 2 has the same issue as emacs-28 - I'm not certain,
    >> but I think pretest 1 didn't. Unfortunately, I deleted pretest 1!
    >> 
    >> Perhaps the fact that I'm on 32 bits is significant. I don't have
    >> any more time today to look at this, but I will later in the
    >> week.

    > Can you or someone who sees the problem please bisect this?  I'm
    > delaying the release of Emacs 27.2 in the hope that we could fix
    > it, if indeed this was introduced between 27.1.90 and 27.1.91.

I may be guilty of crying wolf when there is none. If I configure the
27.1.91 pretest for lucid and "make", the effect does occur on launching
emacs via src/emacs. However if I go the next step and "make install",
the effect does not occur when I launch the installed emacs. I 
will double-check this by installing from the git master branch and
report back.

I am sorry. I stupidly assumed launching emacs from an src directory
would give the same beast as launching from the installed bin directory.


Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> From: Colin Baxter <m43cap@yandex.com>
> Cc: contovob@tcd.ie,  ,  46990@debbugs.gnu.org
> Date: Wed, 10 Mar 2021 19:39:23 +0000
> 
>     > Can you or someone who sees the problem please bisect this?  I'm
>     > delaying the release of Emacs 27.2 in the hope that we could fix
>     > it, if indeed this was introduced between 27.1.90 and 27.1.91.
> 
> I may be guilty of crying wolf when there is none. If I configure the
> 27.1.91 pretest for lucid and "make", the effect does occur on launching
> emacs via src/emacs. However if I go the next step and "make install",
> the effect does not occur when I launch the installed emacs. I 
> will double-check this by installing from the git master branch and
> report back.
> 
> I am sorry. I stupidly assumed launching emacs from an src directory
> would give the same beast as launching from the installed bin directory.

No need to be sorry: your assumption was correct.  Emacs should
generally work the same when you run it uninstalled.  It is strange
that it doesn't in this case.

It is true that the fact the problem doesn't happen in the installed
Emacs makes the problem less serious.  But since we don't really
understand why it happens in the uninstalled Emacs, we cannot
guarantee that it will never happen in an installed one, either.  So
if you can afford bisecting this, or debugging it further, I'd
appreciate any additional information you could dig out.  Ideally, we
should at least understand why this happens, before we decide whether
it should delay the release.

Thanks.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Eli Zaretskii <eliz@gnu.org> writes:

    >> From: Colin Baxter <m43cap@yandex.com> Cc: contovob@tcd.ie, ,
    >> 46990@debbugs.gnu.org Date: Wed, 10 Mar 2021 19:39:23 +0000
    >> 
    >> > Can you or someone who sees the problem please bisect this?
    >> I'm > delaying the release of Emacs 27.2 in the hope that we
    >> could fix > it, if indeed this was introduced between 27.1.90 and
    >> 27.1.91.
    >> 
    >> I may be guilty of crying wolf when there is none. If I configure
    >> the 27.1.91 pretest for lucid and "make", the effect does occur
    >> on launching emacs via src/emacs. However if I go the next step
    >> and "make install", the effect does not occur when I launch the
    >> installed emacs. I will double-check this by installing from the
    >> git master branch and report back.
    >> 
    >> I am sorry. I stupidly assumed launching emacs from an src
    >> directory would give the same beast as launching from the
    >> installed bin directory.

I can now confirm that if I install the git master branch and launch
emacs from the installed bin directory, I can navigate the lucid
menu-bar via the arrow keys and the mouse. However if I launch emacs from
the git/src directory then I can not navigate the menu-bar via the
arrow keys. I can only navigate via the mouse.

It also explains why I thought the effect only occurred in the second
pre-test and not the first. I remember that I installed the first but
not the second.

    > No need to be sorry: your assumption was correct.  Emacs should
    > generally work the same when you run it uninstalled.  It is
    > strange that it doesn't in this case.

    > It is true that the fact the problem doesn't happen in the
    > installed Emacs makes the problem less serious.  But since we
    > don't really understand why it happens in the uninstalled Emacs,
    > we cannot guarantee that it will never happen in an installed one,
    > either.

It could an artefact of my system: 4.9.0-14-686-pae #1 SMP Debian
4.9.246-2 (2020-12-17) i686 GNU/Linux. Perhaps someone needs to confirm
the finding on a different system.

    > So if you can afford bisecting this, or debugging it
    > further, I'd appreciate any additional information you could dig
    > out.  Ideally, we should at least understand why this happens,
    > before we decide whether it should delay the release.

I'm not confident I can bisect, having never done it. It depends on the
available times, though, but certainly I will try.

Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> From: Colin Baxter <m43cap@yandex.com>
> Cc: contovob@tcd.ie,  46990@debbugs.gnu.org
> Date: Wed, 10 Mar 2021 20:30:55 +0000
> 
> I can now confirm that if I install the git master branch and launch
> emacs from the installed bin directory, I can navigate the lucid
> menu-bar via the arrow keys and the mouse. However if I launch emacs from
> the git/src directory then I can not navigate the menu-bar via the
> arrow keys. I can only navigate via the mouse.
> 
> It also explains why I thought the effect only occurred in the second
> pre-test and not the first. I remember that I installed the first but
> not the second.

Thanks, things are more clear now.

> I'm not confident I can bisect, having never done it. It depends on the
> available times, though, but certainly I will try.

Thank you.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Gregory Heytings]

>>> Can you or someone who sees the problem please bisect this?  I'm 
>>> delaying the release of Emacs 27.2 in the hope that we could fix it, 
>>> if indeed this was introduced between 27.1.90 and 27.1.91.
>>
>> I may be guilty of crying wolf when there is none. If I configure the 
>> 27.1.91 pretest for lucid and "make", the effect does occur on 
>> launching emacs via src/emacs. However if I go the next step and "make 
>> install", the effect does not occur when I launch the installed emacs. 
>> I will double-check this by installing from the git master branch and 
>> report back.
>>
>> I am sorry. I stupidly assumed launching emacs from an src directory 
>> would give the same beast as launching from the installed bin 
>> directory.
>
> No need to be sorry: your assumption was correct.  Emacs should 
> generally work the same when you run it uninstalled.  It is strange that 
> it doesn't in this case.
>

It seems that what Colin describes is an old (and indeed strange) 
behavior.  I just tried (on Debian GNU/Linux) various revisions of the 
trunk (up to 5b464a9cea from three years ago), and with 
--with-x-toolkit=lucid the menu cannot be navigated with arrow keys with 
an uninstalled emacs, and can be navigated with an installed one.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> Date: Wed, 10 Mar 2021 23:34:46 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: 46990@debbugs.gnu.org
> 
> > No need to be sorry: your assumption was correct.  Emacs should 
> > generally work the same when you run it uninstalled.  It is strange that 
> > it doesn't in this case.
> 
> It seems that what Colin describes is an old (and indeed strange) 
> behavior.  I just tried (on Debian GNU/Linux) various revisions of the 
> trunk (up to 5b464a9cea from three years ago), and with 
> --with-x-toolkit=lucid the menu cannot be navigated with arrow keys with 
> an uninstalled emacs, and can be navigated with an installed one.

Thanks.  This means there's no need to delay the release of Emacs
27.2.  I'd still like to understand why the different behavior, but
what you say means bisection is not an effective means of finding the
culprit; instead, we should debug this as with any other bug.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Gregory Heytings <gregory@heytings.org> writes:

    >>>> Can you or someone who sees the problem please bisect this?
    >>>> I'm delaying the release of Emacs 27.2 in the hope that we
    >>>> could fix it, if indeed this was introduced between 27.1.90 and
    >>>> 27.1.91.
    >>> 
    >>> I may be guilty of crying wolf when there is none. If I
    >>> configure the 27.1.91 pretest for lucid and "make", the effect
    >>> does occur on launching emacs via src/emacs. However if I go the
    >>> next step and "make install", the effect does not occur when I
    >>> launch the installed emacs. I will double-check this by
    >>> installing from the git master branch and report back.
    >>> 
    >>> I am sorry. I stupidly assumed launching emacs from an src
    >>> directory would give the same beast as launching from the
    >>> installed bin directory.
    >> 
    >> No need to be sorry: your assumption was correct.  Emacs should
    >> generally work the same when you run it uninstalled.  It is
    >> strange that it doesn't in this case.
    >> 

    > It seems that what Colin describes is an old (and indeed strange)
    > behavior.  I just tried (on Debian GNU/Linux) various revisions of
    > the trunk (up to 5b464a9cea from three years ago), and with
    > --with-x-toolkit=lucid the menu cannot be navigated with arrow
    > keys with an uninstalled emacs, and can be navigated with an
    > installed one.

Investigating further, I find that if I launch a lucid "emacs-28" via

src/temacs -Q

and evaluate (menu-bar-mode -1) then the popup menu, formed from <f10>,
does indeed allow navigation from the arrow keys (as well as the
mouse). Only launching "emacs-28" from the following

1. src/emacs -Q
2. src/bootstrap-emacs -Q
3. src/emacs-28.0.50.1 -Q

fails to allow the popup menu-bar to be navigable from the arrow keys.


I hope this helps.

Best wishes,

Colin Baxter.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Gregory Heytings <gregory@heytings.org> writes:
    >>>>> Can you or someone who sees the problem please bisect this?
    >>>>> I'm delaying the release of Emacs 27.2 in the hope that we
    >>>>> could fix it, if indeed this was introduced between 27.1.90
    >>>>> and 27.1.91.
    >>>> 
    >>>> I may be guilty of crying wolf when there is none. If I
    >>>> configure the 27.1.91 pretest for lucid and "make", the effect
    >>>> does occur on launching emacs via src/emacs. However if I go
    >>>> the next step and "make install", the effect does not occur
    >>>> when I launch the installed emacs. I will double-check this by
    >>>> installing from the git master branch and report back.
    >>>> 
    >>>> I am sorry. I stupidly assumed launching emacs from an src
    >>>> directory would give the same beast as launching from the
    >>>> installed bin directory.
    >>> 
    >>> No need to be sorry: your assumption was correct.  Emacs should
    >>> generally work the same when you run it uninstalled.  It is
    >>> strange that it doesn't in this case.
    >>> 

    >> It seems that what Colin describes is an old (and indeed strange)
    >> behavior.  I just tried (on Debian GNU/Linux) various revisions
    >> of the trunk (up to 5b464a9cea from three years ago), and with
    >> --with-x-toolkit=lucid the menu cannot be navigated with arrow
    >> keys with an uninstalled emacs, and can be navigated with an
    >> installed one.

    Colin> Investigating further, I find that if I launch a lucid
    Colin> "emacs-28" via

    Colin> src/temacs -Q

    Colin> and evaluate (menu-bar-mode -1) then the popup menu, formed
    Colin> from <f10>, does indeed allow navigation from the arrow keys
    Colin> (as well as the mouse). Only launching "emacs-28" from the
    Colin> following

    Colin> 1. src/emacs -Q 2. src/bootstrap-emacs -Q
    Colin> 3. src/emacs-28.0.50.1 -Q

    Colin> fails to allow the popup menu-bar to be navigable from the
    Colin> arrow keys.


If I miss out the batch option and make an emacs by

./temacs -l loadup --temacs=pdump

then ./emacs -Q will allow the popup menu to be navigable via the arrow
keys.

This is about as far as my knowledge will allow. I will leave it to
others to decide what it all means.

Best wishes,

Colin Baxter.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> From: Colin Baxter <m43cap@yandex.com>
> Date: Thu, 11 Mar 2021 13:23:26 +0000
> 
>     Colin> Investigating further, I find that if I launch a lucid
>     Colin> "emacs-28" via
> 
>     Colin> src/temacs -Q
> 
>     Colin> and evaluate (menu-bar-mode -1) then the popup menu, formed
>     Colin> from <f10>, does indeed allow navigation from the arrow keys
>     Colin> (as well as the mouse). Only launching "emacs-28" from the
>     Colin> following
> 
>     Colin> 1. src/emacs -Q 2. src/bootstrap-emacs -Q
>     Colin> 3. src/emacs-28.0.50.1 -Q
> 
>     Colin> fails to allow the popup menu-bar to be navigable from the
>     Colin> arrow keys.
> 
> 
> If I miss out the batch option and make an emacs by
> 
> ./temacs -l loadup --temacs=pdump
> 
> then ./emacs -Q will allow the popup menu to be navigable via the arrow
> keys.

This could point to the portable dumper as the culprit (more
accurately, something we do wrongly when producing the pdmp file), but
then why does the installed Emacs behave correctly: it also starts
from the same pdmp file as when you invoke it uninstalled.  Hmm...

Thanks for the data points, anyway.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Gregory Heytings]

>
> This could point to the portable dumper as the culprit (more accurately, 
> something we do wrongly when producing the pdmp file),
>

No, because this behavior predates the portable dumper.  In the previous 
test I went back to revision 5b464a9cea of the trunk three years ago; now 
I went a bit further and the same behavior is also present in 62e170072e 
six years ago.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> Date: Thu, 11 Mar 2021 14:25:52 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: 46990@debbugs.gnu.org
> 
> > This could point to the portable dumper as the culprit (more accurately, 
> > something we do wrongly when producing the pdmp file),
> 
> No, because this behavior predates the portable dumper.  In the previous 
> test I went back to revision 5b464a9cea of the trunk three years ago; now 
> I went a bit further and the same behavior is also present in 62e170072e 
> six years ago.

OK, thanks.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

Colin Baxter <m43cap@yandex.com> writes:

> Investigating further, I find that if I launch a lucid "emacs-28" via
>
> src/temacs -Q
>
> and evaluate (menu-bar-mode -1) then the popup menu, formed from <f10>,
> does indeed allow navigation from the arrow keys (as well as the
> mouse). Only launching "emacs-28" from the following
>
> 1. src/emacs -Q
> 2. src/bootstrap-emacs -Q
> 3. src/emacs-28.0.50.1 -Q
>
> fails to allow the popup menu-bar to be navigable from the arrow keys.

This problem is still present on the current trunk.

There's also other oddities between src/emacs and src/temacs.  With
src/temacs, the menu bar looks fine:


[-- Attachment #2: Type: image/png, Size: 22578 bytes --]

[-- Attachment #3: Type: text/plain, Size: 37 bytes --]


with src/emacs it looks like this:


[-- Attachment #4: Type: image/png, Size: 24762 bytes --]

[-- Attachment #5: Type: text/plain, Size: 382 bytes --]


So the background colour for the face used on the menu bar went missing.
So could we be missing something in ... loadup.el or something?

Hm...  no, the `menu' face is the same in both instances.

Anybody know where I should be poking to debug these possibly unrelated
issues?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> There's also other oddities between src/emacs and src/temacs.  With
> src/temacs, the menu bar looks fine:

X resources are not enabled in temacs.

> with src/emacs it looks like this:

So you have something in your X resources that sets the menu bar
background to black.

> Anybody know where I should be poking to debug these possibly unrelated
> issues?

I suggest looking in `xrdb -query', though if something shows up there
it isn't a bug.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Po Lu <luangruo@yahoo.com> writes:

>> with src/emacs it looks like this:
>
> So you have something in your X resources that sets the menu bar
> background to black.

Ah, yes.  I have:

emacs*background:	black

But I'm starting emacs with -Q, which should make Emacs ignore that.
But it doesn't for the menu bar?  (It ignores it for everything else.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> But I'm starting emacs with -Q, which should make Emacs ignore that.
> But it doesn't for the menu bar?  (It ignores it for everything else.)

It doesn't, since `inhibit-x-resources' doesn't control what the toolkit
does.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Po Lu <luangruo@yahoo.com> writes:

>> But I'm starting emacs with -Q, which should make Emacs ignore that.
>> But it doesn't for the menu bar?  (It ignores it for everything else.)
>
> It doesn't, since `inhibit-x-resources' doesn't control what the toolkit
> does.

I guess that makes sense on some level -- -Q doesn't control what Gtk
does with the toolbar, for instance.  It's still somewhat odd-looking
for Lucid -- is there any way we can stop it from consulting the X
resources, or is that completely out of our hands?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I guess that makes sense on some level -- -Q doesn't control what Gtk
> does with the toolbar, for instance.  It's still somewhat odd-looking
> for Lucid -- is there any way we can stop it from consulting the X
> resources, or is that completely out of our hands?

It can, but I'd rather not go down the rabbit hole of modifying the
behavior of xrdb.c based on the value of `inhibit-x-resources'.

Different versions of Xlib have different bugs in that area, just look
at this mess in xterm.c:

      /* Whether or not XCloseDisplay destroys the associated resource
	 database depends on the version of libX11.  To avoid both
	 crash and memory leak, we dissociate the database from the
	 display and then destroy dpyinfo->rdb ourselves.

	 Unfortunately, the above strategy does not work in some
	 situations due to a bug in newer versions of libX11: because
	 XrmSetDatabase doesn't clear the flag XlibDisplayDfltRMDB if
	 dpy->db is NULL, XCloseDisplay destroys the associated
	 database whereas it has not been created by XGetDefault
	 (Bug#21974 in freedesktop.org Bugzilla).  As a workaround, we
	 don't destroy the database here in order to avoid the crash
	 in the above situations for now, though that may cause memory
	 leaks in other situations.  */
#if false
#ifdef HAVE_XRMSETDATABASE
      XrmSetDatabase (dpyinfo->display, NULL);
#else
      dpyinfo->display->db = NULL;
#endif
      /* We used to call XrmDestroyDatabase from x_delete_display, but
	 some older versions of libX11 crash if we call it after
	 closing all the displays.  */
      XrmDestroyDatabase (dpyinfo->rdb);
#endif

Besides, it would be slightly more annoying to debug the Lucid toolkit
that way.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Po Lu <luangruo@yahoo.com> writes:

> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> I guess that makes sense on some level -- -Q doesn't control what Gtk
>> does with the toolbar, for instance.  It's still somewhat odd-looking
>> for Lucid -- is there any way we can stop it from consulting the X
>> resources, or is that completely out of our hands?
>
> It can, but I'd rather not go down the rabbit hole of modifying the
> behavior of xrdb.c based on the value of `inhibit-x-resources'.

xrdb.c already uses that:

const char *
x_get_string_resource (void *v_rdb, const char *name, const char *class)
{
[...]
  if (inhibit_x_resources)
    /* --quick was passed, so this is a no-op.  */
    return NULL;

But I guess the Lucid calls are via a different path?  (I'm having
issues with trying to follow the call sequence here...)  I'm not sure
whether the Lucid stuff goes through xrdb.c at all?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> const char *
> x_get_string_resource (void *v_rdb, const char *name, const char *class)
> {
> [...]
>   if (inhibit_x_resources)
>     /* --quick was passed, so this is a no-op.  */
>     return NULL;
>
> But I guess the Lucid calls are via a different path?  (I'm having
> issues with trying to follow the call sequence here...)  I'm not sure
> whether the Lucid stuff goes through xrdb.c at all?

No, it doesn't.  It uses whatever database was set as the default for
the display connection, see x_load_resources and what is currently line
26337 of xterm.c:

#ifdef HAVE_XRMSETDATABASE
  XrmSetDatabase (dpyinfo->display, xrdb);
#else
  dpyinfo->display->db = xrdb;
#endif

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Po Lu <luangruo@yahoo.com> writes:

> No, it doesn't.  It uses whatever database was set as the default for
> the display connection, see x_load_resources and what is currently line
> 26337 of xterm.c:
>
> #ifdef HAVE_XRMSETDATABASE
>   XrmSetDatabase (dpyinfo->display, xrdb);
> #else
>   dpyinfo->display->db = xrdb;
> #endif

Ah; thanks.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

Thank you all for this. It works well. I can enjoy Lucid emacs without
having to "make install".

Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Colin Baxter <m43cap@yandex.com> writes:

> 1. make clean and make distclean
> 2. ./configure ---x-toolkit=lucid <RET>
> 3. make <RET>
> 4. src/emacs -Q <RET>
> 5. Remove menu-bar by eval (menu-bar-mode -1) <RET>
> 6. <F10>
> 7. popup menu appears
> 8. popup menu navigable via mouse but not via arrow keys.
> 9. End

I thought that was fixed a while ago.  It works for me here on both core
input and XInput 2, so I don't know what could be going on.

Do you have anything set up that could be overriding the following
translations?

static char
xlwMenuTranslations [] =
"<BtnDown>:	  start()\n\
<Motion>:	  drag()\n\
<BtnUp>:	  select()\n\
<Key>Shift_L:     nothing()\n\
<Key>Shift_R:     nothing()\n\
<Key>Meta_L:      nothing()\n\
<Key>Meta_R:      nothing()\n\
<Key>Control_L:   nothing()\n\
<Key>Control_R:   nothing()\n\
<Key>Hyper_L:     nothing()\n\
<Key>Hyper_R:     nothing()\n\
<Key>Super_L:     nothing()\n\
<Key>Super_R:     nothing()\n\
<Key>Alt_L:       nothing()\n\
<Key>Alt_R:       nothing()\n\
<Key>Caps_Lock:   nothing()\n\
<Key>Shift_Lock:  nothing()\n\
<KeyUp>Shift_L:   nothing()\n\
<KeyUp>Shift_R:   nothing()\n\
<KeyUp>Meta_L:    nothing()\n\
<KeyUp>Meta_R:    nothing()\n\
<KeyUp>Control_L: nothing()\n\
<KeyUp>Control_R: nothing()\n\
<KeyUp>Hyper_L:   nothing()\n\
<KeyUp>Hyper_R:   nothing()\n\
<KeyUp>Super_L:   nothing()\n\
<KeyUp>Super_R:   nothing()\n\
<KeyUp>Alt_L:     nothing()\n\
<KeyUp>Alt_R:     nothing()\n\
<KeyUp>Caps_Lock: nothing()\n\
<KeyUp>Shift_Lock:nothing()\n\
<Key>Return:      select()\n\
<Key>Down:        down()\n\
<Key>Up:          up()\n\
<Key>Left:        left()\n\
<Key>Right:       right()\n\
<Key>:            key()\n\
<KeyUp>:          key()\n\
";

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:

> I thought that was fixed a while ago.  It works for me here on both core
> input and XInput 2, so I don't know what could be going on.
>
> Do you have anything set up that could be overriding the following
> translations?

I can reproduce the problem, too, so I can check.  But override where?
In Gnome Shell?

Using the keyboard works fine in temacs, but not in the dumped Emacs.
Could this also be related to X resources, like the background colour of
the menu bar?  I don't seem to have any keyboard-related things in my X
resources.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Lars Ingebrigtsen <larsi@gnus.org> writes:

    > Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
    > editors" <bug-gnu-emacs@gnu.org> writes:

    >> I thought that was fixed a while ago.  It works for me here on
    >> both core input and XInput 2, so I don't know what could be going
    >> on.
    >> 
    >> Do you have anything set up that could be overriding the
    >> following translations?

    > I can reproduce the problem, too, so I can check.  But override
    > where?  In Gnome Shell?

    > Using the keyboard works fine in temacs, but not in the dumped
    > Emacs.  Could this also be related to X resources, like the
    > background colour of the menu bar?  I don't seem to have any
    > keyboard-related things in my X resources.

    > -- (domestic pets only, the antidote for overdose, milk.)  bloggy
    > blog: http://lars.ingebrigtsen.no

I suppose the Lucid issue with no key-navigation of a popup menu is not
so important since the problem disappears (for me) once the Lucid
compiled emacs is installed. Perhaps it might be worth a note to this
effect in the INSTALL documentation?

Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Colin Baxter <m43cap@yandex.com> writes:

> I suppose the Lucid issue with no key-navigation of a popup menu is not
> so important since the problem disappears (for me) once the Lucid
> compiled emacs is installed.

It's just interesting to find out what's going on here -- there might be
other problems in the same area.

Copying src/emacs and src/emacs.pdmp to /tmp and executing /tmp/emacs
also makes the problem disappear.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Visuwesh]

[திங்கள் ஜூன் 20, 2022] Lars Ingebrigtsen wrote:

> Colin Baxter <m43cap@yandex.com> writes:
>
>> I suppose the Lucid issue with no key-navigation of a popup menu is not
>> so important since the problem disappears (for me) once the Lucid
>> compiled emacs is installed.
>
> It's just interesting to find out what's going on here -- there might be
> other problems in the same area.
>
> Copying src/emacs and src/emacs.pdmp to /tmp and executing /tmp/emacs
> also makes the problem disappear.

Weird... I can use arrow keys just fine here in a Lucid build.  My emacs
executable lives in src/emacs and my PATH contains,

    ~/lib/ports/emacs/lib-src:~/lib/ports/emacs/src

where ~/lib/ports/emacs is where I have the Emacs repo cloned.

The way I launch Emacs doesn't seem to matter either: I tried
`./src/emacs -Q' and `emacs -Q' and both don't show the problem.  If it
is of any help, `xrdb -query' prints,

    *customization:	-color

[ To be clear, I have no Xresources file anywhere in my home directory.  ]

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Colin Baxter]

>>>>> Visuwesh  <visuweshm@gmail.com> writes:

    > [திங்கள் ஜூன் 20, 2022] Lars Ingebrigtsen wrote:
    >> Colin Baxter <m43cap@yandex.com> writes:
    >> 
    >>> I suppose the Lucid issue with no key-navigation of a popup menu
    >>> is not so important since the problem disappears (for me) once
    >>> the Lucid compiled emacs is installed.
    >> 
    >> It's just interesting to find out what's going on here -- there
    >> might be other problems in the same area.
    >> 
    >> Copying src/emacs and src/emacs.pdmp to /tmp and executing
    >> /tmp/emacs also makes the problem disappear.

    > Weird... I can use arrow keys just fine here in a Lucid build.  My
    > emacs executable lives in src/emacs and my PATH contains,

    >     ~/lib/ports/emacs/lib-src:~/lib/ports/emacs/src

    > where ~/lib/ports/emacs is where I have the Emacs repo cloned.

    > The way I launch Emacs doesn't seem to matter either: I tried
    > `./src/emacs -Q' and `emacs -Q' and both don't show the problem.
    > If it is of any help, `xrdb -query' prints,

    >     *customization: -color

    > [ To be clear, I have no Xresources file anywhere in my home
    > directory.  ]

No ~/.Xresource? That's interesting. I think the common factor for those
who see the problem is that they have such a file, even though emacs
settings may have been commented out. I'll remove my Xresources and see
what happens.

Best wishes,

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Colin Baxter <m43cap@yandex.com> writes:

> I suppose the Lucid issue with no key-navigation of a popup menu is not
> so important since the problem disappears (for me) once the Lucid
> compiled emacs is installed. Perhaps it might be worth a note to this
> effect in the INSTALL documentation?

Ah.  Then it's this:

/* For debug, if installation-directory is non-nil this is not an installed
   Emacs.   In that case we do not grab the keyboard to make it easier to
   debug. */
#define GRAB_KEYBOARD  (EQ (Vinstallation_directory, Qnil))

and it's not a bug.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Visuwesh]

[திங்கள் ஜூன் 20, 2022] Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:

> Colin Baxter <m43cap@yandex.com> writes:
>
>> I suppose the Lucid issue with no key-navigation of a popup menu is not
>> so important since the problem disappears (for me) once the Lucid
>> compiled emacs is installed. Perhaps it might be worth a note to this
>> effect in the INSTALL documentation?
>
> Ah.  Then it's this:
>
> /* For debug, if installation-directory is non-nil this is not an installed
>    Emacs.   In that case we do not grab the keyboard to make it easier to
>    debug. */
> #define GRAB_KEYBOARD  (EQ (Vinstallation_directory, Qnil))
>
> and it's not a bug.

`installation-directory' is non-nil for me yet I can navigate the menus
with the keyboard.

    installation-directory is a variable defined in ‘C source code’.

    Its value is "/home/viz/lib/ports/emacs/"

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Visuwesh <visuweshm@gmail.com> writes:

> `installation-directory' is non-nil for me yet I can navigate the menus
> with the keyboard.
>
>     installation-directory is a variable defined in ‘C source code’.
>
>     Its value is "/home/viz/lib/ports/emacs/"

Whether or not the keyboard must be grabbed for key navigation to work
depends on various details of your system, and whether or not the mouse
pointer happens to be on top of the menu bar at the time (if you're
running an XInput 2 build), so I'm not surprised that it works for some
people regardless of the value of GRAB_KEYBOARD.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Visuwesh]

[திங்கள் ஜூன் 20, 2022] Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" wrote:

> Visuwesh <visuweshm@gmail.com> writes:
>
>> `installation-directory' is non-nil for me yet I can navigate the menus
>> with the keyboard.
>>
>>     installation-directory is a variable defined in ‘C source code’.
>>
>>     Its value is "/home/viz/lib/ports/emacs/"
>
> Whether or not the keyboard must be grabbed for key navigation to work
> depends on various details of your system, and whether or not the mouse
> pointer happens to be on top of the menu bar at the time (if you're
> running an XInput 2 build), so I'm not surprised that it works for some
> people regardless of the value of GRAB_KEYBOARD.

Right, point noted.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Colin Baxter <m43cap@yandex.com> writes:

> I suppose the Lucid issue with no key-navigation of a popup menu is not
> so important since the problem disappears (for me) once the Lucid
> compiled emacs is installed. Perhaps it might be worth a note to this
> effect in the INSTALL documentation?

Ah.  Then it's this:

/* For debug, if installation-directory is non-nil this is not an installed
   Emacs.   In that case we do not grab the keyboard to make it easier to
   debug. */
#define GRAB_KEYBOARD  (EQ (Vinstallation_directory, Qnil))

and it's not a bug.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Po Lu <luangruo@yahoo.com> writes:

> Ah.  Then it's this:
>
> /* For debug, if installation-directory is non-nil this is not an installed
>    Emacs.   In that case we do not grab the keyboard to make it easier to
>    debug. */
> #define GRAB_KEYBOARD  (EQ (Vinstallation_directory, Qnil))
>
> and it's not a bug.

It's always nice when behaviour like this has a logical explanation.  😀

But I'm not sure whether we actually want this.  The commit message is
somewhat vague -- what's the debugging this simplifies?  Is it still
relevant?  I've added Jan to the CCs; perhaps he remembers the reasoning
for the 20 year old change:

diff --git a/lwlib/ChangeLog b/lwlib/ChangeLog
index 28626ddc25..3ead711d79 100644
--- a/lwlib/ChangeLog
+++ b/lwlib/ChangeLog
@@ -1,3 +1,8 @@
+2002-04-28  Jan D.  <jan.h.d@swipnet.se>
+
+	* xlwmenu.c: Do not grab keyboard if installation-directory is
+	non-nil (not installed Emacs).  To simplify debugging.
+


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> Cc: Colin Baxter <m43cap@yandex.com>, 46990@debbugs.gnu.org,
>  "Jan D." <jan.h.d@swipnet.se>
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Mon, 20 Jun 2022 17:38:55 +0200
> 
> > /* For debug, if installation-directory is non-nil this is not an installed
> >    Emacs.   In that case we do not grab the keyboard to make it easier to
> >    debug. */
> > #define GRAB_KEYBOARD  (EQ (Vinstallation_directory, Qnil))
> >
> > and it's not a bug.
> 
> It's always nice when behaviour like this has a logical explanation.  😀
> 
> But I'm not sure whether we actually want this.  The commit message is
> somewhat vague -- what's the debugging this simplifies?  Is it still
> relevant?  I've added Jan to the CCs; perhaps he remembers the reasoning
> for the 20 year old change:

I think it's better to have a variable that people who need to debug
this code could set.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

> I think it's better to have a variable that people who need to debug
> this code could set.

I've now introduced a variable for this -- lucid--menu-grab-keyboard.

Po Lu <luangruo@yahoo.com> writes:

> If the keyboard is grabbed, typing anything into another window becomes
> impossible, which is not pleasant if you need to debug the Lucid menu
> bar.
>
> Jan's email bounces, but I would trust his judgement.

It sounds convenient indeed, but ease of debugging shouldn't take
precedence over something actually working for users.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Manuel Giraud]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> I think it's better to have a variable that people who need to debug
>> this code could set.
>
> I've now introduced a variable for this -- lucid--menu-grab-keyboard.

Hi Lars,

Another data point: this patch is a regression for me.

I have the menu-bar on and when I navigate it with the keyboard
afterward I cannot revert to "correct" behaviour into buffers: my cursor
stays hollow, and since I'm using EXWM, external X programs cannot get
back the keyboard input at all.

Tell me, if you want me to do some tests.
-- 
Manuel Giraud

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Eli Zaretskii]

> From: Manuel Giraud <manuel@ledu-giraud.fr>
> Cc: Eli Zaretskii <eliz@gnu.org>,  luangruo@yahoo.com,  m43cap@yandex.com,
>   46990@debbugs.gnu.org,  jan.h.d@swipnet.se
> Date: Tue, 21 Jun 2022 14:30:12 +0200
> 
> Another data point: this patch is a regression for me.

And now?

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Manuel Giraud]

Eli Zaretskii <eliz@gnu.org> writes:

> And now?

Yes it works "as before" AFAICS. Nasty typo by the way.
-- 
Manuel Giraud

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Lars Ingebrigtsen]

Manuel Giraud <manuel@ledu-giraud.fr> writes:

> I have the menu-bar on and when I navigate it with the keyboard
> afterward I cannot revert to "correct" behaviour into buffers: my cursor
> stays hollow, and since I'm using EXWM, external X programs cannot get
> back the keyboard input at all.

I had a reversed check for the ungrab case; should be fixed now.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> But I'm not sure whether we actually want this.  The commit message is
> somewhat vague -- what's the debugging this simplifies?  Is it still
> relevant?  I've added Jan to the CCs; perhaps he remembers the reasoning
> for the 20 year old change:

If the keyboard is grabbed, typing anything into another window becomes
impossible, which is not pleasant if you need to debug the Lucid menu
bar.

Jan's email bounces, but I would trust his judgement.

bug#46990: 28.0.50; popup menu not navigable via arrow keys on lucid build

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Using the keyboard works fine in temacs, but not in the dumped Emacs.
> Could this also be related to X resources, like the background colour of
> the menu bar?  I don't seem to have any keyboard-related things in my X
> resources.

Possibly.  What happens after you run `xrdb -remove'?  (A word of
warning, this will trash the resources loaded into the root window.)