From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Charles A. Roelli" <charles@aurox.ch>,
27114@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#27114: 25.2: fringe click echoes "Emacs-Lisp:" in emacs-lisp mode
Date: Sat, 30 Sep 2017 22:25:57 -0600 [thread overview]
Message-ID: <87vajzwl2i.fsf@gmail.com> (raw)
In-Reply-To: <83shglasw7.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 21 Aug 2017 17:37:44 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 21 Aug 2017 15:20:14 +0200
>> From: charles@aurox.ch (Charles A. Roelli)
>> CC: agrambot@gmail.com, npostavs@users.sourceforge.net,
>> 27114@debbugs.gnu.org
>>
>> > (If you make the proposed change, and then visit some .el file and
>> > click C-mouse-3, what do you see in the header of the pop-up menu?)
>>
>> I still see "Emacs-Lisp Mode" (it's unchanged). Notice that Alex's
>> change removes the "overall prompt" from the "main" Emacs Lisp mode
>> keymap, but not the menu-map.
>
> Then maybe I was confused, and Alex's patch is TRT.
>
> Thanks.
I think it should be applied. The reason I was hesitant in my original
message was because I wasn't sure if displaying menu names when clicking
in the fringe was correct behaviour.
If it is, then I believe the diff is TRT. If it isn't correct behaviour,
then the behaviour itself should be fixed, but I suppose the diff should
still be applied to simplify the definition a bit.
prev parent reply other threads:[~2017-10-01 4:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 9:46 bug#27114: 25.2: fringe click echoes "Emacs-Lisp:" in emacs-lisp mode Charles A. Roelli
2017-05-30 23:16 ` npostavs
2017-05-31 6:23 ` Eli Zaretskii
2017-08-09 23:07 ` Alex
2017-08-20 14:14 ` Charles A. Roelli
2017-08-20 14:58 ` Eli Zaretskii
2017-08-21 13:20 ` Charles A. Roelli
2017-08-21 14:37 ` Eli Zaretskii
2017-08-24 9:38 ` Charles A. Roelli
2018-07-18 1:45 ` Noam Postavsky
2017-10-01 4:25 ` Alex [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vajzwl2i.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=27114@debbugs.gnu.org \
--cc=charles@aurox.ch \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.