From: Tino Calancha <f92capac@gmail.com>
To: 23672@debbugs.gnu.org
Subject: bug#23672: 25.0.94; unitialized package specific menus
Date: Wed, 1 Jun 2016 22:33:55 +0900 (JST) [thread overview]
Message-ID: <alpine.LRH.2.20.1606012232140.30286@calancha-ilc.kek.jp> (raw)
The menus especific to one package, e.g. dired, are not
always fully initialized after loading the library:
some menus may show _anything_ after click on them.
emacs -Q
C-x C-f RET
;;; click mouse left button on Menu "Regexp"
;; The menu doesn't appear correctly.
;; Same happen with menus: "Mark", "Immediate" or "Subdir"
:: Menu "Operate" shows the wrong information.
;;
;;; Now click mouse left button on Menu "Tools".
;; The previous menus are refreshed and show the correct information.
;;; Now try similar test but starting Emacs with:
emacs -Q ~
C-x C-f RET
;;; This time, all menus are initialized and show the right info.
;;; This is a general issue not something restricted to dired.
;; For instance, compare the response of menu "Mark" in I), II) and III):
I)
./emacs -Q
M-x ibuffer RET
;; "View" and "Mark" don't respond as expected; "Operate" looks wrong too.
II) ./emacs -Q --eval "(require 'ibuffer)"
M-x ibuffer RET
;; Same as I)
III) ./emacs -Q --eval '(ibuffer)'
;; All menus looks good.
In GNU Emacs 25.0.94.2 (x86_64-pc-linux-gnu, GTK+ Version 3.20.4)
Repository revision: 9c28e70b4b4b1887030e41103b5f6dd8304585e6
next reply other threads:[~2016-06-01 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 13:33 Tino Calancha [this message]
[not found] ` <handler.23672.B.146478786215027.ack@debbugs.gnu.org>
2016-06-01 14:57 ` bug#23672: (25.0.94; Menu corrupted after being used Tino Calancha
2016-06-01 17:40 ` Glenn Morris
2016-06-04 8:50 ` Eli Zaretskii
2016-06-01 22:02 ` bug#23672: 25.0.94; unitialized package specific menus Paul Eggert
2016-06-02 4:54 ` Tino Calancha
2016-06-02 6:49 ` Paul Eggert
2016-06-06 23:16 ` Glenn Morris
2016-06-07 4:38 ` Tino Calancha
2016-06-04 8:39 ` Eli Zaretskii
2018-07-16 2:48 ` Tino Calancha
2018-07-20 9:23 ` Eli Zaretskii
2018-07-20 14:23 ` Tino Calancha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.20.1606012232140.30286@calancha-ilc.kek.jp \
--to=f92capac@gmail.com \
--cc=23672@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).